Thanks!!

Adam

In my case, when user hits "enter" he is taken to login screen - very frustrating since it happens (most often) in the middle  or in the end of data entry.

Evgeniy

firstly: "Hitting the Enter key to save and close a record is one of the most basic actions a Web user can take"    ... i would suggest this is perhaps true within your sphere, but not part of a bigger default behaviour, at least in my arena. On the web, i and my clients look explicitly for the Submit/Save type button.

secondly: something i have thought about from time to time: xaf can benefit on the web side from following the example of some of the bigger player's methods: if a web form is in a dirty state and there is a possibility of losing data, the entire state is saved temporarily and a warning is issued. If the client signals to continue with the effort, the state is maintained, else it is lost. This is critical on multi-tabbed data entry screens with multiple required fields. It is almost making me rethink the tabbed concept because of the out-of-sight--out-of-mind idea.

finally: it isn't often we catch young Dennis saying funny things, and here i jest a bit but: "In this instance, the button's XAF action is executed. But, this action is disabled and the error you received occurs as expected." Many eyebrows were raised at this statement i bet, likely including Dennis'   (hint: why raise an action on a disabled item? )    drew..

Drew,

> i would suggest this is perhaps true within your sphere, but not part of a bigger default behaviour, at least in my arena. On the web, i and my clients look explicitly for the Submit/Save type button.

My experience with Web users is that most of what they do is automatic.

I highly recommend Steve Krug's book "Don't Make Me Think" which makes this and many other useful points.

To clarify, I would say that many users hit the Enter key without thinking, expecting the form to be saved.  If it isn't saved, they hit it a few more times.  If it still isn't saved, they go looking for a Submit button, and move on happily.

Without getting sidetracked into a discussion of what constitutes thinking, I'm happy to split web users' actions into two groups: conscious and unconscious.  I don't think subtle distinctions are needed here.

The Enter key hit is unconscious, so if the next screen they see is a web site crash, they are going to be very disappointed.

Very few of them will think "I must have hit the Enter key while the focus was in a disabled item."

Also, for the record, it was not.  In MainDemo, the insertion point can be in an enabled text edit area when hitting the Enter key crashes the app.

Most of them will think "This web site sucks!"

:)

Adam

Robert Fuchs:

> Most of them will think "This web site sucks!"

99.9% of the Web sites suck - so this is not a problem ;-)

 

regards, Robert

I hear you.

I think my point was missed too.

If XAF creates a site that ignores the Enter key, that's fine with me.

If XAF creates a site that crashes when the user hits the Enter key with the selection in an enabled edit text item of a form, that presents a big problem for me.

Most important, DevExpress is working on it (thanks!) so joy all around.

Adam

good to hear they are working on it.. and no, i think we all agreed on your point, the behaviour was wrong! thanks for bringing it to our attentions.. drew..

Thanks!

I'll be using and testing XAF 8.2 extensively as soon as it ships.

Adam