column

If I run the exact same code on MacOS 12.7 (Xcode 14.2) and MacOS 15.0.1 (Xcode 15.0.1). In a scrollView, I display lines (lineDivider) and then a LazyVgrid, applying some offset: ScrollView(.vertical) { ForEach(1...50, id: .self) { index in LabelledDivider(label: (index), color: .gray.opacity(0.1)) .offset(y: CGFloat(65*index - 50) } LazyVGrid(columns: gridItemLayout, spacing: 33 ) { ForEach ($allItems.theItems) { $item in ItemView(item: item) } } .offset(y: 40) } In Xcode 14.2, I get the first layout and in Xcode 15.0 the second on right: The divider line is at the same position, but the view in grid is not. If I change .offset(y: 40) to .offset(y: 60) I get the same layout. So my questions: did anyone observe similar change ? is it due to Xcode, to MacOS ? Is it documented somewhere ?

I'm using two loops, one nested in another to create and assign a subclass to the parent class. I'm using x for one loop and y for the other loop. Print statement shows the loop variables being updated correctly, however the subclass has both variables as the same value. I'm not sure if the value is being stored as the same value or being displayed as the same value. I've checked both creation and display code. I can't find the error. var body: some View { NavigationSplitView { List { ForEach(routes) { item in NavigationLink { Text(Route: (item.route_name) nSeason: (item.route_season)nCoordinates: (item.route_coordinates)nProcessed: (String(item.route_processed))nNumber of baseboards: (item.route_baseboards.count)) } label: { Text(item.route_name) } //end route nav link } //end route for each .onDelete(perform: deleteItems) //end route nav ForEach(baseboards) { item in NavigationLink { //if let test = item.baseboard_heightPoints.count { Text(Grid Size: (String(item.baseboard_grid_size))nRow:(String(item.baseb

I need to know correct color conversion matrices for converting YCbCr422 and YCbCr420 10 bit video range sample buffers (BT.2020 color space) to RGB. AVFoundation framework mentions AVVideoYCbCrMatrix_ITU_R_2020 which is a string constant. But I need to know the full matrix that can be used to perform color conversion. I have this matrix for full range BT2020, not sure if this is correct and what is the correct way to adapt it to video range. let colorMatrixBT2020_fullRange = ColorConversion(matrix: matrix_float3x3(columns: (simd_float3(1.0, 1.0, 1.0), simd_float3(0.000, -0.11156702/0.6780, 1.8814), simd_float3(1.4746, -0.38737742/0.6780, 0.000))), offset: vector_float3(0.0, -0.5, -0.5))

I have a Mac Catalyst app configured like so: The root view controller on the window is a tripe split UISplitViewController. The secondary view controller in the Split View controller is a view controller that uses WKWebView. Load a website in the WKWebview that has a video. Expand the video to “Full screen” (on Mac Catalyst this is only “Full window” because the window does not enter full screen like AppKit apps do). The NSToolbar overlaps the “Full screen video.” On a triple Split View controller only the portions of the toolbar in the secondary and supplementary columns show through (the video actually covers the toolbar area in the “primary” column). The expected results: -For the video to cover the entire window including the NSToolbar. Actual results: The NSToolbar draw on top of the video. -- Anyone know of a workaround? I filed FB13229032

I’m talking about CSS-functions: https://w3c.github.io/csswg-drafts/css-values/#round-func) .example { --result: round(up, var(--number), 1); } In Safari 16.x css round didn’t work perfect.round(up, x, 1) did its job, if x wasn’t a “natural” number (all digits after the fraction mark 0). If it was, it resulted the next one! Now Safari 17.0 gives 0 for all numbers! !Update! Sorry, Safari 17 does round! But: not in code like that: :root { --result: round(up, var(--number), 1); Had a project, where this was used to define the number of columns and rows I wanted for an (mostly) quadratic layout. What’s working instead: grid-template-columns: repeat(round(up, sort(var(--items), 1), minimal(…); the former css used the :root-variant (grid-template-columns: repeat(var(--result) …). !Update 2! After some experiments I found: Safari 17 doesn’t like :root any more! (https://www.w3.org/TR/selectors-3/#root-pseudo) And: Safari doesn’t calc correct: `round(up,1,1)˚ is 2 — says Apple. YOU MUST NOT

Hi. If I use Xcode 15 to build wwdc2022-10054 (The SwiftUI Cookbook for Navigation sample project), it crashes when, on an iPad, you: Choose Three Column Navigation in the app (so you need to run this on an iPad or iPad simulator) Select category Dessert Select recipe Tiramisu** Select category Pancake Select any pancake recipe **selecting anything from Kanom Thong Ek or beyond will cause the crash. It seems to be a problem with selecting an item (recipe) when the previous recipe you selected is at least one position further down than the length of the current category recipe list. It's like SwiftUI is trying to deselect a previous list item or something, but the list is now shorter so that item doesn't exist anymore. I'm not sure if it crashed when built with Xcode 14, but it certainly does with Xcode 15.

I created a new project in xCode 15 on MacOS 14. This project only has a View with a Table that has two columns. When I call the view I get the following error several times: Metal failed to load render pipeline: pipeline=PL008BsovXmw_TprcA3Xhf sdk=23A322 Failed to find reflection in binary archives Here is the code: struct Freunde: Identifiable { var id: UUID = UUID() var firstName: String = var lastName: String = init(firstName: String, lastName: String) { self.firstName = firstName self.lastName = lastName } } struct ContentView: View { @State var sortOrder = [KeyPathComparator(Freunde.firstName)] @State public var selectedItems: Set = [] @State var myList: [Freunde] = [ Freunde(firstName: Klaus, lastName: Kirchhoff), Freunde(firstName: Patrik, lastName: Grot), Freunde(firstName: Johannes, lastName: Gottfried), Freunde(firstName: Daniel, lastName: Schaedla) ] var body: some View { VStack { Table(myList, selection: $selectedItems, sortOrder: $sortOrder) { TableColumn(Vorname, value: .firstName) T

I'm creating a program where every time a user clicks a button, which is in the MyPond view, a new fish is added to an array, which appears as a FishView in a grid in the Journal View. MyPond, where the user clicks a button to generate a new fish: struct MyPond: View { @State var newFish = Fish() var body: some View { VStack { Button(action: { newFish = Fish() Journal().addFish(fish: newFish) } }) { Text(Click here to fish) .padding() } } } } The Fish Object: struct Fish: Identifiable { var id = UUID() var name: String = fishNameGenerated.randomElement()! } Journal, which is currently not displaying any fishViews: class Fishies: ObservableObject { @State var array:[Fish] = [] } struct Journal: View { @ObservedObject var fishArray = Fishies() public func addFish(fish: Fish) { self.fishArray.array.append(fish) for fishy in fishArray.array { print(fishy.name) } // currently not printing anything } let columns = [GridItem(.flexible(), spacing: 10), GridItem(.flexible(), spacing: 10), GridItem(.flexible()

I developed a couple of iMessage sticker apps, one of which has medium size stickers and the other has large stickers. Since the iOS 17 update all of the stickers are showing as small size when sent in a message. I don't see a setting in Xcode for 1-column, 2-column, 3-column anymore. How can I get my stickers to show at the correct size again when sending/receiving in iMessage? Edited to add: I have discovered that although the stickers show as small when I send them, they are still receiving in the correct size. I still don‘t see the column setting in Xcode, so it would be useful to know how to set the desired sticker size. (perhaps it is now automatic based on image size?)