Community
Participate
Working Groups
This form says "Enter bug" and some might not call this a bug, but I can find no better option on Help Contribute to report this apparent design defect. Despite Product and Version above, this product is Eclipse IDE for C/C++ Developers Version: 2018-12 (4.10.0) Steps: 1) On C source line pig=vec3(.15,.15,.15)*2; double-click between the first 1 and 5 at caret here https://i.imgur.com/4fVbca8.png - see 15 selected. 2) Double-click between ) and * here https://i.imgur.com/iV2t6kk.png - see .15,.15,.15 (and not ), oddly) selected 3) Try various keyboard commands for the same effect. Expected: one found. I'm assuming (given lack of documentation) that this product is supposed to be fully operable with keyboard. Observed: none found.
The C/C++ Editor component of "Eclipse IDE for C/C++ Developers Version: 2018-12 (4.10.0)" is provided by "Eclipse CDT Version 9.6.0"
This works for me with Alt + Shift plus arrow keys. See https://help.eclipse.org/2019-12/topic/org.eclipse.platform.doc.user/reference/ref-keybindings.htm and find "Expand Selection to"
> This works for me with Alt + Shift plus arrow keys. Not for me. Unless you mean a handful of them. Which sounds unlikely since yes obviously anyone can extend a selection on character at a time, but surely the point of the mouse command it to avoid that need.
With my cursor in the middle of an identifier then Alt Shift Arrow selects the entire identifier, same as double clicking on the middle of the identifier.
> With my cursor in the middle of an identifier That's not following the Steps given for this issue.
Good point, not identical, but like Bug 558564 I suspect it is a lack of specificity in documentation that there is no exact match between keyboard and mouse actions. As mentioned in Bug 558508 there is a double click handler code that handles these code paths and the flow for keyboard is different. Would you like to provide some patches in this area, either to firm up the documentation or add new features? You have done quite a deep dive on the intricacies and subtilities across a wide range of bug reports here. It would be great if you could follow through and improve it for everyone. Let me know if you need any pointers. In the mean time this is really a platform thing too along with the other items.
> I suspect it is a lack of specificity in documentation that there is no exact match between keyboard and mouse actions. I think the more likely cause of this mismatch is a lack in the code. > Would you like to provide some patches in this area, either to firm up the documentation User docs? No. I see little value in documenting what looks to me like undesigned (perhaps even undefined) behaviour - which will hopefully be remedied. Design docs? Sure. But I don't see any. > or add new feature To the code?? Goodness! You would not want this end user touching this code! :)
