On 3/13/2018 5:58 AM, Jeff Young wrote: > There’s a wishlish item to make support for typed-in units more discoverable. > > I think the easiest way to do this is to adopt a policy of removing unit > static-texts following a value textCtrl in favour of displaying the current > units in the text.
I can't imagine this not leading to a bug report. While I agree the units static text doesn't help to make typed-in units support more obvious, I don't really see how it hurts either. At least the user has an indication of the current units. Maybe a fancy wxRichTooltip[1] would be a decent solution to let users know about typed in unit support. > > If the user clicks into the control and types only a number, we’ll assume > current units and display them with the value when the textCtrl loses focus. > > We already have all the code to support this. I can clean up existing > dialogs when I fix them for the eradication of g_UserUnit. > > Thoughts? > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
