Pressing Cancel in a lookup window (Business Partner Info,
Invoice Info, Order Info etc.) clears the triggering field and sets
the state of the record to modified.
*** Status set to PENDING *** If the issue solved, please CLOSE
this request - otherwise set the status back to OPEN (we only
check OPEN items). If there is no reaction within a week, the
system will automatically CLOSE it. To speed up response time,
you may want to consider a support agreement.
***
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I really don't get it, why should I open a lookup window to clear
the field, when I can use backspace or delete, directly in the
field? This is really misleading, as long as cancel means
cancel, not clear.
If I open the lookup window by mistake and want to close it, I
shouldn't press cancel? Honestly, I think this is a usability
issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
backspace will not clear a lookup field in all instances. If you
open the window in error just close it. The cancel means you
want to cancel the selected entry which is the value you
entered. If you do not like it functioning this way you can
change the source code
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Correct me if I'm wrong: if there is a filled field, with a good
value, and a user wants to check something or wants to modify
the value and changes his/her mind, the original value in the
field should be left unchanged, and it's the user responsability
to clear or modify that field. Clearing it without notice, together
with saving it, also without notice, when navigating to another
record, leads to unwanted and messy results.
Take the numeric field, for example. If there is a value in it,
opening the calculator and pressing Escape (shortcut for
cancel), leaves the value untouched.
I hope I'm not the only one believing that this is the correct
behaviour.
It's not about me, I can live with it, and yes, I can change the
source code, but the average user expects some consistency,
inside compiere and compared to other applications out there.
Thank you for your patience,
Alin Vaida
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=329831
That is the way that you clear teh field. IF you do not want to
have that happen, do not select Cancel
Logged In: YES
user_id=329831
*** Status set to PENDING *** If the issue solved, please CLOSE
this request - otherwise set the status back to OPEN (we only
check OPEN items). If there is no reaction within a week, the
system will automatically CLOSE it. To speed up response time,
you may want to consider a support agreement.
***
Logged In: YES
user_id=23294
I really don't get it, why should I open a lookup window to clear
the field, when I can use backspace or delete, directly in the
field? This is really misleading, as long as cancel means
cancel, not clear.
If I open the lookup window by mistake and want to close it, I
shouldn't press cancel? Honestly, I think this is a usability
issue.
Logged In: YES
user_id=329831
backspace will not clear a lookup field in all instances. If you
open the window in error just close it. The cancel means you
want to cancel the selected entry which is the value you
entered. If you do not like it functioning this way you can
change the source code
Logged In: YES
user_id=23294
Correct me if I'm wrong: if there is a filled field, with a good
value, and a user wants to check something or wants to modify
the value and changes his/her mind, the original value in the
field should be left unchanged, and it's the user responsability
to clear or modify that field. Clearing it without notice, together
with saving it, also without notice, when navigating to another
record, leads to unwanted and messy results.
Take the numeric field, for example. If there is a value in it,
opening the calculator and pressing Escape (shortcut for
cancel), leaves the value untouched.
I hope I'm not the only one believing that this is the correct
behaviour.
It's not about me, I can live with it, and yes, I can change the
source code, but the average user expects some consistency,
inside compiere and compared to other applications out there.
Thank you for your patience,
Alin Vaida
Logged In: YES
user_id=329831
That is the way the code works. But that is the great thing
aabout Open Source, if you do not like it you can change it