
You can then press Shift-Command-Z to Redo, reversing the undo command.

Bottom line is I think the functionality that several people have requested is potentially easy to implement.

A user could hit a key sequence and it would be as if they hit several keys. That being mapping a single key to do several operations, not just one. Personally, having been fluent in vi and emacs, where I did not have to de-home hands off of the main portion of the keyboard, it would be so very productive to have the ability to map keys (far more than you currently offer).ĭepending upon how the mapping were implemented, one could really have a whole MACRO functionality. Whether it be a user familiar key sequence like vi, emacs, or some other editor. If there was access to the cursor movement functions via the Menu Shortcut Key preference window, a user could map a key sequence to a function that is called for the 'Key-Arrow-Right'. There is no method of moving cursor one character to left without DE-HOMING hands to use an arrow key or the mouse. The cursor is now at BC-15 - For entry of an attribute.

What exists as a very limited subset, is USER mapping ability of keyboard event to function call via the Menu Shortcuts Keys.ĭepending upon internal code modularity and methods of implmentation, these requests would be a very simple change to a single code file.Ġ123456789 0123456789 0123456789 0123456789Įvent sequencing line, cursor at BB-13Ĥ) Line BC: just finished typing 'Key-Enter' and the tag completes with its closing tag.ĪRG. (PgUp key invokes OxygenXML-internal-code to move the view-port of currently active window context to view items occurring before the current view-port location)

In the request for movement in the code completion menus, there exists some code functionality that receives the movement of the or (a general keyboard event) and recoginzes the context (the code completion menu) and calls the appropriate function to effect the selection movement within the completion menu.Īll the functionality exists. I believe that there is an important underlying issue that resolves the above and a multitude of other potential requests and already exists !Ĭore issue: provide extensive access to the code function call to the Menu Shortcut Keys mapper.įundamentally an event, a keystroke, is received, which is then mapped to a function call, which implements the users request. This will be analyzed and if found appropriate, it will be implemented in a future version of Oxygen (long term). I have logged your request to our issue tracking tool.
