sunderme
commented
2 years ago There will be no selection of incomplete behaviours. The only option is to implement more multicursor movement with well defined behaviour over corner cases.
Open fernandozucatelli opened 2 years ago
sunderme
commented
2 years ago There will be no selection of incomplete behaviours. The only option is to implement more multicursor movement with well defined behaviour over corner cases.
fernandozucatelli
commented
2 years ago There will be no selection of incomplete behaviours. The only option is to implement more multicursor movement with well defined behaviour over corner cases.
I don't very well how to well define the behavior in terms of the code. However, I can suggest the following.
Starting from the behavior I saw in version 3.1.2. If at least one multicursor is in the same line and (Home or End) is pressed, then keep version 4.2.3 behavior and remove multicursor. else, if there no multiplicity in the same line and (Home or End) is pressed, then keep version 3.1.2 behavior and move each multicursor to the (Home or End) of its respective line.
I don't know all "corner cases". The only one I knew was multiple multicursors and the same line and then (Home or End) is pressed. Please, present the others cases the community has already found, and I will be glad to help suggesting defined behaviors for each of them.
octaeder
commented
2 years ago One caveat I have seen is code expansion. One could insert something at multiple posititions and then try code expansion. But code expansion may depend on text surrounding the different cursors and may result in different expansions. It would not be possible to present different drop down lists for further selection. I concluded myself that multicursors should only be used in simple cases, with care and with not to much expectations.
Another example: You could setup two multicursors at the beginning of one word each (words should be the same). Then select the words by pressing Ctrl+D, which is currently not working (why?). So we use cursor movement to select the words. Now press Ctrl+B for example, then only the first of the two words will be surrounded with \textbf{...} (again why?). I assume it could be quite difficult to come to a (reasonable) general concept of simultanious work at multiple cursors.
fernandozucatelli
commented
2 years ago One caveat I have seen is code expansion. One could insert something at multiple posititions and then try code expansion. But code expansion may depend on text surrounding the different cursors and may result in different expansions. It would not be possible to present different drop down lists for further selection. I concluded myself that multicursors should only be used in simple cases, with care and with not to much expectations.
Yes, I remember some troubles like this.
Video 3.1.2 A:
\textbf{, autocompletes }, delete }, End, type }. Writes every single one. Perfect.\textbf, type {, autocompletes (same as before).https://user-images.githubusercontent.com/2475760/166114739-a1c83423-56db-4c81-a28b-99b357362d36.mp4
Video 4.2.3 A:
\textbf{}. Perfect.\textbf{} only for first element. No objections. Perfect.\textbf{, autocompletes }, delete }, End, goes only for first line, type }. I have to navigate each end line (Arrow Down + End) inserting each }. Not ideal.\textbf, type {, autocompletes (same as before), but now only first line, I would have to repeat for each line.\textbf, with multicursor in all lines, Shift + End, now type { and it autocompletes perfectly (It also happened in version 3.1.2, despite not presented in the video).Another example: You could setup two multicursors at the beginning of one word each (words should be the same). Then select the words by pressing Ctrl+D, which is currently not working (why?). So we use cursor movement to select the words. Now press Ctrl+B for example, then only the first of the two words will be surrounded with \textbf{...} (again why?). I assume it could be quite difficult to come to a (reasonable) general concept of simultanious work at multiple cursors.
Video 3.1.2 B:
*1: Post video verification. I wrongly typed Ctrl + V without noticing it. I did the test again by pressing { after Ctrl + V and it adds {<contents>}. Perfect.
https://user-images.githubusercontent.com/2475760/166115265-16e99016-6971-4807-93c0-0dcc383a8491.mp4
Video 3.1.2 C:
https://user-images.githubusercontent.com/2475760/166115273-edfcbb94-7190-4ed3-972b-0d154273ba4d.mp4
Video 4.2.3 B (entails "3.1.2 C"):
\textbf) Double Click first line, Multiple selections with Alt Gr + Click, , Ctrl + D (I did it twice, but the same happens when pressed once), Ctrl + B, adds \textbf{} to the last cursor position. Not ideal.\textbf{} to the first cursor position. No objections.\textbf{} to the first line. No objections. Perfect.https://user-images.githubusercontent.com/2475760/166115277-9a29a40c-bfb3-457d-a7c0-a2df41403d56.mp4
OBS: You may notice some "old ghost cursors" at the end of some line. They appeared while I was testing and training before capturing video. Probably a glitch, but I'm not concerned about them.
The next one I found out while testing. It was a nice surprise.
Video 4.2.3 D:
https://user-images.githubusercontent.com/2475760/166115718-85055477-fa37-4ce9-b20c-61be9b3d57a8.mp4
Despite Home/End behavior have been altered, I still can do some of the old tricks by adding Shift to the key combinations. I agree some old behaviors (3.1.2) were not ideals, but in my humble opinion, they seemed better than the new ones (4.2.3).
I understand and agree that drop down lists wouldn't make sense. Every time I had to insert commands with multicursors I was aware it would complete all lines, so I typed or copy-pasted them and navigate with keyboard arrows to complete not aligned ends, when it couldn't just be made with a jump to end. Sometimes even using Alt Gr + Click at the correct locations.
I really would like to have back the old Home/End behavior, but if it will bring more questions and issues than answers and solutions, I will re-adapt myself using an added Shift to my hand typing movements.
benibela
commented
2 years ago fixed in 7231acaa4023a22850f4e4a0dcfff2c8116e6b99
Selecting multirow, Ctrl + D, -- strange behavior selection last line twice --, Ctrl + B, adds bold only for last element.Selecting multirow, Ctrl + B, adds only \textbf{}. Perfect. Selecting multirow, Ctrl + B, adds \textbf{} only for first element. No objections. Perfect. Typing \textbf{, autocompletes }, delete }, End, goes only for first line, type }. I have to navigate each end line (Arrow Down + End) inserting each }. Not ideal. Copy-Pasta \textbf, type {, autocompletes (same as before), but now only first line, I would have to repeat for each line. After Copy-Pasta \textbf, with multicursor in all lines, Shift + End, now type { and it autocompletes perfectly (It also happened in version 3.1.2, despite not presented in the video).
did not change that
Describe the feature and the current behavior/state
I would like to have an option to select between two behaviors of multicursors: 1 - The old one until version 3.1.2 2 - The new one of version 4.2.3
Who will benefit with this feature?
Every user that learned how to use the old behavior and lost that skill.
Any Other info
Details of old and new behavior were presented at #2292.