(2021-04-14, 16:23)N. W. Perry Wrote: Thanks, that is very helpful! So we can at least say that Wine itself will run under Big Sur, but only 64-bit programs will work, confirming the rumors. For users who only really want to get LDCad working, that may be enough. (There seem to be a lot of Studio users on macOS who would like to be able to work in LDCad, for example.)
If you (or anyone) have Mission Control enabled with multiple desktop spaces, could you try something else?
1. Open LDCad in a desktop space with no other windows or apps in it
2. Switch to another desktop (this one can have windows open, or not; it doesn't seem to matter)
3. Switch back to the LDCad space
— Does the LDCad window appear to be the front window (even thought it's the only window)?
—Without clicking the mouse/trackpad, does anything in the LDCad window respond to mouse-over? Menu highlights, part highlights, source window entries, etc.?
—Without clicking the mouse/trackpad, does LDCad respond to any keyboard input? For example, ctrl-N for a new file?
4. Now click in the LDCad window, as if to make it active.
—Does the window now respond normally to mouse-over or keyboard inputs?
This is the issue I found with LDCad specifically, starting in Wine 5.0. The issue is not present in Wine 4.0.3. To me, it's a deal breaker, but other users might find it acceptable and thus be okay with current versions of Wine. (But I haven't tested other LDraw apps in 5.0.)
I can confirm, that you must first select LDCad in order that mouse over , ... is working. When you select the app it will work.
But in my opinion, this is natural to MacOS, since LDCad is not an app bundle. If you e.g. develop a program with wxWidgets (a cross platform C++ Gui framework) you have the same result. After compiling and launching the program it will not have the focus. As soon as you create an app bundle, it will behave as a "normal" MacOS app. Also Cmd-Q does not work for closing the app. You need to close the window.