Johannes Ringler
Johannes Ringler
there is a potential issue with detecting markers reliably, potentially due to the changes introduced in https://github.com/Novakasa/brickrail/commit/af6be84cb096e934f38f5c66f810c60b12a329da and related commits, to filter out colors that are never used as markers...
to be investigated probably some scheduling issue between disabling switch control when train is going over switch
> Ok, it happened again, but with a Byte array error and then disconnected the BLE > I had increased the chroma on both trains as I was getting random...
we don't really need control over which end of the block the train stays at anymore, flipping the heading at the end will be very short since the train only...
this might help with current block rendering issues, where I'm guessing the float to int precision doesn't hold up for high values, making some of the states go bad. Replacing...
**Is your feature request related to a problem? Please describe.** When people encounter issues with Brickrail, it will be really helpful to have some information of what was going on...
Seeing this: https://github.com/pybricks/pybricksdev/pull/52 which links: https://docs.micropython.org/en/latest/develop/natmod.html Seems to be really useful if we want/need to make the hub programs much more efficient in the future.
**Is your feature request related to a problem? Please describe.** Currently we have one control scheme that relies on right- and left click (and optional middle mouse click). Especially right...
if hub is not responsive, trigger emergency stop this can be the case when hub battery is low or pybricks crash
requested in https://github.com/Novakasa/brickrail/discussions/107#discussioncomment-5689736 Should be possible by setting the size in the GUI font resource dynamically. Needs some remodeling of some Control nodes and scroll bars in the layout gui...