column

>> then I would lose preferred unit for localizationDo you have a use-case for this?It's a really odd requirement. If you don't know the unit of the resulting string, nor will anyone looking at it in the UI.I mean, if you're displaying a column of weights, you'd have to say what the numbers meant, somewhere. If do know that, then you don't need a measurement formatter (just use a numeric formatter on the number). If you don't know that, your numbers are meaningless.

Stating it like that shows that your goal is impossible. You've exposed your own false assumptions:— that any formatted measurement consists of 2 discrete parts: the formatted number and the units— that any spacing between the parts is composed of whitespace characters only— (worst of all) that the order of the parts isn't locale-specific (you don't return anything that indicates where the unit string was found in relation to the measurement string).These conditions might be satisfied in some locales, but it's wrong to believe they must hold everywhere.(What would you expect if the locale-specific string for 98 degrees Celsius was [the equivalent of] 2 degrees below boiling?)If you have a need to separate the quantity from the units, you can use a NumberFormatter for the number, and MeasurementFormatter.string(from:Unit) for the units. This would be appropriate if, for example, you were displaying a table with the numbers in one column and the units in another column. It wouldn't be appropri

Hi,Thanks for your answer but it doesn't make it clearer to me.To answer your question, I guess the tableView gets it's views by automatically invoking the method make(withIdentifier: owner:).About the tableView(_:viewFor:row:) delegate method, I don't implement it, as Apple says that when using Cocoa bindings, this method is optional if at least one identifier has been associated with the table view at design time, and If this method isn’t implemented, the table will automatically call the NSTableView method make(withIdentifier:owner:). And as recommended, I use the Automatic identifier in IB.Here's what I'm trying to say (and sorry if I'm not clear enough, probably because of my bad english):Let's say I have a view-based TableView (TV) in a view, stored in a nib File. Each column contains a tableCellView and each tableCellView contains different controls (for the example below, it's simply textFields). No bindings in IB at all, as I want them to be done in the viewController's implementation. So fa

It's unclear what you mean by One of the rows is of just plain string text. The other row of png images.A picker has different columns and each column has many rows. The column is called a component and is numbered from 0 to a few (like 2 or 5). There can be many rows. In your code, if wordPicker was 0 or 1 it would make sense - that would be the column, or component, that had the words in it. Each row in that column would have a height of 60. And each row in the other columns would have a height of 200.I suspect that wordPicker is not an NSInteger less than the number of columns (aka components) in the picker. The number of columns is set by your response to:- (NSInteger)numberOfComponentsInPickerView:(UIPickerView *)pickerView{ return 2;}

Thanks for the heads up about type inferencing. Ya, the top three rows all had many additions. When porting code from Objective-C, this problem has popped up a few times. I notice the literal type defaults to Double and I have to be more explicit with the Float type.I had some product results from vDSP_vmul accelerate methods. ( or what was the simd length 16 in Objective-C ) These results were being added together in the matrix array decleration. I figured there were enough adds to just call vDSP_vadd. Then I put those results into the matrix and the type inferencing issue went away. Ironically, Swift proded me to do an improved solution.Regarding arrays, I had another simple question but I want to be sure.😁 Again, just to be sure 100%, what is the proper Swift analog to a C array of a packed type on the stack -- not an array malloced on the heap. That is, the stack would contain memory of the atomic type float for instance without any other data structures. I'm assuming its Array of Float. And Array is goi

Hello PBK, Correct. My apologies in not clarifying it. One column is of imageComponent = 0, and the other stringComponent = 1. And I attempted both ways, of return for number of components: Return 2; //later Return component.count; In so much that when setting total component count with a mistake, only one row is displayed in Picker. In my situation, both are displayed correctly and return values for which each individually selected. I am even able to set the width for each row. Though I am not able to set individual row height.

Regarding arrays, I had another simple question …That’s your idea of a simple question (-:First things first, Swift arrays are (almost?) always allocated on the heap. The Array type itself is a struct, which is allocated on the stack, but the contents of the array is held in a heap-based buffer. It’s this indirection that allows for efficient copy on write (COW), appending and removing elements, and so on. Swift has no direct equivalent of C’s fixed sized array. When the C importer sees a C fixed sized array, it imports it as an N-element tuple, which works but is super kludgy and not the way you’d write the code in Swift itself.DSP-ish stuff isn’t really my thing, so I don’t have a lot of direct experience here, but if I were in your shoes I’d build an abstraction layer around these large buffers of floats so that you can explicitly manage their allocation, copying and destruction. If you’re explicitly trying to deal with mutable state (and thus avoid COW), you can make this a class and pass around a referen

I suspect that the reason no one has responded is that your question is cast in terms of spreadsheets, which are a bit hard to grok when you’re used to traditional programming languages. So I dusted off my copy of Numbers and looked up the VLOOKUP function. It seems to be equivalent to Swift’s array subscripting. For example: let sheet: [[Int]] = [ [1, 2, 3], [4, 5, 6], [7, 8, 9], ] let row = 1 let column = 2 print(sheet[row][column]) // prints “6”If you read the documentation on arrays and subscripts, that might put you on the right path.Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Thank you, I'll be sure to check out the documentation. Now, again, I'm new to Swift, so forget the silly questions, but can you generate array numbers based upon other array inputs?Basically, I want to have people input 3 numbers (which will be a part of the arrays), and have the rest of the array numbers generate in a certain manner from there. For example, if I want the user to input row 1, column 1, and from there, it would make, say, row 2, column 1 two more, and row 2, column 2 one more, could I do something like that?I assume I can.

Additionally, how does the array formatting go?Why would row 1, column 2 be 6? Are columns horizontal, and rows vertical here? Also, is there a 3-number limit per row of code? If I add a 4th number to each row, it still returns 6.SO confused regarding the order. It makes zero sense why the rows/columns aren't logically ordered.

If you look at Quinn's example:let sheet: [[Int]] = [ [1, 2, 3], [4, 5, 6], [7, 8, 9], ]and compare it to a spreadsheet, it would look like this: A B C 1 1 2 3 2 4 5 6 3 7 8 9 If we add a 4th number to each row, the spreadsheet would look like this: A B C D 1 1 2 3 95 2 4 5 6 96 3 7 8 9 97which would correspond to:let sheet: [[Int]] = [ [1, 2, 3, 95], [4, 5, 6, 96], [7, 8, 9, 97], ]Columns are vertical, but there are no real columns as in a spreadsheet. Instead, every row contains all numbers in the row. It is still easy to get a certain cell (or element, as we call it), since you first get the row you want and then get the column you want from that.There is no limit per row of code, but the second column of the first row will always be the same, even if you add numbers at the end of the row.One thing to remember is that in Swift (and most programming languages), rows and columns start on 0, while they start on 1 in most spreadsheets. Is this what confuses you?