How to disable "sticky" selections?

[avenger]

Thank you in advance for any suggestions...

I'm looking for an editor option to disable what I am choosing to call "sticky" selections. When I use any arrow key (or Home, End, etc.) to move the caret location, I would like to have my current selection dropped/forgotten/deselected, essentially moving the selection start point to the new caret position with a selection length of 0 (zero) - similar to Windows Notepad and other text editors. Is there a way to do this? I know pressing [ESC] first will accomplish the same thing, but I want it to happen as soon as I move the caret. I have version 3.98e installed.

[jussij]

Which keyboard mapping do you have set as your current keymap

You can determine this using the Options, Editor Options menu and selecting the Keyboard panel.

Cheers Jussi

[avenger]

Thank you kindly for your response.

I have the Standard key map selected. Zeus is currently using the "out-of-the-box" config settings. Just from looking at the available options under key maps, I'm guessing either the MSVC or Simple maps might provide the functionality I'm looking for - if I assume that by directing me here, this is where I would find my answer. I'll test.

BTW, when is the store going to be operational again? Just a rough estimate...days?...weeks?...months?

[jussij]

Just from looking at the available options under key maps, I'm guessing either the MSVC or Simple maps might provide the functionality I'm looking for

I run the BriefEx mapping and the actions you describe is exactly how it works.

But I also thought Standard worked the same way

To test this out I turned on Standard and sure enough I could replicate your marking behaviour.

So there is definitely something in the Standard mapping that is doing this.

I'll take a closer look and try to find out what is going on.

if I assume that by directing me here, this is where I would find my answer. I'll test.

Trying one of the other mappings should fix this and hopefully I will also have an answer for the Standard mapping shortly.

BTW, when is the store going to be operational again? Just a rough estimate...days?...weeks?...months?

The store went down when Kagi went out of business so and that meant Zeus had to find a new store front provider.

It now does have a new storefront provider and that setup is mostly done, but the provider is taking its time before actually activating the new account

I am hoping that activation will only take a few days more.

Cheers Jussi

[jussij]

I can confirm you have found a small bug in the CUA marking code

But luckily there is a very simple work around

To fix this just do the following:

1. Use the Options, Editor Options menu and select the Keyboard Mapping panel.

2. Edit the Standard keyboard mapping.

3. Hit the down arrow and rebind that key from MoveLineDownEx to just MoveLineDown

4. Repeat the process for the up arrow key.

This issue will also be fixed properly in the next Zeus release

Cheers Jussi

PS: The shop front will hopefully be up and running by this coming Monday

[avenger]

Thank you yet again for your time, your input was a big help! I was able to create a "Modified Standard" key map after first exporting all original key maps as a backup plan. I located the functions that simple Up, Down, Right, Left, Home and End were assigned to and then re-assigned each. For example, Up is now assigned to MoveLineUp (which does NOT move line content as its name seems to imply, but is actually a "go to next line above" - I might have named the function MoveCaretUp or MoveCursorUp, but I'm getting nit-picky). Each other arrow key plus the Home and End keys are now linked to similar functions. I'll also have a look at the key map(s) you suggested.

Good news on the store - congrats.

Best Regards

[jussij]

While the keyboard function names might seem strange, there is in fact some logic in how they are name

For example the cursor movement functions are grouped by the Move prefix.

Likewise the Scroll functions are prefixed with the Scroll prefix etc. etc.

So the MoveLineUp function is actually meant to be read as follows:

1. It is a cursor Move function.
2. It works at the Line level.
3. It will move the cursor in the Up direction.

Likewise the MoveLineLeft function reads as:

1. It is a cursor Move function.
2. It works at the Line level.
3. It will move the cursor to the Left

Likewise the MoveDocumentEnd function reads as:

1. It is a cursor Move function.
2. It works at the Document level.
3. It will move the cursor to the End (of the document).

With so many functions available the idea is to try and group similar functions together.

Cheers Jussi

[jussij]

This bug is now fixed in the latest Zeus release.

Cheers Jussi