azskyguy A get info on the app shows it is an Apple Silicon app
It actually is an iOS/iPadOS app that is "translated" by macOS when you run first it on macOS.
Incidentally, the "iOS iPad/iPhone" reference is also sloppy -- the OS that runs on an iPad is called iPadOS while the OS that runs on an iPhone is called iOS. The fork (that today includes tvOS and watchOS) occurred a couple of years ago, and allow custom functionalities and checking during compile time (an Apple Pencil does not work on tvOS, for example).
iOS/iPadOS/tvOS/... are based on the Cocoa Touch framework, while the macOS is based on the Cocoa framework.
The Cocoa frameworks' GUI framework in turn is based on the AppKit while the Cocoa Touch framework is based on the UIKit.
Pinch zoom is available on the latter and not the former, for example, while the API MouseDown is not present in UIKit.
The two frameworks share the non-UI related API called the Foundation framework (Foundation is descended from NeXTStep from NeXT, Inc which merged with Apple in the late 1990s -- that is why all the Cocoa system calls start with "NS").
When you start an iOS/iPadOS the first time, macOS turns all the UIKit calls that are not present in AppKit into some "equivalent" AppKit calls. Things like pinch zoom are turned into either a TouchPad interface, or some really odd combination of Option/Command keys and mouse actions, for example.
One big difference that is likely to be causing the bug that you encountered after updating macOS is the behavior of NSWindow. On an iPad, the "window" is the entire physical screen (with some behavior when you turn on multi-window multitasking). When "translated" for use on macOS, that fixed window becomes a floating, movable and scalable (if the app allows it) discrete window on macOS.
That is probably where the bug resides. The ASIAIR app is forcing the app to change orientation between the flash window and the ASIAIR window. Unless those calls adheres to the documented behavior in macOS, an app that uses a hack that was made to work on an OS is not guaranteed to work on future versions of the OS. This is why real developers obey documentation and not resort to hacks or copy-and-paste coding -- that is the only way to make sure an app survives OS updates.
Short story is that ASIAIR iOS app needs to comply with the macOS requirements. (This is what the annual WWDC is all about -- ZWO probably did not attend the WWDC sessions.) It is probably a ten minute fix, plus a day or two of regression testing by QA to make sure buttons and captions don't start to behave badly, assuming that regression tests have previously been automated (else, the customer becomes the guinea pig/Beta tester).
Chen
P.S., I am just an old retired guy who started using what became MacOS X internally at Apple, when it was called "Rhapsody," before it was released to the world as Developer Release 1 and Developer Release 2 of Rhapsody. I have nothing to do with ZWO, except to, over the past years help answer questions from their developers.