Hey,
I wanted to check if it’s just me or if also other members of the “KiCadmunity” think similar
In some cases, I would like to have a better adaptive window scaling that changes the size according to the content OR just a maximized window. For example in layout, it would be great to view the whole stackup:
Also pretty strange is the visualization of the layer and the grid menu because the width and the via drop down menu don’t show that behavior:
Next thing ist that in some panels, it is not possible to use the arrow keys for navigation, like the search panel.
And when I select a component there with the mouse and hit E while with the mouse arrow still inside that window, the properties panel of the selected component isn’t opened. Only if I move the mouse inside the schematic window and press the key, then it opens.
Then I miss underscores in the menu bar lists to access commands/menus:
You can find out from the recent “what are you hoping for in V10” thread . . . how many are looking for GUI improvements ? how many are looking for functionality improvements/additions ?
This is entirely user preference and opinion. Perhaps the size and maximize state of that dialog can be saved per user after it’s changed from default.
You can blame your OS/GTK.
Windows opens the drop-downs correctly heh
The headache here is translation. Kicad supports every language under the sun and it’s very difficult to setup accelerators universally (for example, New in English has a leading N, but the translated word in Turkish starts with a Y for Yeni).
Accelerator keys are translated (using ampersand & in the menu item string). The translator of the string would be responsible for finding the letter which hasn’t been reserved yet in that menu. These accelerators change from language to language, contra hotkeys or shortcuts. Note that at least on Windows KiCad already has menu item accelerator in the main level items (File Edit etc.) but for some reason not in the menu items under them. KiCad also has the drawback of having many too long menus for that system. Each menu is a context where one has to find a unique key for each menu item. Near-identical strings or too many strings cause running out of available letters.
This is not a perfect system but at least gives possibility for using Alt + visual cue to follow. Some applications implement it and some people use it. Some people hate it.
I don’t understand why you take that example, New in English etc., because the idea of those accelerators is that they are chosen ad hoc by the programmer for the original language (English) and then again ad hoc by each translator. They are not set “universally”. They can be left out in translations, too. Some systems can even assign them automatically, I don’t know about wxWidgets.
