|
I think that is part of the Windows text box control. Same if you press backspace in an empty text box.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
That doesn't happen on any app I've got, one's I've writren or otherwise
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
It does if you use the Win32 edit control directly. MS just disabled the beep by default in their higher level libraries. Because apparently, only Win32 is worth of the beep.
Jeremy Falcon
|
|
|
|
|
Check it out. Pulled up some Win32 code of mine where I had to explicitly stop the beep. Just to preface the code so it makes sense, it's C code and I used typedefs for intrinsic types for this app so I didn't have to change out my entire app if I swap from 32, 64, whatever bits, change compilers with diff implemenations, etc. in the future.
Anyway...
static numeral CALLBACK
subprocEditControl(HWND hWnd, uint32 uMessage, WPARAM wParam, LPARAM lParam, unumber uIdSubclass, dword dwRefData)
{
...
switch(uMessage)
{
case WM_CHAR:
if(wParam == VK_TAB) return 0;
...
}
...
return DefSubclassProc(hWnd, uMessage, wParam, lParam);
}
Jeremy Falcon
modified 10-Nov-17 11:50am.
|
|
|
|
|
She uses the ENTER and BACKSPACE keys interchangeably - they're close enough on the keyboard for that to be acceptable for any standard user.
Remove one or both keys from keyboard.
Problem solved.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
The app beeps when a textbox has focus and the enter key is pressed. I didn't design that 'feature' but I will have to override it.  Try it...put two textboxes in a winform and try to navigate between them using Enter or Shift+Enter. It baffles me how she manages to 'get around' in other programs using just the Enter key. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
It it a WinForms thing specifically? My WPF apps don't to that
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
I'll be dam... It DOES do that in WinForms, but not in WPF.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Cool, good to know...I'll add it to the list of possible resolutions! Thanks for testing!
"Go forth into the source" - Neal Morse
|
|
|
|
|
I think WPF doesn't use the Common Controls Library, which WF uses. The beep is a part of that.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Brisingr Aerowing wrote: WPF doesn't use the Common Controls Library
None of WPF's controls or dialogs use the built-in controls or dialogs. They're all emulations of the standard controls, essentially built on DirectX.
Software Zen: delete this;
|
|
|
|
|
I don't know if I should tell you this, but there is some kind of bug in .NET, that happens once in a blue moon, when you use the enter key to enter text in a textbox: Every now and so often the cursor will jump to the next tab stop when you hit enter on a WPF textbox, but the text is NOT entered. If this is a WPF textbox: Good luck! I hope I didn't spoil your evening!
Get me coffee and no one gets hurt!
|
|
|
|
|
Communication man.
Sometimes people don't know what they're asking for (time wise). It's up to us to tell the customer what it'll cost in time. They may be under the impression it's a 3 second change and no big deal.
Some of the biggest executives of some of the biggest companies in the world can be the nicest people ever if you just don't get so afraid to talk to them that you never communicate. This is how unrealistic expectations happen.
Communication. Communication. Communication.
Jeremy Falcon
|
|
|
|
|
First response
No it should not be done because it is non standard functionality
Second response - when they express no interest in standards
It will cost $n and $n+10% every upgrade we supply to customise the application for you.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
The point still stands, explain this to them... communication. People skills. But, if it comes off as smug it'll never go over well. It's called human nature bro.
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: communication. People skills.
Some of those peripheral skills a well rounded developer requires but so few of us work on. Self employed will tend to acquire these a dammed sight quicker than corporate developers.
It seems by going back to corporate I have reverted to a grumpy old bastard.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: Some of those peripheral skills a well rounded developer requires but so few of us work on. Self employed will tend to acquire these a dammed sight quicker than corporate developers.
Exactly
Mycroft Holmes wrote: It seems by going back to corporate I have reverted to a grumpy old bastard.
Been there, done that brother. 
Jeremy Falcon
|
|
|
|
|
|
I think I would need to know more about the app to come to that conclusion.
Long ago data entry into computer applications did use the enter key. Exclusively. And data entry was a job and some people were very good at it. Fast and precise.
In terms of an app I see no reason why the enter key shouldn't be used, unless it precludes some other functionality. Which would be a cause for a problem. For example do not some text controls allow one to enter multi-line text, which requires the enter key. Seems like that could be a problem. That of course doesn't mean that it should be used instead of the Tab key.
Other than that I would also want to know what this customer represents to the company. For example if one has a very useful beta tester with a lot of domain knowledge for the target industry I would want to keep her very happy. Even with non-standard functionality (especially since non-standard for me might in fact be standard for the industry.)
|
|
|
|
|
jschell wrote: I would also want to know what this customer represents to the company
This should only control how polite you are, even someone with a lot of domain knowledge should not influence an industry (software not domain) design standard. If they are your ONLY customer then that may be different otherwise you end up with a myriad of different versions to meet non standard requests.
I got the impression this is neither a high speed data entry program nor is the user particularly knowledgeable so customisation seems unreasonable.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: This should only control how polite you are, even someone with a lot of domain knowledge should not influence an industry (software not domain) design standard
In terms of domain knowledge they should have a better understanding of what users in that industry (not tech/UI) expect. So their knowledge might drive to the point that users in that industry expect different behavior. There are two sides to that in that the user might be mistaken but it could also be because an alternative product used widely in the industry (not the one being developed but rather as an alternative or even competitor does that.)
Additionally my impression was that this was an alternative and not instead of. In my experience getting reasonable and frequent feedback from actual external customers is something that must be treasured because most users are not interested and do not have the time. Even when they are incentivized with cheaper or free products feedback is seldom forthcoming. The description suggests that possibility. Those people must be coddled.
Finally for me I deliver domain solutions that strive to meet to needs of the problem domain as the users expect. That has and will continue to mean compromising all parts of application implementation to some extent to deliver products that most fully meet what they need, expect and even desire. All of those are important to not only deliver something that works as they want but also sometimes items that are not even used but which might help is selling the product to a new customer group.
Mycroft Holmes wrote: I got the impression this is neither a high speed data entry program nor is the user particularly knowledgeable so customisation seems unreasonable.
My explanation there was not complete. The point is that due to past experience this is something that one person or a group of people might expect and be comfortable with. That could drive their expectations now (even though process now is different.)
|
|
|
|
|
jschell wrote: Long ago data entry into computer applications did use the enter key. Exclusively. And data entry was a job and some people were very good at it. Fast and precise.
Had a bunch of people two jobs ago who were around since who-knows-when and had ingrained habits that I had to compensate for.
The weirdest one was Hitting the space bar before typing anything else in the text boxes.
I have no idea what system they were used to that needed that...to wake it up, I guess?
But I ended up having to Trim every bit of text before sending it off to the database.
|
|
|
|
|
GenJerDan wrote: But I ended up having to Trim every bit of text before sending it off to the database.
But I have done that just because users type spaces accidentally as well.
|
|
|
|
|
Jeremy Falcon wrote: Sometimes people don't know what they're asking for (time wise). It's up to us to tell the customer what it'll cost in time. They may be under the impression it's a 3 second change and no big deal.
This is certainly the case here...the user in question seriously thinks that we designed the program to beep on Enter, finds it annoying, and simply asked if we could make it stop. Even my ex-programmer business partner assumed it's just a trivial thing to fix...just wave the magic wand...we can do anything! 
"Go forth into the source" - Neal Morse
|
|
|
|
|
kmoorevs wrote: Even my ex-programmer business partner
Hah so he has turned to the dark side and become a salesman.
Never underestimate the power of human stupidity
RAH
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
My thoughts exactly! Unfortunately, trying to explain standard functionality to an end user, and even to some colleagues is like talking to a wall...they believe that anything is possible...and easy...and can be done by tomorrow!
