“column”

So the complete code part1: struct ContentView: View { @State var text1: String = // <<-- Declare HERE ; could be an array of String @State private var tipa: [Double] = [] @State private var costa: [Double] = [] @State private var cost = @State private var costt: Double? = 0.0 @State private var paidt: Double? = 0.0 @State private var paid = @State private var tipp = @State private var tipc = @State private var tipaa = @State private var totalCost = @State private var totalTips = @State private var totalCash = @State private var tipcc = @State private var numbc = @State private var deletep = 0 @State private var number = 0 @State private var errorMsg = var body: some View { GeometryReader { g in NavigationStack { VStack { HStack { // No need to manually pad the date out with spaces, which will never be correct. // Just use an HStack and put a Spacer() in, so it goes: |<.....Spacer().....>Date| Spacer() Text(Date().formatted(date: .numeric, time: .omitted)) .foregroundStyle(Color.black)

Okay, well, you went ahead anyway. Here's my update: // ContentView.swift import SwiftUI struct ContentView: View { @State private var tipa: [Double] = [] @State private var costa: [Double] = [] @State private var cost = @State private var costt: Double? = 0.0 @State private var paidt: Double? = 0.0 @State private var paid = @State private var tipp = @State private var tipc = @State private var tipaa = @State private var totalCost = @State private var totalTips = @State private var totalCash = @State private var tipcc = @State private var numbc = @State private var deletep = 0 @State private var number = 0 @State private var errorMsg = var body: some View { GeometryReader { g in NavigationStack { VStack { HStack { // No need to manually pad the date out with spaces, which will never be correct. // Just use an HStack and put a Spacer() in, so it goes: |<.....Spacer().....>Date| Spacer() Text(Date().formatted(date: .numeric, time: .omitted)) .foregroundStyle(Color.black) .fontWeight(.bold) .pad

When I created the first scheme on CK, there was no problem, but once I try to modify the scheme, adding more tables and adding more columns to existing tables, I got the same error. In my case there were some tables created automatically, like Users and CDMR. I just had to add SORTABLE and QUERYABLE to CDMR And it solved the problem. I ended up adding to every single table just in case 😅 Indexes: createdTimestamp: QUERYABLE and SORTABLE 2.modifiedTimestamp: QUERYABLE and SORTABLE recordName: QUERYABLE and SORTABLE I have added the above to all tables

It turns out that the problem isn't with GeometryReader, it's with LazyVGrid. I'm not clear on why, but my grid with 5 columns doesn't always report the same size. I can make it work by adding a 6th column that doesn't get used in the view. Very odd.

Hi @christiandevin It sounds like you want to convert a 2D point, on an image (of the left camera frame), to its corresponding location in 3D space. Before we discuss this, I want to bring your attention to a bug: The camera intrinsic matrix is row major instead of column major. I suspect this bug is the cause of the unexpected behavior @tsia observed. To account for this, look for the principal point and focal length at different positions in the intrinsic matrix (see snippet). Now let's turn to your goal. I'll refer to the 2D point on the image as the observation point. Using the camera intrinsic and extrinsic data with queryDeviceAnchor, you can convert the observation point to a 3D point (in world space) that represents the observation's location relative to the left camera's projection plane. That's not the same as its position in 3D space. Imagine seeing the world through a piece of glass (which represents the projection plane), the former is a point on that glass and the latter is the actual p

Look at your image and imagine there's a blue column immediately to the right of every red column. Now, the x-axis labels look like they're in the centre of the two columns. So, is your chart supposed to have two columns for each value? If not, in this line: AxisMarks(position: .automatic, values: shownXValues) { val in can position: .automatic be changed to something else? Also, is .useAppFont() a SwiftUI thing, or something you've written yourself? I've never seen it before.

Is there a way I can use the lldb user defined commands, which I can load from a KDK, to determine how much memory my kext has consumed? Is there a way to figure out what size blocks they are? Sort of. Keep in mind that your KEXT is simply a loadable library running inside the component, not an independant process/component. Just like in a user space process, there are a variety of mechanisms in place to associate memory allocations to components, but the information you get depends entirely on exactly what you're doing and why. In terms of commands, the kernel debugging command set has 400+ separate commands, many of which are specific to memory. You can see the full command list and a summary of each with the lldb command kgmhelp and each command accepts -h for more specific info. Taking zprint (one of the common starting points for looking at memory issues) as an example: (lldb) kgmhelp ... zprint - Routine to print a summary listing of all the kernel zones ... (lldb) zprint -h zprint: Routine to print a s