Use case
A common first step for a branded app shell is copying Atlas_Core.Atlas_Default into your own module: describe layout, then create layout under a new name, then customise. In v0.24.0 the describe output says so itself:
$ mxcli -p Repro.mpr -c "describe layout Atlas_Core.Atlas_Default"
...
-- Forms$SidebarToggleButton (sidebarToggle3) -- NOT re-executable: mxcli cannot author this widget, so re-running this script would drop it
Atlas's responsive sidebar (slide-in navigation on phones and tablets) depends on that button. The copied layout therefore loses mobile navigation, and nothing warns at exec time.
Proposed behaviour
- A widget keyword, for example
sidebartoggle sidebarToggle3 (Caption: '', Icon: …, Class: 'toggle-btn', RenderMode: Button), which describe layout emits instead of the comment. Its properties are those of Forms$SidebarToggleButton (caption, icon, button style, render mode).
- Until then,
exec of a layout containing that comment could print a warning that the copy has no sidebar toggle.
Environment
mxcli v0.24.0; Mendix 11.14.0 blank project (Atlas_Core 4.1.3); the same widget is in current Atlas versions.
Use case
A common first step for a branded app shell is copying
Atlas_Core.Atlas_Defaultinto your own module:describe layout, thencreate layoutunder a new name, then customise. In v0.24.0 the describe output says so itself:Atlas's responsive sidebar (slide-in navigation on phones and tablets) depends on that button. The copied layout therefore loses mobile navigation, and nothing warns at
exectime.Proposed behaviour
sidebartoggle sidebarToggle3 (Caption: '', Icon: …, Class: 'toggle-btn', RenderMode: Button), whichdescribe layoutemits instead of the comment. Its properties are those ofForms$SidebarToggleButton(caption, icon, button style, render mode).execof a layout containing that comment could print a warning that the copy has no sidebar toggle.Environment
mxcli
v0.24.0; Mendix 11.14.0 blank project (Atlas_Core 4.1.3); the same widget is in current Atlas versions.