Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COA NumericUpDown is *not* as easily created as you think. Try to build / find a decent implementation that actually works with spinners *and* masked text - and let me know when you do :) Aside from that, the question is that for the most-used, standard controls - why would you *want* everyone to build them themselves ? The idea should be consistency in user-experience across apps, so why make that so hard for developers ? Hand them the standard controls, and if they need something more - *then* they could 'easily' make it themselves, right ?
      singulars
    2. COI created a basic NumericUpDown, it's not much code, I haven't tried to make it to work with spinners and masked text though =P. The fact is, if someone needs a control to show a hand of cards for a poker game, can create it. Obviously microsoft won't release a basic "CardHand" user control, that's the same for other controls. Pretty basic one like NumericUpDown (that was part of Windows Form already) should have been released, i know, but maybe it goes against the finality of the product..
      singulars
    3. COOfcourse a numericupdown without spinners and masked text is not much code. Those 2 things working *well* are actually what make a good NumericUpDown :) And I don't consider a cardhand a most-used control. But the webbrowser I'm typing this in uses numericupdown-controls in multiple places, as does my text-editor, programming-ide, photoshop etc.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload