fet-6.0.2 / no ALT-Hotkeys for menu bar

Started by uni_instructor, May 14, 2021, 11:33:17 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

uni_instructor

Dear Liviu,

the most recent version of FET 6.0.2 does not support ALT-hotkeys for the menu bar.
I have attached two screenshots of version 6.0.2 and 5.49.1

As you can see, FET 5.49.1 supports  ALT-hotkeys whereas FET 6.0.2 does not.
Applying ALT+F should open the file menu but there is no reaction.

Regards

UI

Liviu Lalescu

Hello, dear UI,

This is done by me. The reason is that on at least one platform, GNU/Linux with XFCE, my computer, the fields with accelerators appear shortened in a bad way, like "&Institu ... mation" or something like that, when using the new Qt 6. So I decided to remove the Alt accelerators in FET version 6, considering that they are not used by anybody, since anyway the mouse is much more important in the constraints, where there are no accelerators, and the mouse is needed almost everywhere.

I am so sorry for the inconvenience. Were you using much the Alt accelerators? I hoped nobody used them, and there are available the Ctrl shortcuts, which are the real useful shortcuts in my opinion.

uni_instructor

Dear Liviu,

thank your for your reply.

I don't know how many FET users are 100% mouse addictives. I use Linux at home, but Windows because of professional reasons also.
Nevertheless using keyboard shortcuts are in many ways the faster and more productive way if you know how to handle them.

As you might remember I am a friend of automating. So I wrote some (autohotkey) scripts  that allowed me to speed up the handling of FET in windows.
Most of my scripts work by generating Alt accelerator key commands for accessing the main menu (e.g. for opening both time-table windows teacher/students simultaneously).

As far as I see there don't seem to be possibilities in FET to setup user defined hotkeys. That would be useful to me. Is there a kind of a user accessible configuration list?

I am not into the details of QT6 but isn't there a possibility to define different compilation modes depending on the target architecture (e.g. target Windows - Alt accelerators enabled / target Linux - Alt accelerators disabled) ?

Regards

UI


Liviu Lalescu

Dear UI,

I think I cannot define the strings according to the environment, and I don't like the idea. The problem might appear on Windows, or some GNU/Linux users might want the accelerators.

I'll investigate if I can add the accelerators and somehow disable the elide (shortened strings with "..." in the middle), and let you know.

Liviu Lalescu

#4
Dear UI,

I searched everywhere, I cannot find what I want about Qt 6 elide of actions.

I have a solution: add a shortcut for the most important items (the actions you use). So, could you please tell me the actions you need shortcuts for and some suggestions for their shortcut? Like "Timetable view (students) days horizontal" -> Alt+S, or you sure know better than me. We can use Ctrl+Shift+letter, or the functions (F), or two letters: Alt+S,D.

Also, should I add "Ctrl+M" for generate multiple?

I cannot say I like this way of operation, but you surely know better than me.

Please let me know a bit sooner.

uni_instructor

Dear Liviu,

thank your for your reply and your offers.   :)
I spent the weekend for some reprogramming on my little helper scripts and I have been able to create some workarounds for solving my problem. :)  :)
So there is currently no need to add additional user specific shortcuts, although Ctrl+M could be useful.

Maybe you should do a poll on that issue what most used / most needed menu options of FET should deserve keyboard-shortcuts?

I  attached my helper script below (Autohotkey is needed)

Best regards

UI

Liviu Lalescu

Thank you for the good news, UI,

I think I understand what you did in your script.

I would prefer not to add more keyboard shortcuts, because of the reason of colliding translations. If a translator uses the same string (like Ctrl+G) for two actions, they will both be inactive. This is also a reason not to add Ctrl+M, because in some languages Ctrl+M is already taken and until the translator will translate the English Ctrl+M, they will both be inactive. But I will think of this.

Regards, Liviu.