Hello,
building upon my earlier (but difficult to implement) suggestion and the forum discussion on event data here I can provide a hopefully improved suggestion.
The issues addressed by this idea:
- receiving an EVENT_DATA_CHANGED event for a numeric control does not mean that the numeric value has changed
- receiving an EVENT_DATA_CHANGED event for a numeric control does not provide information if the value has been increased or decreased
- receiving an EVENT_DATA_CHANGED event for a numeric control does not provide information if the 'up' or 'down' arrow button has been pressed (which is not necessarily the same as the second issue)
Idea: Provide eventData1 and eventData2 information.
For example, eventData1 could tell about the numeric value:
- eventData1 = -1: numeric value has been decreased
- eventData1 = 0: numeric value is unchanged
- eventData1 = 1: numeric value has been increased
eventData2 could tell about the increment/decrement arrow, e.g.:
- eventData2 = -1: decrement arrow has been pressed by mouse
- eventData2 = -2: decrement arrow has been pressed on keyboard
- eventData2= 1: increment arrow has been pressed by mouse
- eventData2= 2: increment arrow has been pressed on keyboard
Since so far no eventdata are provided this suggestion should not break backward compatibility.
