Description Bug 2009f3

[JÞB]

This is REALLY annoying-

The work-around is obvious but time consuming

[dan_u · Accepted solution]

The same in 8.5.1. Shift-Return (but not Shift-Enter) does the trick.

Daniel

[RavensFan]

What is the difference between shift-return and shift-enter?

[JÞB]

is there a CAR# or is this not getting fixed?

[smercurio_fc]

---

Ravens Fan wrote:
What is the difference between shift-return and shift-enter?

---

The Return key should be the one that's next to the apostophe key (on US keyboards). The Enter key should be the one that's on the numeric keypad, if the keyboard has one. They are technically different keys, but most keyboards I've seen nowadays label both "Enter".

[smercurio_fc]

---

Jeff Bohrer wrote:
is there a CAR# or is this not getting fixed?

---

This behavior has been around for a looooong time. At least as far back as I can remember. I recall debate about whether it was a bug or not. Don't remember if there was ever a consensus. Feel like stirring up a hornet's nest on a Friday? 

[dan_u]

---

smercurio_fc wrote:

---

Ravens Fan wrote:
What is the difference between shift-return and shift-enter?

---

The Return key should be the one that's next to the apostophe key (on US keyboards). The Enter key should be the one that's on the numeric keypad, if the keyboard has one. They are technically different keys, but most keyboards I've seen nowadays label both "Enter".

---

As smercurio says usually they are treated the same, but they are technically 2 different keys. When using the "Key Down" event in LV you also have 2 different VKeys (Return & Enter). Might be important when you use that event and scan for keys.

For key navigation of controls on the other hand both keys are treated as one.

Message Edited by dan_u on 01-29-2010 04:56 PM

[RavensFan]

---

smercurio_fc wrote:

---

Ravens Fan wrote:
What is the difference between shift-return and shift-enter?

---

The Return key should be the one that's next to the apostophe key (on US keyboards). The Enter key should be the one that's on the numeric keypad, if the keyboard has one. They are technically different keys, but most keyboards I've seen nowadays label both "Enter".

---

That's pretty archane referencing to those two keys.  Older keyboards did use to call the key in the alphabetical part of the keyboard "Return" but now all seem to call it "Enter".  To me, "Return" and "Enter" are interchangeable words.  If you say "Hit the Return key" or "Hit the Enter key", you are saying the same thing.  So using them to refer to different keys makes no sense.  Dan-U's one line message is very ambiguous as a result and needed clarification.

[JÞB]

---

smercurio_fc wrote:

---

Jeff Bohrer wrote:
is there a CAR# or is this not getting fixed?

---

This behavior has been around for a looooong time. At least as far back as I can remember. I recall debate about whether it was a bug or not. Don't remember if there was ever a consensus. Feel like stirring up a hornet's nest on a Friday? 

---

Why not-  A stirred up nest of hornets can be hardly less annoying (but Shift enter is a much better solution) Perhaps only the DOCUMENTATION needs a CAR# so that users can find this solution.

[dan_u]

---

Ravens Fan wrote:

That's pretty archane referencing to those two keys.  Older keyboards did use to call the key in the alphabetical part of the keyboard "Return" but now all seem to call it "Enter".  To me, "Return" and "Enter" are interchangeable words.  If you say "Hit the Return key" or "Hit the Enter key", you are saying the same thing.  So using them to refer to different keys makes no sense.  Dan-U's one line message is very ambiguous as a result and needed clarification.

---

Well then try both keys in the description control and you'll see they are not the same.

On my keyboard the Return key just has a picture on it (arrow) while the Enter key is labelled as such.

It's a bit similar to the - sign... the one on the keypad has a different scan value than the one in the alphabetical part. Usually it results in the same ASCII character, but the scan code is different and so they can be treated differently.