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
Rui Azevedo edited this page May 24, 2018
·
2 revisions
this options should be activated at compiler command line so that all files are influenced by them.
Usually providing a -D compiler flag.
ex: -DMENU_IDLE_BKGND
MENU_USERAM
This option is active by default on non-AVR devices. It allows menu data to reside on RAM.
If used on AVR devices it will allow dynamic menus.
MENU_DEBUG
Activates debug mode, code blocks inside _trace(...) are activated
TRACE
If debug mode active then code blocks inside trace(...) are activated, this is often too much as all debug messages will be printed. Its preferable to turn trace into _trace manually to have specific blocks active.
MENU_IDLE_BKGND
If compiling with this option defined then the idleTask function is always called if not the same as sleepTask, as a complement to allow common behavior.
MENU_ASYNC
Activates some extra functions to allow stateless usage of the menu, this option is required for web menu implementation. It does local state transformations to switch between current and requested state, following all steps between the states.
MENU_FMT_WRAPS
Allows output wrap overlays to be used on output devices, this is essential to have menu structure exported to xml, as xml tags need to wrap the content.