I was using those, too. But when I click into a word between them and I wan to hold command+arrow to jump to the next underscore (say to highlight the word to change it or delete it quickly) underscores are treated as part of the work or string… where hyphens will act more like a space or break in text and so you can jump quickly from one word to the next. My workflow is like this…
click anywhere in widget name
hold CTRL/CMD and use arrow keys to jump to the start or end of a particular word such as “save” in “command-commandBar–save”
adding shift to my modifier (so now SHIFT+CMD+Arrow) I can select just that word (the name of the object that is unique being ‘save’) to “delete”
now the widget name reads as “command-commandBar–delete”
I am using the “–” to denote what comes after it as being the object’s unique ID versus what comes before as the object type/structure/layout shorthand.
PROBLEM: In using the underscore, you have to use the mouse to click directly onto the spot you want to start the cursor, then hold shift, then click the end of the word (or drag along the text with RIGHT-CLICK)
PROBLEM: if I don’t use underscore, that problem is solved, but now I don’t have the visual cue of the double hyphen to guide my eye to the unique ID i’ve established for the widget.
I totally get autocorrecting to an extended hyphen in most cases. But every other UI / OS gives you the option to customize autocorrections like that, or turn them off completely. Axure doesn’t have any preferences specifically available for modifier keys, autocorrect, or anything else that might help with either problem.
It’s just frustrating because it gives us the ability to use freeform text to create a naming system that makes sense to the user, and I can even search the widget names based on something like “–” to find unique objects, or even “–save” to find that quickly as opposed to “–savingModal”.
I guess it’s a niche experience issue. I just find it strange when a UI is like, “here’s an open field to enter something custom that makes sense to you!” and then autocorrects certain characters and gives no option to turn it off.
To me, as a UX practitioner, nearly anything that is automated by the system, should be able to be switched to a manual process (or be disabled) by the user if they wish (with some exceptions where the automation is necessary to the core function of the workflow or something).