-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
Table switches unintentionally #20
Comments
It happens when a timefield is highlighted by the note. For example, if it is currently after sunset and the note is for sunrise (tomorrow), it will highlight that field (swapping the cards if "today" is currently shown). At the moment that happens whenever the note is updated, which is happening in each of the cases you describe. I think its that last one (when the clock shows the next minute) that is unexpected/annoying since it steals the view against the user's intention. What is the right behavior here? We could disable highlighting the field entirely (no more transitions at all), or maybe detect when today/tomorrow have been explicitly swapped (and then prevent the highlighting from hijacking the view), or toggle behaviors w/ an option. |
#20: the today/tomorrow card no longer switches when clock shows next minute; the today/tomorrow card is retained when swapping apps / on orientation change
fixed in v0.2.0 |
...still a problem. It works correctly when pressing the next ">" and prev "<" buttons, but swiping the view triggers the bug. Even a partial swipe (that doesn't trigger a card change) seems to reset the flag, and the next update switches the table. tested against v0.2.1, v0.3.0 (api19) |
withSwipe, withNextButton reproduces bug in #20
fix for #20 .. it should only be possible to set flag true from touch listener (the flag shouldn't be reset if failed to swap view). To trigger the bug.. swipe, a double ACTION_UP occurs (caused by "extended move" in ACTION_MOVE) - the first ACTION_UP swaps the view (setting flag true), the second ACTION_UP tries again (and fails setting flag false).
Ahoi Forrest,
another one here ;-)
The table in the main activity switches on some events that I would not expect.
It seems to switch between today and tomorrow e.g.:
The last two appear intended, what do you say?
Greetings
~HerHde
The text was updated successfully, but these errors were encountered: