- Generated on Sun Sep 24 2023 00:04:24 for KiCad PCB EDA Suite by
1.9.5
|
KiCad PCB EDA Suite
|
#include <wx/defs.h>Go to the source code of this file.
Macros | |
| #define | ROOM_FOR_KICADMANAGER 50 |
| Common command IDs shared by more than one of the KiCad applications. More... | |
| #define | ROOM_FOR_3D_VIEWER 100 |
| #define | ROOM_FOR_PANEL_PREV_MODEL 50 |
| #define | DEFAULT_FILE_HISTORY_SIZE 9 |
| IDs range for menuitems file history: The default range file history size is 9 (compatible with default wxWidget range). More... | |
| #define | MAX_FILE_HISTORY_SIZE 99 |
| #define DEFAULT_FILE_HISTORY_SIZE 9 |
| #define ROOM_FOR_KICADMANAGER 50 |
Common command IDs shared by more than one of the KiCad applications.
Only place command IDs used in base window class event tables or shared across multiple applications such as the zoom, grid, and language IDs. Application specific IDs should be defined in the appropriate header file to prevent the entire project from being rebuilt.
However, we must avoid duplicate IDs in menus and toolbar items, when wxUpdateUIEvent are associated to menuitems and/or toolbar items The reason is the fact wxWidgets try to send a wxUpdateUIEvent event to a given window and, if a wxUpdateUIEvent event function is not defined for a menuitem, wxWidgets propagates this event ID to parents of the given window. Therefore duplicate IDs could create strange behavior in menus and subtle bugs, depending on the code inside the wxUpdateUIEvent event functions called in parent frames. I did not seen this propagation to child frames, only to parent frames
Issues exist only if 2 menus have the same ID, and only one menu is associated to a wxUpdateUIEvent event, and this one is defined in a parent Window. The probability it happens is low, but not null.
Therefore we reserve room in ID list for each sub application. Please, change these values if needed
| enum main_id |
1.9.5