Using the term "windows" for the top tab like items, and "tabs" are those under each window - I can see a rational as grb2007 mentions for grouping related items. But this was already possible by having an actual movable "window", with multiple tabs (which are now called "windows"). We have all used that function for years. My biggest issue is that swiping between tabs seems to be broken. If I click on file1 in the navigator, it shows up. If I click another file2, it shows up. But swiping to the right doesn't show file1, but somewhere else. What's worse, is my file1 shows up for a second, then it's yanked away and that somewhere else shows up. I assume it's using the tab history, but I can't figure it out. Anyone know how to either remove the new "tab" feature, or at least fix the swiping between files in the file history? thanks.

I deleted all my derived data and sadly the windows are all still black. I'll look for a newer 14.0.1 next. What's strange, is the navigator in the storyboard also shows things black for View, TextView, StackView etc. That's what leads me to believe there is some preference that I cannot figure out. This screenshot shows the different colored TextView browser. /Users/scott/Desktop/BlackWindows2.png

I actually found others with this issue from previous editions. I am using cocoa pods which might be the issue. I'll look at that direction next. I don't know about the Rosetta in the information for Xcode (which is checked).

I just updated to 14.0.1 ER and the windows are back to their default colors. Yay.

I too believe taking away storyboards is a step back. Storyboards are impressive IMHO. Without them it's like having to place debug statements in my embedded ESP chips; such a lower level. I've been trying to duplicate a watch app in another projects but it's not possible manually, and the app they create is in Swift. I also like Objective-C way more than Swift.

Did you ever get a reply to this? Most of my apps of the watch were initiated by the watch, which woke the iPhone and then potentially sent a message out on the network (and received messages as well). But now I have the issue where an MQTT message needs to be received by the iPhone and then forwarded to the watch. Since the phone is in the background, that won't work. So I was wondering if the watch could wake up the phone for some period of time - and have it wait for messages (or if MQTT saves the messages). This fits your question of "how long can background process run).

Well I too am having issues with Xcode 15 and git. I can see the normal file list with the "M" showing a change. But then the "stage all" and the commit-push doesn't work. I can sometimes get staging a single file to commit but even there it doesn't provide any feedback that it did the commit. I have to go to the GIT website and hope it worked. As I have about 6 pods or other repositories that make up my app, this too seems to get an error saying it cannot communicate with GIT (on one of them). Maybe it takes too long. Prior to Xcode 15 everything was working very nicely.

Start here: drawingwithquartz2d

This is the Tobii link: https://us.tobiidynavox.com/# But I cannot post as a 'link' because of error: "This domain "https://us.tobiidynavox.com/#/" is not a permitted domain on this forums."