Post

Replies

Boosts

Views

Activity

Reply to iPadOS 15, cannot replace/destroy foreground scene, and activate an existing background scene.
Is there any UIKit engineer knowing how how to handle multiple scenes, or is it dark magic? The Apple iOS apps, Pages for instance, handle multiple scene in a elegant way, whereas my app, using the same Activate/Destroy API, looks bad. Replacing current scene with another scene: Open doc A in scene A, then open another scene B, and open the same A doc. Pages simply shows the former scene, and the latter one disappears. I succeeded to make my app work on iOS 15, but it works in an unyielding manner, as I described above: The current scene B is shrinked to half screen, then the target one, A, is activated on the other half of the screen, then B scene is destroyed, and finally scene A is enlarged on the whole screen. Opening a document from Spotlight, that's already open in one of the existing scenes, does not activate that particular scene. Instead, it activates the last used scene, EVEN if there is another scene that has that doc already open. (I do set 'prefersToActivateForTargetContentIdentifierPredicate', but no luck). On Apple Pages, it activates the correct scene.
Topic: UI Frameworks SubTopic: UIKit Tags:
Sep ’21
Reply to Prevent creating "Default configuration" scene on macCatalyst at startup
L.E. ..to work on a doc app with multiple windows. For the rest it works just fine, I'm close to launching my app ported from iOS and it helped tremendously.
Topic: UI Frameworks SubTopic: AppKit Tags:
Replies
Boosts
Views
Activity
Aug ’22
Reply to Prevent creating "Default configuration" scene on macCatalyst at startup
Is there anybody using macCatalyst with multiple scenes or it's only good for simple, one window apps?? No documentation, no way to change anything scene related, unless you dive into AppKit, it looks like it's a waste of programmer's time :(
Topic: UI Frameworks SubTopic: AppKit Tags:
Replies
Boosts
Views
Activity
Aug ’22
Reply to 'UIColorPickerViewController' is only available in Mac Catalyst 14.0 or newer
Here's the settings from my project, no macOS deployment target at project level.
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
May ’22
Reply to iPadOS13 (b7), UIMenuController and multiple windows
Did you find a fix? The solution using 'makeKeyWindow' is not working on iPadOS 14-15.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Oct ’21
Reply to UIMenuController won't open sub-menu
Did you find a solution? I'm also facing this issue.
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
Oct ’21
Reply to iPadOS 15, cannot replace/destroy foreground scene, and activate an existing background scene.
Is there any UIKit engineer knowing how how to handle multiple scenes, or is it dark magic? The Apple iOS apps, Pages for instance, handle multiple scene in a elegant way, whereas my app, using the same Activate/Destroy API, looks bad. Replacing current scene with another scene: Open doc A in scene A, then open another scene B, and open the same A doc. Pages simply shows the former scene, and the latter one disappears. I succeeded to make my app work on iOS 15, but it works in an unyielding manner, as I described above: The current scene B is shrinked to half screen, then the target one, A, is activated on the other half of the screen, then B scene is destroyed, and finally scene A is enlarged on the whole screen. Opening a document from Spotlight, that's already open in one of the existing scenes, does not activate that particular scene. Instead, it activates the last used scene, EVEN if there is another scene that has that doc already open. (I do set 'prefersToActivateForTargetContentIdentifierPredicate', but no luck). On Apple Pages, it activates the correct scene.
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
Boosts
Views
Activity
Sep ’21