![]() |
|
|||||||
| Home | Register | FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Bug Reports Post about errors or bugs encountered. |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Hi,
I found a little bug or unpleasent property, when using NumUpDown control. When I set maximum (for example to 100), using keyboard I'm able to write greater value to the NumUp control then setted maximum . But program calculate with maximum value (100 in this case). So I can see another value, then is used for calculating and the outcome could be confusing. Regards Petr. |
|
|||
|
Yes, I reported this allready in the old forum. The problem is that keyboard entries do not trigger the ValueChanged-event and therefore there is no min/max-check.
As far as I remember Erel plans to fix this issue with the next version.
__________________
iPAQ 6515, MDA compact |
|
|||
|
Thank you for your reply Erel, but I've upgraded my PDA to NETCF2 SP2 and behaviation of NumUpDown didn't change. As I wrote, that's no problem to check maximum in program, but I'd like to know, why it don't work. By the way, is there any possibility, how to find out, what release of NETCF is running on my PDA?
Thanks in advance Petr |
|
||||
|
See this post: How to check whether .Net CF 2.0 is installed correctly
|
|
|||
|
Thank you Erel, now I have no problem with NumUpDown
. I had an impression, that I saw the advice about NETCF installing but I searched it on forum and forgot about Basic4ppc.com But I don't know how to test release of NETCF. Please see my reply on your thread about it. Petr |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| NumUpDown | skipper | Questions & Help Needed | 2 | 02-13-2008 04:19 PM |
| NumUpDown anomaly | agraham | Bug Reports | 1 | 07-30-2007 04:57 PM |
| NumUpDown control | davelew1s | Questions & Help Needed | 5 | 07-29-2007 08:25 PM |
| Wrong numUpDown control during design on the device | specci48 | Bug Reports | 0 | 05-20-2007 08:24 AM |