View Issue Details

IDProjectCategoryView StatusLast Update
0001946NoesisGUIC# SDKpublic2021-04-29 10:26
Reporterai_enabledAssigned Tosfernandez 
Status resolvedResolutionfixed 
Product Version3.0.9 
Target Version3.0.12Fixed in Version3.0.12 
Summary0001946: RepeatButton commits extra command when pressed repeatedly
DescriptionHi guys,
If the user clicks on the button too often, it often invokes the Command two times per single frame.
I've tried setting high Delay but the issue persisted so it seems to be not related.
It's like it's listening to the double click event now. Really odd.

TagsNo tags attached.




2021-03-19 15:54

updater   ~0007090

Actually, there is a more serious issue. Very often the click is registered two times in the row.
There were no changes on our side and we've noticed the issue only today, using 3.0.9 and didn't test it thoroughly.


2021-03-19 16:11

updater   ~0007091

Were there any input-related changes lately?


2021-03-19 17:08

updater   ~0007092

Last edited: 2021-03-19 17:08

View 2 revisions

After further investigation, it seems to be related to Noesis.MouseDoubleClick operating now differently. (I've commented it out and cannot reproduce the issue anymore)



2021-03-19 17:14

updater   ~0007093

Last edited: 2021-03-19 17:15

View 2 revisions

Reworked now our input processing code to match how NoesisGUI operates in Unity (to call either MouseDoubleClick or MouseButtonDown, previously we've called MouseDoubleClick before MouseButtonDown in the case of double click). The issue seems to be gone, will keep you updated!



2021-03-19 21:25

updater   ~0007094

Yes, it was that. Using the input processing code similar to one from Unity plugin, resolved it completely.

Please close this issue.


2021-03-20 13:16

manager   ~0007095

Last edited: 2021-03-20 13:16

View 3 revisions

We expect the following events when double click happens:

MouseButtonDown  <-- first click
MouseDoubleClick   <-- second click

This is legacy behavior from Win32 API and risky to change but we should definitely document this properly because it is not the first time it is source of confusion.

Issue History

Date Modified Username Field Change
2021-03-19 12:35 ai_enabled New Issue
2021-03-19 12:36 jsantos Assigned To => sfernandez
2021-03-19 12:36 jsantos Status new => assigned
2021-03-19 12:36 jsantos Target Version => 3.0.12
2021-03-19 15:54 ai_enabled Note Added: 0007090
2021-03-19 16:11 ai_enabled Note Added: 0007091
2021-03-19 17:08 ai_enabled Note Added: 0007092
2021-03-19 17:08 ai_enabled Note Edited: 0007092 View Revisions
2021-03-19 17:14 ai_enabled Note Added: 0007093
2021-03-19 17:15 ai_enabled Note Edited: 0007093 View Revisions
2021-03-19 21:25 ai_enabled Note Added: 0007094
2021-03-20 13:16 jsantos Note Added: 0007095
2021-03-20 13:16 jsantos Note Edited: 0007095 View Revisions
2021-03-20 13:16 jsantos Note Edited: 0007095 View Revisions
2021-04-29 10:26 sfernandez Status assigned => resolved
2021-04-29 10:26 sfernandez Resolution open => fixed
2021-04-29 10:26 sfernandez Fixed in Version => 3.0.12