KB Shortcuts for Change Case?

[phossler]

I was using the right-click menu to change the case of selected text (very useful BTW)

But I couldn't find a way to assign each of the 4 or 5 Change Case options to a KB shortcut

There didn't seem to be (at least as far as I could find) a way to do that in Editor.

Did I miss something? Or could they be added to the list of customizable KB shortcuts?


Thanks

[kovidgoyal]

https://github.com/kovidgoyal/calibr...2b3e08856eba4a

[phossler]

Thanks

I wish I understood Python (?)

Does that mean I can assign (say) Shift+Alt+L to LowerCase, and Shift+Alt+U to UpperCase?

[eschwartz]

Originally Posted by phossler

Thanks

I wish I understood Python (?)

Does that mean I can assign (say) Shift+Alt+L to LowerCase, and Shift+Alt+U to UpperCase?

Kovid's way of saying the fix was made, and will be in the next calibre release. The summary on top says yes, lowercase/uppercase/titlecase/capitalizing have all been added to the shortcuts preferences so you can assign whatever shortcuts that aren't already taken.

[phossler]

Originally Posted by eschwartz

Kovid's way of saying the fix was made, and will be in the next calibre release. The summary on top says yes, lowercase/uppercase/titlecase/capitalizing have all been added to the shortcuts preferences so you can assign whatever shortcuts that aren't already taken.

I understood the 'fix was made' part, but I was asking

a. if there are 5 shortcuts that can be assigned (one to LC, one to UC, etc.) or

b. if there was only one keystroke combo that could be assigned to bring up the current [Change Case] menu with it's 5 choices.

I just know 0.0000000% about Python (other than of course the Kovid is a whiz at it)

[kovidgoyal]

It means you can assign whatever (as long as it does not conflict with something else) you like to whichever individual action you like.

EDIT: There is a small caveat, IIRC, the shortcut system does not support the shift key, you would have to use ctrl+Alt+L instead.

[phossler]

Thanks for translating it into 'User Speak' for me

[BetterRed]

Originally Posted by kovidgoyal

It means you can assign whatever (as long as it does not conflict with something else) you like to whichever individual action you like.

EDIT: There is a small caveat, IIRC, the shortcut system does not support the shift key, you would have to use ctrl+Alt+L instead.

Kovid, I suspect you meant the shift/alt key combo, shift alone is fine - for me at least.

BR

[kovidgoyal]

Originally Posted by BetterRed

Kovid, I suspect you meant the shift/alt key combo, shift alone is fine - for me at least.

BR

Shift alone is pretty useless since it is used for typing. The problem is that in Qt, keyboard shortcuts are case independent, so ctrl+u and ctrl+U are the same thing. Not only that, the list of such items is keyboard layout dependent. For example, on typical US keyboards you press shift for +, on Norwegian keyboards you press Shift for =

This means one has to detect the presence of shift by examining the text produced by the keypress and for certain combination of modifier keys such as, for example, shift+ctrl+u Qt produces ascii control codes for the keypress text, which confuses the logic I use to detect shift sensitive characters. I have actually implemented a fix for that, though there's no way to make it fully robust, so it will work with some keyboard layouts, with some keys, on some platforms, some of the time...best to just avoid using shift.

[BetterRed]

As I said - 'shift alone is fine - for me at least' - now if it stops working I won't be able to ask - why wasn't I told? :lol:

I was sort of surprised when I discovered shift/something worked at all.

Curiosity : why can't we use shift/alt ?

BR

[kovidgoyal]

Shift alone will certainly work as a shortcut, the problem with it is that it prevents you from using the shift key while typing (I am talking about the editor here) since the shiortcut will be triggerred instead of the upper case letter being typed.

[BetterRed]

In my usage case the Code Editor window, and the S&R panel, seem to take precedence.

Due to procedural serendipity, I only use the two I assigned - shift/p (smarten punctuation) and shift/c (Remove unused CSS rules) - when there's no file in the CV window - i.e. when the EPUB is first opened.

If there's a file open in CV the shift/p and shift/c produce a 'P' and 'C' wherever the insertion point is in the CV window, or similarly in the S&R text boxes.

BR

[kovidgoyal]

Well ok, it goes the other way, the typing takes precedence over the shortcut, the point is that they conflict. I suppose you can get away with it if you are particularly careful about which shift based shortcuts you assign where.