Reply to thread

Message

<blockquote data-quote="morpheus_xx" data-source="post: 1143580" data-attributes="member: 48495">In this case you can simply create a specialized home screen that does not depend on master_bare.xaml. Just copy the wanted stuff over. Or better: create another &quot;master_bare_animated.xaml&quot; and use it as base.Another thing: I quickly implemented a &quot;IsHomeWorkflowState&quot; property into menu model to bind menu button's visibility to it. It works already, button is only visible in &quot;non-home&quot; screens.The issue with this approach: all settings screens use a screen base, which shows the menu options always (and not in hidden menu). So there the button logic is wrong (menu is visible). That's why I would put the button only into master_menu.xaml, because only there the hidden menu is defined. Only thing we need to find out is, how to place button the best way into the intended position.I would see two options: LayoutTransform to move the button up&nbsp; (not so good), or we define a placeholder in master_bare.xaml and only define a DynamicResource inside master_menu_bare.xaml (better <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />)</blockquote>

[QUOTE="morpheus_xx, post: 1143580, member: 48495"] In this case you can simply create a specialized home screen that does not depend on master_bare.xaml. Just copy the wanted stuff over. Or better: create another "master_bare_animated.xaml" and use it as base. Another thing: I quickly implemented a "IsHomeWorkflowState" property into menu model to bind menu button's visibility to it. It works already, button is only visible in "non-home" screens. The issue with this approach: all settings screens use a screen base, which shows the menu options always (and not in hidden menu). So there the button logic is wrong (menu is visible). That's why I would put the button only into master_menu.xaml, because only there the hidden menu is defined. Only thing we need to find out is, how to place button the best way into the intended position. I would see two options: LayoutTransform to move the button up (not so good), or we define a placeholder in master_bare.xaml and only define a DynamicResource inside master_menu_bare.xaml (better :)) [/QUOTE]

Verification