Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
2
Found in
4.0.1
Issue ID
569902
Regression
No
MonoDevelop doesn't remember the last window position (with dual screens)
This issue occurs when using more than 1 screens.
1. Open MonoDevelop
2. Move the window to another screen.
3. Maximize
4. Close
5. Open MonoDevelop - it's on the wrong screen
Note: Monodevelop remembers the position if it's not maximized.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some Material Overrides are viewed as broken when using the Shadergraph CustomLighting package sample
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
Add comment