Skip to content
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

Double-click timing not honored #238

Open
ktwbc opened this issue Jul 17, 2023 · 0 comments
Open

Double-click timing not honored #238

ktwbc opened this issue Jul 17, 2023 · 0 comments

Comments

@ktwbc
Copy link

ktwbc commented Jul 17, 2023

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:

  1. Click a field
  2. Wait 2 seconds
  3. Click same place again
  4. Quick editor box appears (it should not, it wasn't a proper double click)

Example:

  1. Click a field
  2. Wait 2 seconds
  3. Double click normally on the field
  4. 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:

  1. Click a field
  2. wait 2 seconds
  3. Option+click on mac to. open larger record editor
  4. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant