More people complaining about this.
https://stackoverflow.com/questions/71904374/swiftui-how-can-you-make-your-app-come-to-the-front-when-clicking-on-the-dock-i
M1 Pro MBP, should have no problem with this sort of load but it does.
TextEditor will hang if you give it say 10mb worth of log data (string).
Programable scrolling is missing in action.
My work around will been to trim the data I'm displaying so that it remains manageable or roll my own NSViewRepresentable with a proper cocoa NSTextEditor.
Apple can do much better.
Thank you all,
Been chasing this intermittent glitch for a while
At one point I was using ${TARGET_BUILD_DIR}/${INFOPLIST_PATH} as input which was not helping.
Thank you.
I wish this was incorporated into apple's docs.
For example following these instructions is a lot harder and the code recreates the WindowGroup, thus each time you receives one of these urls, you end up with a new window.
https://developer.apple.com/documentation/xcode/supporting-universal-links-in-your-app
More people complaining about this.
https://stackoverflow.com/questions/71904374/swiftui-how-can-you-make-your-app-come-to-the-front-when-clicking-on-the-dock-i
M1 Pro MBP, should have no problem with this sort of load but it does.
TextEditor will hang if you give it say 10mb worth of log data (string).
Programable scrolling is missing in action.
My work around will been to trim the data I'm displaying so that it remains manageable or roll my own NSViewRepresentable with a proper cocoa NSTextEditor.
Apple can do much better.
Thank you all,
Been chasing this intermittent glitch for a while
At one point I was using ${TARGET_BUILD_DIR}/${INFOPLIST_PATH} as input which was not helping.
Thank you.
I wish this was incorporated into apple's docs.
For example following these instructions is a lot harder and the code recreates the WindowGroup, thus each time you receives one of these urls, you end up with a new window.
https://developer.apple.com/documentation/xcode/supporting-universal-links-in-your-app