DateTimePicker up-down arrows behaviour

0
0

Hi guys,

Please have a look at the attached project with a DateTimePicker configured for Time-only display. The up-down arrows is strange. To see what I mean take the following steps:

  1. place the mouse cursor in the minutes part
  2. press the up arrow – minutes are highlighted and go up by 1 – correct
  3. press again the  up arrow – whole time, hour and minutes get highlighted and minutes go up by 1
  4. press again the up arrow – hour and minutes remain highlighted and hour goes up by 1
  5. press again the up arrow – hour only remains highlighted and goes up by 1
  6. all next up arrows increase the hour part

So, I started trying to increase minutes and I end up increasing hours. Same thing happens for down arrow.

Even stranger, sometimes when I press the down arrow it goes up just for once and then down for the next times. This rings a bell, so it might be a regression.

Best,
Alex

Attachment
  • You must to post comments
0
0

Hi Alex,

The fix was related to the Up/Down keyboard arrows (it also added PageUp and PageDown support) and broke the Up/Down button arrows. It is fixed and included in the current build which should be released tomorrow, also the Up/Down buttons are now repeat buttons – keeping them pressed repeats the click. Currently there is the development build 1.3.20 available for downloading (it still has this problem though).

Thanks!

/Luca

  • Alex Prinias
    a, ok, then this was a misunderstanding from start, I was referring to the buttons, not the keys. Anyway, if it’s fixed in the next release, all good! :) Alex
  • You must to post comments
0
0

Hi,

Unfortunately, the fix in 1.3.18, which I just checked, was rather radical ! I mean, the wrong behaviour I described is not there any more, but now the up/down arrows do nothing! Clicking on them does not affect the control value at all. You can check it with the original attached test project.

Best,
Alex

  • You must to post comments
0
0

Hi Alex,

WJ-7891 fix is included in the latest build (1.3.18).

Best regards
Frank

  • You must to post comments
0
0

Thanks Alex,

we could reproduce, logged as WJ-7891 and fixed it.

It will be in the next build.

Best regards
Frank

  • You must to post comments
Showing 4 results
Your Answer

Please first to submit.