Is there any reason why the shift-option-arrow key combinations don't work
with the QScintilla editor on OSX?
Left-arrow and right-arrow work as expected to shift the cursor left and
right.
Adding the option or command modifier keys works too - shifting the cursor a
whole word or a whole line at a time.
Adding the shift modifier only works by itself or with the command key.
I.e.: I can select one character at a time or an entire line at a time. I
can't select a word at a time. In Windows, the equivalent would be
shift-ctrl-left/right arrow.
Is there some function in QScintilla that reserves this key combination?
I use this way of navigating all the time when editing, and the lack of this
functionality is the main reason why I've been reluctant to activate the
QScintilla editor.
I swear I submitted this as a bug previously, but now I can't find it so
maybe I only dreamt I did?
--
Sent from: http://forum.openscad.org/
I'm not an mac user.
But we have this wiki, which may be a little out of date (note to self!).
It has a link to an Apple page which says:
Option–Shift–Left Arrow: Extend text selection to the beginning of the
current word, then to the beginning of the following word if pressed
again.
Option–Shift–Right Arrow: Extend text selection to the end of the current
word, then to the end of the following word if pressed again.
Admin - email* me if you need anything, or if I've done something stupid...
Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.
Sent from: http://forum.openscad.org/
oops forgot to link to the wiki
https://github.com/openscad/openscad/wiki/Keyboard-Shortcuts
Admin - email* me if you need anything, or if I've done something stupid...
Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.
Sent from: http://forum.openscad.org/
Thanks Michael.
Those shortcuts work in the standard editor, but stop working as soon as I
activate QScintilla. It's as if QScintilla is hijacking those keycodes but
not doing anything with them.
This has happened since the new editor was introduced, and it has never
really bothered me to have to stick to the old editor until now. I was
hoping it would have been fixed eventually but there has been a long gap
between the last two releases so I guess it might be a long wait for this
one.
Incidentally, the following excerpt on that page is a little confusing:
Overview over OpenSCAD keyboard shortcuts and Mnemonics
…
C - Ctrl (Cmd on Mac)
S - Shift
A - Alt
M - Ctrl on Mac (Windows/Meta key on others)
It took me a while to understand what it was trying to say. I think it would
read better if it listed the 'normal' keybinds first in all four cases
(C=Ctrl, S=Shift, A=Alt, M=Meta/Windows) and then add the Mac equivalents
after (use Command instead of Ctrl and use Ctrl instead of Meta).
At the moment, it looks like C and M are both Ctrl until you read the text
in brackets.
--
Sent from: http://forum.openscad.org/
On 05.07.19 10:22, QuackingPlums wrote:
This has happened since the new editor was introduced, and it has never
really bothered me to have to stick to the old editor until now. I was
hoping it would have been fixed eventually but there has been a long gap
between the last two releases so I guess it might be a long wait for this
one.
The old editor will go away pretty soon.
If you see problems with something, just hoping it will be fixed
eventually is not the most reliable option. If you want to see
something fixed, please make sure there's a github issue created.
It's true that some issues are waiting a long time before
they are fixed. But with no github issue, the basic assumption
is that no problem exists.
ciao,
Torsten.
Thanks Torsten,
I did think I submitted an issue but I can't find it now, so either I just
dreamed it or I got distracted before hitting submit. I meant that it would
be a long wait because if it wasn't already on the radar, then I'll have to
create a new issue and wait for whenever the next release comes. Hopefully
the old editor won't go away until this is fixed.
I'll create another now - I just wanted to check that I hadn't missed
something before potentially duplicating something that had been discussed
before.
--
Sent from: http://forum.openscad.org/
Ok, I think I found a thread and a commit that might be in direct conflict
with standard OSX key behaviour.
The commit here looks like a PR to assign the shift-option-arrow keys to
some 'number precision extension'?
https://github.com/MikeBenza/openscad/commit/2af1dbb7a1833f27527112bfb97416681cd3ad03
Am I reading that right? It's been too many years since I've been a coder!
Issue 2885 seems to cover this scenario:
https://github.com/openscad/openscad/issues/2885
It looks like we keep flip-flopping between hijacking option-arrow and
shift-option-arrow. Both of these are standard/reserved combinations but the
last few comments seem to imply that we have to live with one of these
combos being hijacked, and evidence would suggest that the
shift-option-arrows combo lost out.
Is this interpretation correct? Are we really saying that we're losing this
functionality and sticking two fingers up at OSX users, especially with the
basic editor being deprecated? That would be similar to hijacking
shift-ctrl-arrows on Windows!
--
Sent from: http://forum.openscad.org/
In any case, here is my new issue:
https://github.com/openscad/openscad/issues/2984
I've also added a comment and link to the associated issue 2885
https://github.com/openscad/openscad/issues/2885 .
--
Sent from: http://forum.openscad.org/
On 05.07.19 15:31, QuackingPlums wrote:
In any case, here is my new issue:
https://github.com/openscad/openscad/issues/2984
Thanks, I've added both issues to the brand new "Next Release"
project, so it will get at least some attention. Platform
specific issues are always extra problematic and for MacOS
even more so due to Apple being massively hostile towards open
source devs.
The hope is certainly to have not that long to the next release
but in the end it depends on how much time people have.
ciao,
Torsten.