Search Issue Tracker
By Design
Votes
0
Found in
Issue ID
1107082
Regression
No
[OSX] Menu item becomes inactive if custom window is closed before progress bar.
When a window is created from custom menu item, and a progress bar is generated through that window, if the user closes the window before the count down finishes on the progress bar, the menu item becomes unavailable on the menu.
Repro:
1. Download and open attached project
2. In menu bar, Example -> Progress Bar Usage
3. In the window appeared, click Display Bar button.
4. Progress bar window appears and starts to count down.
5. Before the Progress bar finishes, close the custom window.
6. The progress bar starts counting down and stuck (this is normal)
7. Try to reopen the window again via menu bar, Example -> Progress Bar Usage
Expected: The user can open the custom window after closing it before the count down finishes in progress bar
Actual: The menu item becomes inactive if user closes the window before the progress bar finishes counting down
Found in: 2019.1.0a11
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2019.2.X):
Editor menus are disabled while a modal dialog is displayed. The user script never calls EditorUtility.ClearProgressBar when the window is closed so the modal progress bar stays and keeps menus disabled.