Missing TSpeedButton keyboard shortcuts

Andrew · 2014-05-21 01:26

All these 6 instances are missing keyboard shortcuts (although the first 3 can share the same one):

__________

Of the following 3 Help buttons, the first one has a shortcut i.e. F1 while the other two don't. Moreover, all three should clearly mention that they link to or will launch Online Help in their tooltips:

den4b · 2014-05-21 17:17

I've added it to the list.

This is a low priority because most of these are auxiliary actions, i.e. they do not provide functionality that cannot be accessed some other way.

However, "Translit Alphabet" button is a main action, it might be better to convert it to a normal tab-accessible button.

Andrew · 2014-05-27 01:55

den4b wrote:

However, "Translit Alphabet" button is a main action, it might be better to convert it to a normal tab-accessible button.

I agree that the others aren't as high-priority.

However, can you add the tooltips and F1 shortcuts for the two Help buttons at least, to match the third one? That way all of them will look and behave similarly. Please also ensure the tooltips for all three state "Online Help (F1)" so the user knows they are all external web resource links.

den4b · 2014-06-04 15:29

Ok, "Online Help (F1)" will be added.

Andrew · 2014-08-13 23:58

A minor issue with 6.0.0.1 alpha - all TSpeedButton menus now no longer have underlined keyboard accelerators as before:

Also, can you make the popup menu not hide the Alphabet button on the Translit rule? As you can see neither the Scripts nor Options menus behave this way.

Last edited by Andrew (2014-08-13 23:58)

den4b · 2014-08-18 23:41

Keyboard accelerators have been added to all context menus in v6.0.0.3 Alpha.

Appearance of the popup menu is connected to a single point, which is usually either the top left or the bottom left corner of the connected component (button). In both cases the popup menu can cover the connected component as it gets repositioned automatically when there isn't enough desktop space.

I think the main concern here is consistency. In all cases, except Scripts and Alphabets buttons, the popup menu is connected to the bottom left corner, so that the popup menu is not converting the connected component when displayed downwards (it will still cover it when forced to be displayed upwards).

All context menus in the next version will use the bottom left corner for consistency.

den4b Forum

#1 2014-05-21 01:26

Missing TSpeedButton keyboard shortcuts

#2 2014-05-21 17:17

Re: Missing TSpeedButton keyboard shortcuts

#3 2014-05-27 01:55

Re: Missing TSpeedButton keyboard shortcuts

#4 2014-06-04 15:29

Re: Missing TSpeedButton keyboard shortcuts

#5 2014-08-13 23:58

Re: Missing TSpeedButton keyboard shortcuts

#6 2014-08-18 23:41

Re: Missing TSpeedButton keyboard shortcuts

Board footer