You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The classic menu in the old version is the most usable because it combines the complete s/w list, most recently used together.
The classic menu in the new version does not limit the size of the complete s/w list (i.e. no scroll bar) thus the menu will be very tall to expands to the entire screen height. Now I can certainly move some apps into sub-menus, but looking for them becomes a chore in use. Why not add back the scroll bar when the complete s/w list exceeds a number (e.g. 10, 20) ?
Similarly, the new graphic menu split the complete s/w list, recent, most used into 3 tabs all with scroll bars. That's great! It doesn't suffer the same problem as the classic menu. BUT, each time I have to click on recent. The menu should remember what is the last tab the user has selected - whether it's the complete list, most used, or recent.
Describe the solution you'd like
For the classic menu, please limit the size of the s/w list by introducing scroll bar.
For the graphic menu, please remember the tab the user has last selected.
Thank you! This is a great s/w I have been using for over 10 years!
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
The classic menu in the new version does not limit the size of the complete s/w list (i.e. no scroll bar) thus the menu will be very tall to expands to the entire screen height. Now I can certainly move some apps into sub-menus, but looking for them becomes a chore in use. Why not add back the scroll bar when the complete s/w list exceeds a number (e.g. 10, 20) ?
I tried to do some research, and unfortunately it is not possible to add a scrollbar in the context menus of windows. It would need something ad hoc, but I doubt that something exists for Lazarus/Delphi.
Similarly, the new graphic menu split the complete s/w list, recent, most used into 3 tabs all with scroll bars. That's great! It doesn't suffer the same problem as the classic menu. BUT, each time I have to click on recent. The menu should remember what is the last tab the user has selected - whether it's the complete list, most used, or recent.
For this, it should not be difficult. I would add an option to remember the last used tab in graphic menu.
Thank you! This is a great s/w I have been using for over 10 years!
Thank you very much. It's always nice to know that someone is still using software that was developed several years ago.
Is your feature request related to a problem? Please describe.
The classic menu in the old version is the most usable because it combines the complete s/w list, most recently used together.
The classic menu in the new version does not limit the size of the complete s/w list (i.e. no scroll bar) thus the menu will be very tall to expands to the entire screen height. Now I can certainly move some apps into sub-menus, but looking for them becomes a chore in use. Why not add back the scroll bar when the complete s/w list exceeds a number (e.g. 10, 20) ?
Similarly, the new graphic menu split the complete s/w list, recent, most used into 3 tabs all with scroll bars. That's great! It doesn't suffer the same problem as the classic menu. BUT, each time I have to click on recent. The menu should remember what is the last tab the user has selected - whether it's the complete list, most used, or recent.
Describe the solution you'd like
For the classic menu, please limit the size of the s/w list by introducing scroll bar.
For the graphic menu, please remember the tab the user has last selected.
Thank you! This is a great s/w I have been using for over 10 years!
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: