It's not a bug, but so far, shortcuts are asigned by positions. Thus, if I move a clip, the asigned shortcut is applied to another clip, not to the original.
Will there be some way to assign the shortcuts by clip name and not by position?

No plans to accommodate that that I know of (not that that couldn't change).

Shortcuts are assigned to the clip number, not the clip action/description. It has always worked the way it currently does. I can see how it might cause some confusion when reorganizing things in the clip editor, though. But this is the first time I remember anyone bringing the issue up. Perhaps people don't do a lot of clip reorganization. :D

And as names/actions for clips are user assignable and easily changed, using that approach would end up with something broken just as easily.

You are assigning a shortcut to clip number 1's actions, not assigning a shortcut to an action or name.

@RbnJrg: You can easily assign shortcuts to 40 Clips (and even more), so keeping an eye on the order is probably not that scary.

My setup works perfectly for me, and my hands trigger these combinations themselves. Clips 31 to 40 serve as temporary for me and therefore I assigned shortcuts to them from the numeric keypad.

As Diap says, if we reorganize the clips, we lost all our shortcuts.

In the sigil_clips.ini there are the names and the numbers of the clips and in Sigil.ini, we have the associated shortcut to the clip numbers. So, maybe it could be possible to assign, in Sigil.ini (or in another .ini file), where we can read, for example,

120\id=MainWindow.Clip1
120\keySequence=Ctrl+Num+*

the "id" to the name of the Clips that are stored in sigil_clip.ini. Maybe an asociation between MainWindow.Clip1 and the respective name in the sigil_clip.ini could do the trick.

Thanks for sharing your method, Becky. Yes, there are ways to minimize the fact that one can't move the clips, but we would have more freedom if Kevin and Diap could link all the info already available.

By the way, that woud be a nice new feature that would do Clips in combination with shortcuts even more practical and powerfull.

It is not that easy. All other actions registered for keyshortcuts have fixed, translatable strings representing their functions known at compile time. There is a one to one mapping of action and function.

For clips, we do not know what name/function they will have only an action number (by clip number) at compile time. So using our current mechanism we assign shortcuts to actions/functions which are clip numbers.

Nothing else is available at compile time.

This is why and how we handle keyboard shortcuts for the first 10 plugins in the same way.

This is not something I am interested in changing. BeckyEbook's approach seems to make the most sense to me.

I did wonder about that, but I didn't pursue because I use the menu and arrow keys to access Set Semantic, Rename etc.

Is there a way to give the panels keyboard focus using the keyboard? And see at a glance which panel has keyboard focus?

BR