Skip to content
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

Catalyst version: Image settings window unresponsive after upscale. #21

Closed
ArguingMeadows opened this issue Jan 9, 2021 · 5 comments
Closed

Comments

@ArguingMeadows
Copy link

Hi there,

In the latest update for the the MacOS Catalyst version, if you upscale a photo, and then go back and upscale a new one, the image setttings (MPSCNN/cunet, Noise Level, etc.) window becomes unresponsive. The only way to get around it is to close the program entirely and start it back up.

@imxieyi
Copy link
Owner

imxieyi commented Jan 14, 2021

Are you using Big Sur or Catalina? This issue didn't happen with Catalina before the update. Looks like it wasn't fully fixed in the recent update.

@ArguingMeadows
Copy link
Author

M1 with Big Sur.

@imxieyi
Copy link
Owner

imxieyi commented Jan 14, 2021

SwiftUI hit test in Mac Catalyst seems to be broken on Big Sur. Even iOS version on M1 Mac is broken in the same way. A potential fix is to convert iOS views to macOS native views, which can be done by changing UI Idiom. However, this requires dropping support for Catalina. Also, a lot of optimizations are needed to make it feel right on macOS. For now, please consider using CLI version before this is completely fixed (likely recently). Sorry for the inconvenience!

@ArguingMeadows
Copy link
Author

It's a minor inconvenience, I just wanted to bring it to your attention. I personally like this version better so I'll be sticking with it for the time being. Thanks again, and I look forward to more updates.

@imxieyi
Copy link
Owner

imxieyi commented Jan 23, 2021

It turns out that changing UI Idiom still won't fix this issue. I moved the setup interface to a separate window instead. Please update to the latest version in Mac App Store and it should be fixed.

@imxieyi imxieyi closed this as completed Jan 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants