Dear @adam , Dear All
This might be a very stupid question and maybe it has been answered a hundred of times… but I wasn’t able to find a real answer in the forum nor in the docs.
Basically I would like to have the top AppBar as “sticky” or “permanent” (call it however you want. ). So when you scroll through your dashboard content, the AppBar should stay always on top.
Is that possible? If yes, how?
Because I haven’t found a way to define this using the New-UDDashboard commandlet…
What we currently do is this:
New-UDDashboard -Title “MyDashBoard” -Pages $Pages -Theme $Theme -DefaultTheme dark
But there is no possibility to say for example “-AppBar sticky” or something like that.
You can use the New-UDAppBar cmdlet with the -position fixed parameter. The div is just to demonstrate the fixed nature by putting something really high in the body.
Indeed, I tried to use UDAppBar in my main UD-Dashboard file which will start the Dashboard itself… However I’m still encountering some issues:
First it seems that you cannot use AppBar in combination with New-UDDashboard -Pages but only with -Content
Second if I use AppBar to override the default AppBar which gets created via New-UDDashboard also this happens:
– The Theme Switch goes to the very left of the AppBar, next to the AppBar Title
– The Avatar and Username incl. the Logoff buttons disappear.
Again, sorry to bother again with this… maybe it’s even possible… But I wasn’t able to find information in the docs and in the Cmdlet Help Page (and forum obviously )
However I think this won’t be the final solution to the problem. I realized that the AppBar somehow overrides the “main” AppBar which gets created by New-UDDashboard. So in theory it should be possible to specify the “-Position fixed” parameter directly as one of New-UDDashboard arguments. I don’t think it will be possible to cleanly workaround this issue by just using New-UDAppBar.
To be honest I don’t really see the usecase for this command since on every page an AppBar is automatically created… and you can’t even override it’s layout but just create a new one.
Again, maybe I’m totally wrong… But hopefully @adam or somebody else who has deep knowledge on this component will put some light on it.
OK thanks a lot Adam! Really much appreciated that you’ll take care also of this “issue”.
Looking forward to it!
I’ll add a reference to this thread in your issue tracker…