Bug report: UI controls occasionally become zombie orphans
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I've been using F360 for about a week. I'm definitely enjoying how much more powerful it is than TinkerCAD (my "I need a custom bracket and I don't really care what it looks like" go-to for many years)... but the UI is reminiscent of using Eclipse to write Java circa 2004 or so. For example, I've lost count of how many times I've sworn at something not working, only to realize I was still editing a sketch. Modal interfaces are fine (said the Vim user), but I wish the current mode was more obvious.
ANYway. Several times a day, I'll be in the middle of some operation (usually Move/Copy, which I find extremely unintuitive), get confused, and hit Escape to cancel it... but whatever control currently has the focus (e.g., a dimension text input) doesn't get closed with its parent panel. Then the control just sits there, floating in space, for as long as the app remains open. I can click into the text field, and change its contents, but the autocomplete behavior goes away. I can even drag it around, and it maintains its position even when the app's main window is dragged out from "under" it. Dragging the control after that immediately snaps it back inside the main window's boundary.
The only way I can get rid of them is to quit the app and restart it, which is... a workaround, but not the fastest operation ever, especially when MacOS decides it needs to verify the app AGAIN.
Unfortunately, I can't provide steps to reproduce; I'll come back and update this if I notice a pattern.
I've observed this behavior on MacOS Monterey, on both a 2019 Intel MacBook Pro and on a 2020 M1 MacBook Air. Screenshots are from v2.0.13158 on the MBA ("macOS 12.1 x86_64 (21C52) on MacBookAir10,1" according to the "About" window.)