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
Reported by jteh on 2008-11-05 23:44
IN the sliders for the speech parameters in the Voice Settings dialog, the up arrow key decreases the setting and down arrow increases it. This is not logical, as these are simple numeric settings, so up should increase and down should decrease. This also makes these sliders consistent with the synth settings ring.
The left and right arrow keys are fine as they are.
The text was updated successfully, but these errors were encountered:
Comment 2 by pvagner on 2009-07-16 12:29
I have just discovered there is a style wx.SL_INVERSE for wxpython sliders which changes the behaviour of up and down arrow keys. It however also changes value reporting. While going upwards the value is decreasing and while going down value is increasing.
Now we do need to decide whether we do want to implement our keys for classic slider or whether we do rather like inverse style and we'll need to override value reporting.
Changes:
Changed title from "Up arrow and downn arrow keys should be reversed in Voice Settings dialog sliders" to "Up arrow and down arrow keys should be reversed in Voice Settings dialog sliders"
Comment 4 by pvagner on 2010-09-22 04:49
After some reading I've found out wx does not fire appropriate events when changing the value of slider programmatically. I need to figure out how to post the event manually and then if you like we can use this patch.
Reported by jteh on 2008-11-05 23:44
IN the sliders for the speech parameters in the Voice Settings dialog, the up arrow key decreases the setting and down arrow increases it. This is not logical, as these are simple numeric settings, so up should increase and down should decrease. This also makes these sliders consistent with the synth settings ring.
The left and right arrow keys are fine as they are.
The text was updated successfully, but these errors were encountered: