stride3d / stride3d/stride

Xenko window should remember monitor/window position (per project)

Open
#682 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-GameStudio enhancement
Dominant language
C#
Stars
7.8k
Forks
1.2k
Avg merge
2d 17h
Merged PRs (30d)
49

Description

Release Type: official 4.0.0.1-beta2-0926
Version: official 4.0.0.1-beta2-0926

Platform(s): Windows

Describe the bug

The Xenko studio widow starts on whatever monitor the mouse happens to be when it finally creates the window, but it takes quite a long time to launch. This is really annoying, because I often do something else during the long launch time, and then it starts up on the wrong monitor -- every time.

It should (a) remember the last monitor/window position per project, like visual studio, and (b) get the current monitor the moment it is launched, instead of only when the window is created. so it'll start on the monitor where the mouse was when it was launched, not wherever it is when the user is doing something else while waiting for it to launch.

To Reproduce
Steps to reproduce the behavior:

  1. launch the Xenko launcher on the primary monitor
  2. click the big red "Start 4.0.0.1-beta02-0926" button (or equivalent)
  3. move the mouse to a secondary monitor
  4. WITNESS: when Xenko finally starts 20-60 seconds laster, it comes up on the secondary monitor, because this is where the mouse happens to be while waiting for Xenko.

Expected behavior

I expect Xenko to (a) start up on the monitor and window position it was last closed at in the project, and (b) on a new project, I expect it to start on the monitor where the mouse was when it was launched, not 20-60 seconds later when it decides to finally create the window.

Additional context

Other similar tools remember the monitor and window position per project, and start on the monitor where the mouse was the moment they are run/launched, not 20-60 seconds later.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue through the Xenko launcher, using the large red start button and the Windows Studio startup flow described here. Done means a project reopens on its last monitor and window position, while a new project uses the launch-time monitor rather than the monitor occupied later during startup.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop, game-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.