You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In standard GUI design, a double-click should me measured as two consecutive mouse clicks with a certain timing between them (i.e. 500ms or less, usually an operating system setting because Accessibility settings can modify this). Consecutive clicks outside of the timeframe should be treated as single clicks.
It appears that Dynobase isn't watching this timing. If you click on a field in a table, wait 2 seconds, then click again, it brings up the shortcut editor that should only appear with a normally timed double-click. It appears these single clicks are being cached as the first half of a double click, leading to strange behavior as you click around the screen.
Example:
Click a field
Wait 2 seconds
Click same place again
Quick editor box appears (it should not, it wasn't a proper double click)
Example:
Click a field
Wait 2 seconds
Double click normally on the field
The quick editor box will briefly flash and go away because you're now out of sync. The first click of your proper double click will actually "finish" the incorrect double click action from step 1, showing the box, then your final click will dismiss it all within a few ms.
Example:
Click a field
wait 2 seconds
Option+click on mac to. open larger record editor
The window won't open properly as the cached click has messed up the processing.
There are other examples of UI errors from this bug but it all stems from the same place.
The text was updated successfully, but these errors were encountered:
In standard GUI design, a double-click should me measured as two consecutive mouse clicks with a certain timing between them (i.e. 500ms or less, usually an operating system setting because Accessibility settings can modify this). Consecutive clicks outside of the timeframe should be treated as single clicks.
It appears that Dynobase isn't watching this timing. If you click on a field in a table, wait 2 seconds, then click again, it brings up the shortcut editor that should only appear with a normally timed double-click. It appears these single clicks are being cached as the first half of a double click, leading to strange behavior as you click around the screen.
Example:
Example:
Example:
There are other examples of UI errors from this bug but it all stems from the same place.
The text was updated successfully, but these errors were encountered: