|
|
Post by Stefan on Feb 21, 2021 5:03:46 GMT -5
Hi George,
I've come to appreciate the (DataInsert) primitive. I use it instead of (Insert) on.
But I wonder... can you change it do that repeated presses of the key to which it is assigned toggle (DataInsert) on and off just as what happens with (Insert)?
|
|
|
|
Post by George on Feb 21, 2021 10:47:51 GMT -5
Stefan: I guess. I think now it takes a cycle of (Insert) to clear it. I suppose you'll want it to remember the previous Insert/Overtype state and restore it.
George
|
|
|
|
Post by Stefan on Feb 21, 2021 11:46:54 GMT -5
Sorry, I don't quite understand you question. Let me clarify...
By default, the <INSERT> key executes the (Insert) keyboard primitive.
Its behaviour is to turn on INS mode when pressed and revert back to OVR mode when it is pressed again, i.e. a toggle action.
I'm one of those goofy people who operates in OVR mode by default. So my typical sequence is: Type some stuff in my default OVR mode, hit <INSERT> key for INS mode, type more stuff, hit <INSERT> for OVR mode and type more stuff.
I am requesting the same behaviour from the (DataInsert) primitive as described above for the (Insert) primitive, i.e toggle the action. Currently the only other way to cancel the (DataInsert) mode is to press the (Enter) key which naturally moves the cursor away from where I'm working.
In terms of what other indicators you set, I don't really mind. The current physical aspects of (DataInsert)and how it works is fine. I just wish the key would toggle its behaviour on/off.
|
|
|
|
Post by George on Feb 21, 2021 12:04:09 GMT -5
Stefan: I was asking - when (DataInsert) toggles the mode off, should it always revert to one of INS or OVR, or should it revert to what mode it was in when (DataInsert) was 1st toggled?
Already done (as it was only a couple code lines). It will restore whatever mode it was in previously. Which should suit you just fine.
George
|
|
