Yes, of course they can be.
But you have to know where the code that defines them is. Or make a new ux :smile:
Printable View
Yes, of course they can be.
But you have to know where the code that defines them is. Or make a new ux :smile:
If Show Quick Menu Button is disabled QuickMenu Button is not active, that is, it depends on the proper functioning of the first field.
I don't need to say to be careful with changes in the ux.Spoiler: image
Good luck.
I won't touch it anymore and i'll adjust to it.Quote:
Originally Posted by jorgeultra [Only registered and activated users can see links. Click Here To Register...]
Last question please, about the feature which i haven't yet understood its function - The "Auto close second quickmenu" button and its 0-30 sec' "Time" feature display.
Thank you
The buttons set in QuickMenu Buttons remain on the screen respecting the time the user sets in Auto close second quickmenu.
This function allows the user to enable several functions that may be needed at some point and does not pollute the cockpit during the route.
In normal situation, during the route, the screen (cockpit) has only the buttons set by the user through the Cockpit Buttons option.Spoiler: QuickMenu Buttons
Spoiler: Cockpit Buttons
Thank you @jorgeultra for the demo.
Since i had the "as-is mess" in the UX folders and they were reflected in failed performance for me - I couldn't experience this important feature. Now and for the first time, i fully understand the difference and the benefit usage between "cockpit buttons" and "quick menu buttons" display.
And again, Thank You all very much.