search

subhashis / fibernavigator

Automatically exported from code.google.com/p/fibernavigator
0 stars 1 forks source link

Events triggered twice #47

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
From what I have tested, all wxCommandEvent are triggered twice. I did a search 
and it seems to be present in the 2.8 branch of wxWidgets. An update of 
wxWidgets would be required.

Original issue reported on code.google.com by levesque...@gmail.com on 5 Nov 2011 at 4:38

GoogleCodeExporter commented 9 years ago 
On what OS what is tested? Was it reproduced on OSX, Linux?

Is there a link to the page explaining the problem with the 2.8 branch of 
wxWidgets?

What steps were taken to test this? How would it be reproduced?

Original comment by Jean.Chr...@gmail.com on 6 Nov 2011 at 3:38

GoogleCodeExporter commented 9 years ago 
It was tested on Windows 7 64bits. Didn't try the other OS' yet.

The ticket I found about it is : http://trac.wxwidgets.org/ticket/10530

To test this, simply put a breakpoint inside the callback function of a slider, 
such as Threshold (new slider for the equalization threshold in 
Personal_JFLevesque_EqualizationSlider branch). So, for each click of the mouse 
on the slider, the callback function gets called twice. To verify if it was 
also present in the release version, I added a call to printDebug saying my 
method was called. In the logs, I could then see two times the same message 
with the same timestamp.

Original comment by levesque...@gmail.com on 6 Nov 2011 at 3:48

GoogleCodeExporter commented 9 years ago 
Tested on OSX and Ubuntu 10.04. Behavior is different from the behavior in 
Windows, and different between OSX and Ubuntu.

OSX: the event is triggered once on each click on the slider, and once when the 
value changed.

Ubuntu 10.04: the event is triggered only when the value of the slider changes, 
and is triggered only once.

If it does not create big problems on the Windows version of the 
fibernavigator, we will leave it as is for the moment since, according to the 
ticket linked in the previous comment, the problem is present on wxMSW, even in 
the 2.9 branch of the code, so even updating wxWidgets would not fix this.

Original comment by Jean.Chr...@gmail.com on 7 Nov 2011 at 4:05