Ability to launch app maximized

[blueheron786]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

I am trying to get my app to launch maximized. It doesn't. I can't seem to get it to. Things I've tried:

• Getting access to the BlazorDesktopWindow
• Calling ToggleFullscreen on it (UI thread vs. non-UI thread issues)
• Accessing the underlying WPF window thing
• Setting WindowState manually
• Using event handlers like Activate to set it

All my attempts ended up pretty much the same:

• Can't get access to the UI thread reliably, even with 100ms-10s delays to make sure initialization is done
• Setting the property/code does nothing

Describe the solution you'd like

This could be as simple as: app.Services.GetRequiredService().Bar()

Failing that, a working tutorial would really go a long way here.

Additional context

https://github.com/blueheron786/code-health

[andrewbabbittdev]

Fairly trivial way to do this would be to call the ToggleFullScreen method on BlazorDesktopWindow in a root level component like a Layout.

Here's an example of the MainLayout.razor from the default template doing it:

@using BlazorDesktop.Wpf
@inherits LayoutComponentBase

@inject BlazorDesktopWindow window

...

@code {
    protected override void OnInitialized()
    {
        window.ToggleFullScreen();
    }
}

[andrewbabbittdev]

You should also be able to do this from the Routes.razor component which is at the highest level and would likely be the best option if you needed for the entire apps lifecycle.

[blueheron786]

I can't believe I spent so many hours on this and the solution is so easy. Thank you.

Not related to my initial problem; a few other things:

• Please consider adding an issue type for inquiry/help/other. That's what this issue type really is ...
• Is this project still under development / intended to be supported in the long-term?

Cheers,

[andrewbabbittdev]

Please consider adding an issue type for inquiry/help/other. That's what this issue type really is

I need to update some of the templates to match changes I have done in some of my other repos, so this is on my list. Also enabling discussions as that's the better area for these kind of questions.

Is this project still under development / intended to be supported in the long-term?

Yes as I use it for some of my other projects, I always update it to the latest version of .NET around November / December every year. Its in a pretty good spot now, the only real thing to be looked at would be better support for multiple windows and the APIs for it, though realistically some of the changes for that are big enough that I wouldn't want to do it on the 9.x release cycle.

[blueheron786]

Came back to say this now opens the app full-screen, which is not what I wanted; I want users to be able to see the top bar.

Is this a regression? I'm not 100% sure, but I don't think it worked like this before.

[andrewbabbittdev]

Depends on your windowing settings, full screen would indicate window chrome not being visible. Are you rendering your own window chrome or using the windows default?

Nothing has changed on this front since your last post on our side.

[blueheron786]

I think I'm using the defaults, I haven't changed any settings and added your changes on top. If you can provide a minimal example of this writing or something, that would be amazing. I'll close this again since it's technically done.

[blueheron786]

Reopening because I feel like we do need a feature request for this...

Looks like the recommended API really was (as the name said ...) fullscreen and not maximized. To maximize, adding this to MainLayout's OnInitialized function did it:

window.WindowState = System.Windows.WindowState.Maximized;

I really fell, as a user, that there should be an easier way to do this.

[andrewbabbittdev]

Sorry I misunderstood when I gave you the previous code, that is indeed the way to maximize the window. Full screen is for if you want to render your own window chrome.

Also the window is a WPF object, so you are expected to use WPF apis to manipulate it.

There's no plan to wrap those APIs as the WPF window API surface area is quite large. We give you the WPF window so you are uninhibited on what you can do.

The docs for the window class are here: https://learn.microsoft.com/en-us/dotnet/api/system.windows.window?view=windowsdesktop-9.0

We cover how to do this sort of thing under the readme with the example of closing the window with a custom chrome, but the rest is up to an independent developer to decide how they want to do things in their app.