Kristyne McDaniel wrote: > Paul, > >> These particular users need to be trained. I would be >> fumingly annoyed at a program that forcefully changed >> the caret position from where I purposely placed it. > > I disagree. If it is a custom program that they're going to be living in all > day long to do their work, accommodating a few oddball requests is a > worthwhile thing.
It works against the standard Windows UI behavior[1], so it is just wrong. Obviously, you do what the client asks, but you gotta do your best to explain why it is the way it is so they can decide to press for this "feature" with eyes open. One of my apps has the oddball behavior that turns capslock on when entering a particular textbox, and turning it back off when exiting the textbox. The client insisted on this because "the old software worked that way". I put it in and they were happy, but a few newer hires have mentioned how wacky this is, to which I must agree. > I would, however, make it an optional behavior that can be turned on/off on > a settings dialog so that the native behavior is still available to users > that want it. Yes, that would definitely be the way to do it. [1] Granted, "Windows standards" is an oxymoron. _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
