Keyboard shurtcut for Designation search tool?

[markusd112]

Hi,

is there any keyboard shurtcut to open the designation search tool in the target list?

I haven't found any info in the help.

Thanks,

Markus

[theskyhound]

Hello,

Short answer: no.

The Keyboard shortcuts in SkyTools are primarily for items on popup menus, or things that directly affect a list or chart. The reason for this is that a shortcut needs to be tied to something that has the keyboard focus when you press the key, otherwise no message will be generated when you press the key. Its a real pain unless you are using strict Windows 3.1 guidelines for the GUI, and its 2023, so that would be ridiculous.

To make all this all work, SkyTools Visual forces the keyboard focus to be on the list (for the Nightly Planner). They key presses operate on the list as a way to quickly bypass a right-click to open a popup menu. The popup menus also provide a place where the shortcuts are displayed to the user.

I suppose I *could* add a "hidden" keypress to open the Designation Search but then I'd have to do the same with all of the other things you can do on the dialog, and if nothing else, I'd run out of memorable keys to assign. So I don't really see a reasonable way forward for this.

[bigmasterdrago]

I love hot keys. But you're right. So many combinations to remember. Can always use Ctrl/Shift/Alt + letter or number.... LOL

Sorry. Couldn't resist.

[theskyhound]

Thinking further: given that the Designation search is actually in a top level menu as well as on the dialog, perhaps there is something I can do there. I will see about making shortcuts for all of the top level menu items, although I can't guarantee anything due to the previously mentioned limitations.

[howardgrams]

Thinking further: given that the Designation search is actually in a top level menu as well as on the dialog, perhaps there is something I can do there. I will see about making shortcuts for all of the top level menu items, although I can't guarantee anything due to the previously mentioned limitations.

Please do!!!  To me the most frustrating thing about using Skytools is the inability to navigate with the keyboard. Needing to mouse around to accomplish anything at all is extremely limiting.

[theskyhound]

Please do!!!  To me the most frustrating thing about using Skytools is the inability to navigate with the keyboard. Needing to mouse around to accomplish anything at all is extremely limiting.

The design philosophy I was taught, was that you should stick with one or the other, never forcing people to switch to the mouse if the keyboard is the primary interface, and vice versa. Given that there is only limited typing in SkyTools, it is designed to be used primarily with a mouse for that reason. When using the mouse, it is clumsy to have to reach for the keyboard with your other hand, or worse, to take your hand off the mouse. I have done everything I could to design things to work with the mouse as efficiently as possible.

SkyTools is primarily for planning, so most of the functions are not used in the field, and when used in the field, I have things automated as much as possible to work with only a few key presses. So the presumption is that the mouse is available, even if using a laptop. I use a small Bluetooth mouse with a small mouse pad for my laptop. If using a  tablet... well, there is neither a mouse nor a keyboard, but I've done my best to accommodate it as well.

I am aware that some people expect to do everything with the keyboard, but again, I am basically forced to choose between one or the other. Its just not possible to fully optimize both experiences. As an example, SkyTools uses embedded dialogs, sometimes three deep. This has many advantages, and is an example of how focusing on the mouse only can allow for a better UI. The keyboard interface in Windows does not handle navigation across sub dialogs well, and the tedium and time involved in handling the keyboard over 100+ dialogs is more time than I can afford, in order to accommodate a small number of keyboard users. So I focus on the mouse. I am sorry about that. But its not just the first time I make a dialog, but every single time it is revised. Things are changing, and if I come across some form of automation that fully handles the keyboard interface for me, then I will try it out.