General Category > Additional Components
New Keypad
Phrog30:
--- Quote from: Archie on June 18, 2017, 04:13:45 PM ---The Setter for the AllowNegatives property was not setting the field value of m_AllowNegative:
m_AllowNegatives = value
Is the AllowNegatives property really needed since setting MinValue to >=0 could indicate the same thing?
--- End quote ---
Probably not. Again, I tried to keep this as open as possible so it can be used across the board. Your keypad has this property as well.
Attached is an updated file. It's a single file (at least what I consider a single file), but still allows edits in designer. I edited the properties for allowdecimal and negative to align with your keypad. Mine has "s" at the end, yours didn't. I also found a few things that weren't quite correct and added the option to show current value in the white box on load or leave blank, leave blank is default. Personally, I don't see the need for keypad width. The current size is small enough for most displays and big enough to not fat finger. I left the property to align with the original keypad, but it's not being used. Perhaps one day I will be get this .NET stuff, but for now I'm just going for functional. I know that makes real programmers cringe, but even though my code might not be standard, I still consider it simple and easy to follow.
James
Archie:
--- Quote from: Phrog30 on June 18, 2017, 04:38:32 PM ---Personally, I don't see the need for keypad width. The current size is small enough for most displays and big enough to not fat finger.
--- End quote ---
Many version ago the keypad was fixed at one size, but after several deployments that I can recall in which the first request was a larger keypad, the size property was added. The problem with Winforms is its resolution dependence. You may deploy on one system with a 12" screen at 800x600 in which a keypad size works well, but then you may get an 8" screen also with 800x600 in which the keypad will shrink considerably.
Phrog30:
I understand. I'm looking for a panelview replacement. If you notice FTView keypad and keyboard are all the same size, which is what I'm doing as well. Also, we probably will never go below a 15" display. We have no plans to use AHMI as SE or run on a desktop machine. However, my needs and those of others will probably vary widely, so I can understand the features you have currently.
Phrog30:
Found a bug I missed, here is an update:
James
BlueAltezza:
I know this thread is ancient, but the v3 has features my customers definitely want/need.
I got the keypad to pop up as desired, but after entering data/closing the new keypad the standard keypad pops up as usual.
Is there a way to do a global replace of the standard keypad or a way to prevent the standard keypad from appearing after the v3?
I'm also using an additional write instruction to relay the data from v3 keypad to desired tag...where the standard keypad has that built in.
Is using the additional write instruction the preferred method or is there a way to build that in?
Navigation
[0] Message Index
[*] Previous page
Go to full version