WizardStan
Mega GP Mania
- Joined
- May 24, 2008
- Messages
- 16,731
So disable it. You don't need a compose key, turn that functionality off.In my opinion, any keyboard that is blocking the shift-enter combination is utterly useless
So disable it. You don't need a compose key, turn that functionality off.In my opinion, any keyboard that is blocking the shift-enter combination is utterly useless
According to that argument keyboard layout is always irrelevant since you can remap stuff yourself.So disable it. You don't need a compose key, turn that functionality off.
No it doesn't. The compose key wasn't labelled. If you aren't using it you lose nothing by changing it.The default keyboard layout is important because they all get labels. Also you're likely to use all of the keys for their labelled purpose at some point in time. Changing a labelled key introduces the potential for problems.According to that argument keyboard layout is always irrelevant since you can remap stuff yourself.
I think you're exaggerating how common it is. I can't remember ever encountering such a shortcut, and googling for it brings up very few hits. Powerpoint uses it for a "soft return", whatever that means.What were you using when you found the need to hit shift-enter, and why didn't you report it as a bug when you found it didn't work as you expected?however the default layout should be as good as possible and shift+enter is a very common combination
Shift-Enter is used in pretty much any application that uses enter for submit so that you can insert newlines.I think you're exaggerating how common it is. I can't remember ever encountering such a shortcut, and googling for it brings up very few hits. Powerpoint uses it for a "soft return", whatever that means.What were you using when you found the need to hit shift-enter, and why didn't you report it as a bug when you found it didn't work as you expected?however the default layout should be as good as possible and shift+enter is a very common combination
There are many word processors that use shift + enter for a regular line break while using enter by itself for a paragraph break (to break from the current paragraph and begin a new one.)I think you're exaggerating how common it is. I can't remember ever encountering such a shortcut, and googling for it brings up very few hits. Powerpoint uses it for a "soft return", whatever that means.
What were you using when you found the need to hit shift-enter, and why didn't you report it as a bug when you found it didn't work as you expected?
I still don't understand why it needs to be tied with shift when Fn + enter could be easily used instead. Please see my last post for a several good examples of known and common shift + enter usages. Yes, your schema only uses one of the shift keys but I still feel that should be strongly advised against for a default configuration.Compose Mode is now Left Shift + Enter only.
Either Left Shift + Enter or Fn + Enter would work. I prefer the former since it's like it was on the Pandora is all.I still don't understand why it needs to be tied with shift when Fn + enter could be easily used instead. Please see my last post for a several good examples of known and common shift + enter usages. Yes, your schema only uses one of the shift keys but I still feel that should be strongly advised against for a default configuration.Compose Mode is now Left Shift + Enter only.
That only works if you only need three special letters, or at least at most three that are common. In Dutch, you don't need any special letter frequently, but you do need ä, ë, ï, ö, ü, á, é, í, ó, ú, à, è, ù, â, ê, ô, œ and ç every now and then, none of them much more commonly than the others. Having three dedicated extra letters does not solve much.Or, with an intl layout, its a letter of its own. ÆØÅ ÖÜÄ etc all day. It doesnt require re-learning anything, its fast, and its one key.
Such as?Shift-Enter is used in pretty much any application that uses enter for submit so that you can insert newlines.
"on many editors" doesn't tell me a lot. I'm not asking hypotheticals, I'm curious for specific applications. Which ones on the Pandora have you used that caused problems and why didn't you report it as a bug when it didn't work?There are many word processors that use shift + enter for a regular line break while using enter by itself for a paragraph break (to break from the current paragraph and begin a new one.)
It's used in many many chat and messaging programs to break to the next line where by itself sends the text. I've seen it used in email clients to save to drafts where as a solo stroke breaks to the next line as normal. Other clients I've seen use it as a faux paragraph break or vice versa where it emulates word processors.
I've seen other editors that use shift + enter for a carriage return (where it goes down to the next line but at the same column position it was previous) or programming orientated editors where it closes a block and positions the caret to begin another, which is sort of reminiscent of the word processor usage, but more programming specific that usually respects indentation, etc.
It's also normally a perfectly configurable combination in many other programs and games that let you customize their functions and controls. Therefore it seems like a rather bad idea to clobber this be default, especially when there exists an Fn key or the suggestions others have made.
If the two Right Shift keys, one on the shoulder and the other on the keyboard part, have different scancodes, then Fn + Right Keyboard Shift for Compose Mode does make sense. I am reluctant though to have Fn + combos on Shift keys. That includes Caps Lock also. I'd prefer all three Shifts were Shift keys only to keep it pure and honest. Fn + Tab for Caps Lock seems more apropos and Fn + Pyra for Escape may work out as well. Back to Left Shift + Enter for Compose Mode too, possibly.I think it makes more sense to have the default Compose key on Meta/Fn/AltGr+RShift (not the shoulder button shift, but the right keyboard shift). That way we have a reason to put a "Compose" label on that key, and it becomes a sensible key to use as a dedicated Compose key -- power users don't need two shift keys on the keyboard itself, since L1 is more effective as shift anyway.
I think it makes more sense to have the default Compose key on Meta/Fn/AltGr+RShift (not the shoulder button shift, but the right keyboard shift). That way we have a reason to put a "Compose" label on that key, and it becomes a sensible key to use as a dedicated Compose key -- power users don't need two shift keys on the keyboard itself, since L1 is more effective as shift anyway.
If the two Right Shift keys, one on the shoulder and the other on the keyboard part, have different scancodes, then Fn + Right Keyboard Shift for Compose Mode does make sense. I am reluctant though to have Fn + combos on Shift keys. That includes Caps Lock also. I'd prefer all three Shifts were Shift keys only to keep it pure and honest. Fn + Tab for Caps Lock seems more apropos and Fn + Pyra for Escape may work out as well. Back to Left Shift + Enter for Compose Mode too, possibly.
What's wrong with the term "power user"? It sometimes makes sense to distinguish different types of users:Nothing personal, but I always get a chuckle out of the expression "power users". Such a silly, devaluing label hatched from the media outlets. :rolleyes: :lol:
Your Dutch must be different from mine (i.e. Flemish ). I don't recall ever writing those in Dutch.In Dutch, you don't need any special letter frequently, but you do need ... â, ê, ô, œ and ç every now and then
The "wrong" here is the categorizing people which means to say one group is more than another because of something. "Lusers" as you put it versus "Powers". All may be purchasers once or many times and all will use the product or they won't. That's not the error in thought here and has nothing to do with how simplistic the GUI will be for the skillset of the person staring into the monitor. What is is one set is devalued over another because of the inferiors inability or desire to learn.I think it makes more sense to have the default Compose key on Meta/Fn/AltGr+RShift (not the shoulder button shift, but the right keyboard shift). That way we have a reason to put a "Compose" label on that key, and it becomes a sensible key to use as a dedicated Compose key -- power users don't need two shift keys on the keyboard itself, since L1 is more effective as shift anyway.
If the two Right Shift keys, one on the shoulder and the other on the keyboard part, have different scancodes, then Fn + Right Keyboard Shift for Compose Mode does make sense. I am reluctant though to have Fn + combos on Shift keys. That includes Caps Lock also. I'd prefer all three Shifts were Shift keys only to keep it pure and honest. Fn + Tab for Caps Lock seems more apropos and Fn + Pyra for Escape may work out as well. Back to Left Shift + Enter for Compose Mode too, possibly.
I would make the right keyboard shift actually be a different key (Super, perhaps), so it gets a different scancode, and make the default configuration so that it works like a third shift key.
I don't really see why Shift has to remain more "pure and honest" than, say, Enter or Space. It's a small keyboard, we can't have too many keys with just one label.
What's wrong with the term "power user"? It sometimes makes sense to distinguish different types of users:Nothing personal, but I always get a chuckle out of the expression "power users". Such a silly, devaluing label hatched from the media outlets. :rolleyes: :lol:
- lusers (unskilled and not willing to learn)
- noobs (unskilled but willing to learn)
- regular users (skilled, knows how to do most of the normal tasks)
- power users (very skilled, tries to get the most out of it)
Ideally, something (an application, a hardware design, whatever) works well for all types of users, but that is not always possible. Sometimes choices have to be made. One of the differences between the GNU/Linux (FOSS) way of doing things and the Apple/Microsoft/Sony/Nintendo (proprietary) way of doing things is that the former tends to optimize for power users while the latter usually optimizes for lusers.