-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto range issues in Compare Models & more #327
Comments
@Mrnofish thanks i will look at it. But wont be before September. sorry |
I'm sure there are good reasons for this, however I have to ask: Does this mean work pace slowing down significantly and that less important tickets will have to be put on a or slow lane or even the backburner ? Or rather, no updates at all for the next 7 months? |
@Mrnofish i ll be on a bike for the next 6 months. I wont have a computer but only a tablet. I have set up everything so that i can still make bug fixes / releases. However as i wont be able to build locally for testing, bug fixes will limit to things i am sure about so that i can start a release from github actions. |
Understood, thanks for clearing that up. Sounds like you're going on an adventure... is this going to be something that can be followed over the Internet? |
@Mrnofish yes it is but only for close family. I dont really like having personal stuff / images on the internet. I dont really trust it ;) |
I've been encountering issues with auto ranging in Compare Models, specifically:
May be related: occasionally the whole app gets stuck in landscape mode when using "force landscape for charts", even after switching apps, main view would still trigger a screen rotation.
1 seems deterministic and easy to reproduce, as long as that data pattern is available.
2 can be induced if you select temp low hourly (a combo that does not exist) and then switch to temp hourly.
Speaking of which, it might be sensible to somehow prevent the selection of non-existent metrics, such as hourly temp max.
The whole metric selection pane could use some refinement,.however disabling controls for unavailable metrics would also be fine.
The text was updated successfully, but these errors were encountered: