Can wails handle multiple monitors?

[realtebo]

I'm scouting for a system to develop a multiple monitor app.
The context is a 'not-so-simple' timer for a conference room.
But it's deadly important to have full control of each window in each monitor.
for example, app must start in the 'main' monitor, in front of the user, but timer must be full screen in the monitor #3 while in the monitor #2 there will be additional infos running about the current speaking

[dosubot[bot]]

Wails can handle multiple monitors and lets you create and control multiple windows in a single app. You can enumerate all connected screens using the ScreenGetAll API, which gives you details like which monitor is primary, its size, and its coordinates. To place a window on a specific monitor, you create a new window, then use the monitor's coordinates (from ScreenGetAll) with WindowSetPosition to move the window to the desired screen, and WindowFullscreen to make it fullscreen if needed. Each window can be independently sized, positioned, and set to fullscreen mode reference reference.

One limitation: all windows share the same frontend assets, so you can't load a completely different UI in each window out of the box reference. For your use case (main app on monitor 1, timer fullscreen on monitor 3, info on monitor 2), you can create three windows, move each to the correct monitor using their coordinates, and control their content via your frontend logic (e.g., show/hide different panels per window).

If you need each window to have a totally different frontend (not just different content), that's not currently supported by the public API. For most multi-monitor conference timer scenarios, though, Wails' APIs should give you the control you need.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[leaanthony]

@dosu is partially hallucinating. You can absolutely have different assets rendered in different windows, you just select a different path within a common asset bundle.

[dosubot[bot]]

You're right, and thanks for the correction. Wails v3 does let you render different assets in different windows by specifying a different start URL (path) for each window within your embedded asset bundle. You can embed multiple frontend builds (each with its own index.html and assets) using Go's embed.FS, then, when creating each window, set its start URL to the desired entry point (like /window1/index.html, /window2/index.html, etc.). This is supported and maintained, as shown in recent examples and merged PRs (example). All assets just need to be present in the common bundle and referenced by their respective paths. No major caveats are documented for this approach in v3.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}