QT Creator - Column Edit
-
Qt Creator 3.2 supports column editing, described as this:
Column Editing
To apply a change to several rows in a column simultaneously, press Alt, select the rows, and start typing. The text you type appears simultaneously at the cursor position on all the selected rows.
http://qt-project.org/doc/qtcreator-3.2/creator-editor-refactoring.html#column-editing
Doesn't work for me. When they say "press alt" do they mean tap it once, or do they mean press and hold? Which alt do they mean? On my system (as is very, very, very common on popular Linux window managers) left alt is the generic "drag this window" instruction to my window manager, so am I simply out of the game on column editing? When they say "select", do they mean just highlight the rows I want? Do I have to highlight the whole row, or just any part of the row?
-
Is there a way to skip lines when doing column selection?
For example, SublimeText allows to place multiple cursors anywhere in the text using Ctrl+Click. Same principle (Ctrl+Click-and-Drag, Ctrl+DoubleClick) is used to make multiple non-continuous text selections.
I wish these edit semantics were supported by all code editors.
-
Is there a way to skip lines when doing column selection?
For example, SublimeText allows to place multiple cursors anywhere in the text using Ctrl+Click. Same principle (Ctrl+Click-and-Drag, Ctrl+DoubleClick) is used to make multiple non-continuous text selections.
I wish these edit semantics were supported by all code editors.
-
Sorry for resurrecting an old thread.
I had exactly the same problem as @kgregory and managed to get something working by cloning https://github.com/qt-creator/qt-creator , removing the relevant 2 lines from src/plugins/texteditor/texteditor.cpp and building it withqmake -r ; make -j8
.
Column editing works now for me on macOS Mojave 10.14.4, the way I was used to it on Linux with Opt+Shift+Arrow keys.
Of course this overwrites the standard functionality of these combinations on a mac, but I consider column editing far superior. If overwriting the standard combinations is the only downside of this solution, I would like to propose making it default.