-
-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Window on Windows 10 positioned at top left under taskbar #1590
Comments
The position of the window is not set by F3D but by the OS itself. If you open F3D multiple time you will see that the windows are positioned "nicely" so that all their title bar is visible, this is Windows doing its thing. The taskbar stuff looks like Windows not taking taskbar position when computating new Window position. You can force the position of the F3D window using the |
And yet this only happened with For other apps on Windows, the behavior is also different. For example:
It's as if they tried to position themselves to the best way to use the program.
No this didn't happen. Every single f3d window is opened in top left corner (under taskbar) no matter how many instances I opened.
Hmm, as I carry around config files everywhere, I think this workaround is good enough for me. Recommending them to most users will be another story though. Perhaps this is more like feature request than a bug, but I guess it's not very important considering there is already |
I don't doubt it :) F3D however tries to not touch anything but keep defaults from the system. That being said, on MacOS we do position the window because it we do not, it is really wrongly positioned, maybe an arguement can be made that the window should be positioned somewhere else by default on Windows. Centering the window is not trivial as it requires access to the screen size.
Indeed, I just checked and it doesnt do that. I wonder why as I remembers this behavior clearly from some years ago, Ill check.
So your feature request would be that, F3D should position itself by default in the center of the screen, is that correct ? |
Interestingly, some Windows app do have the cascading effect (eg, Win11 terminal app), but others dont (cmake-gui), and some even do not support to be opened multiple times (eg: clock) I do thing we could improve this behavior to be more Windows-like. It is quite barebone now. I'll add it to the Windows related improvements: #21 |
Primary Request
Yes, but more specifically:
I believe this is the ideal/best behavior. It is important that it's only centered in the current focused display in case user is using multi monitor setup, and they are browsing 3D assets on their secondary monitor. Something like this: (it's two monitors stacked vertically) Possible Issue:I'm not sure how to get the screen size, but if the screen size obtained is span of multiple monitors, then if there are two monitors the window will be created in between two monitors. I remembered some apps do this in the past, I don't remember which one. This should NOT be what happened. What I meant is something like this: Alternative Request!In case previous request is not possible, perhaps This behavior is similar to Nomacs image viewer. Possible Issue:If user have multiple monitor, and they drag f3d to secondary display, close it, and then f3d saves it's position and size, then unplug the second monitor, the next time they open f3d, the window will be gone. It will be opened outside of the screen and you can't see them. |
Indeed, that would be nice, but position should be controllable too if needed.
|
Launching F3D in Windows 10, the window is not centered, but instead in the top left corner.
Putting them in top left corner making the title bar inaccessible due being covered by taskbar if the taskbar happened to be on the top.
But even if the title bar is accessible I think it's better to put them at the center of the screen of the currently focused display.
Or another way is to remember the last window position, mimicking Nomacs image viewer.
The text was updated successfully, but these errors were encountered: