-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
toolbar inaccessible outside screen #13946
Comments
It seems you are not using FreeCAD but the modified Ondsel version, is this reproducible in FreeCAD too? |
Good question. But I don't want to also break my FreeCAD install so I am not eager to try to reproduce this unless there is a way to revert this. Which I don't see yet. |
If this is Ondsel-specific, another option might be to submit the issue at https://github.com/Ondsel-Development/FreeCAD/issues. As an aside, I wonder if there is a way to transfer issues across GitHub projects. It might be beneficial to move issues around, in both directions across upstream and distributions. |
Seems like there is a way. Just not sure it works also across orgs. Feel free to move it if that's a better fit. |
I'll close this here then, please create it at the Ondsel repo. |
FWIW ... Changing Settings > Workbenches > Workbench selector type/position brought this back into a usable state. Still a pretty ugly bug. |
Is there an existing issue for this?
Problem description
By mistake I have dragged the workbench toolbar. Now I can no longer attach it.
The console shows
(qt.qpa.window) Window position QRect(1064,-280 70x1490) outside any known screen, using primary screen
I am hope it's OK to report this here since it happened in Ondsel.
Full version info
OS: macOS 14.4.1 Word size of Ondsel: 64-bit Version: 2024.2.0.37191 (Git) Build type: Release Branch: (HEAD detached at 2024.2.0) Hash: 2ad5fb327d068ae6280cf702d528b3a6e35770a7 Python 3.11.9, Qt 5.15.13, Coin 4.0.2, Vtk 9.2.6, OCC 7.7.2 Locale: C/Default (C) Installed mods: * Ondsel-Lens 2024.1.22.01
Subproject(s) affected?
None
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: