“column”

It's now possible in SwiftUI with TableColumnForEach [1] But don't use it. I tried and I got crashes when reloading data using Observable, I got crashes when changing columns. My app hung and needed killing when switching away from the table view and back. It crashes if there are zero columns. It's also really slow. Unusably so with about 200 rows and 150 columns. I tried with a release build and no difference was noticable. NSTable on the other hand handles everything admirably. [1] https://developer.apple.com/documentation/swiftui/tablecolumnforeach

@txoof import numpy as np import pandas as pd import matplotlib.pyplot as plt from sklearn.preprocessing import MinMaxScaler from tensorflow.keras.models import Sequential from tensorflow.keras.layers import Input, LSTM, Dense, Dropout import tensorflow as tf from tensorflow.keras.callbacks import EarlyStopping import logging # Suppress warnings logging.getLogger(tensorflow).setLevel(logging.ERROR) logging.getLogger(urllib3).setLevel(logging.ERROR) # Verify GPU availability physical_devices = tf.config.list_physical_devices('GPU') print(fGPUs Available: {bool(physical_devices)}) # Load data with flexible features def load_data(filename, features=['Close']): df = pd.read_csv(filename, parse_dates=['DateTime']) df['DateTime'] = pd.to_datetime(df['DateTime'], format='%Y.%m.%d %H:%M:%S') required_columns = ['DateTime'] + features df_cleaned = df[required_columns].dropna().sort_values('DateTime') if df_cleaned.empty: raise ValueError(Dataset is empty after cleaning!) return df_cleaned, features # Example using mul

@captmagnus You should try using navigationSplitViewColumnWidth(min:ideal:max:) to set the preferred width for the column and .windowResizability(.contentSize) for the resizability strategy. For example: WindowGroup { ContentView() } .windowResizability(.contentSize) struct ContentView: View { @State private var columnVisibility = NavigationSplitViewVisibility.all var body: some View { NavigationSplitView(columnVisibility: $columnVisibility) { Text(Sidebar) .navigationSplitViewColumnWidth(min: 300, ideal: 300) } detail: { Text(Detail) .navigationSplitViewColumnWidth( min: 600, ideal: 600, max: 900) } .onChange(of: columnVisibility) { print(columnVisibility) } } } It's also worth filling a bug report for the animation hitch. Bug Reporting: How and Why? has tips on creating your bug report. Post the FB number here once you file the bug report.

Could be useful for someone, here's an example of script for Numbers to manipulate the content, cells and rows with placeholders: set newList to {} repeat with anItem in theList set newList to {anItem} & newList end repeat return newList end reverseList on replaceText(theText, searchString, replacementString) set AppleScript's text item delimiters to searchString set textItems to text items of theText set AppleScript's text item delimiters to replacementString set newText to textItems as text set AppleScript's text item delimiters to return newText end replaceText tell application Numbers tell document TestNum repeat with s in sheets tell s repeat with t in tables -- Create a static list of row indices set totalRows to count of rows of t set rowIndices to {} repeat with i from 1 to totalRows copy i to end of rowIndices end repeat set revIndices to my reverseList(rowIndices) repeat with iRef in revIndices set rowNum to iRef as integer -- Directly use row rowNum of t to access the row set numCells to count

Nowadays the metal shading language specification states that it's possible, but still it doesn't specify the order, section 2.3.2 Matrix Constructors says: Since Metal 2, a matrix of type T with n columns and m rows > can also be constructed from n * m scalars of type T. The following examples are legal constructors: float2x2(float, float, float, float); float3x2(float, float, float, float, float, float); I'm too lazy to bounce data to the shader and back just to check, but I'd appreciate if anybody who knows would answer to the initial question, and even better would make a clarification in that document BTW the document: https://developer.apple.com/metal/Metal-Shading-Language-Specification.pdf

UPDATE : I was able to narrow down my metadata errors vaslty. The only error that sustains is as follows. Package Summary: 1 package(s) were not uploaded because they had problems: /Users/isseyyohannes/Desktop/ALGORA_Performance.itmsp - Error Messages: ERROR ITMS-3000: Line 16 column 15: element versions not allowed here; expected the element end-tag or element metadata_token at XPath /package/versions ERROR ITMS-3000: Package null failed schema validation. [2025-02-20 12:23:44 EST] DBG-X: Returning 1 This is the structure of my metadata file. GL5BCCW69X GL5BCCW69X ALGORA_Performance.pkg ALGORA Performance Trading made easy. This app is optimized for macOS trading. Any insight on to what I may be doing wrong in my metadata.xml file would be appreciated. Thank you. Note : md5 was hidden on purpose.

Hi @NahtanMak I was able to achieve a similar effect using shader graph. I adjust each pixel's opacity based on its distance from the center of the image. I used texture coordinates to calculate that distance. Here's how to setup the graph: Add an Image node. Connect its Out to the color property on an UnlitSurface. Add a TextureCoordinates node. Connect its Out to the In of a Remap node. For both columns of the Remap node, change:Out Low to -1 and Out High to 1. Drag its Out to the In of Magnitude node. Drag the Out of the Magnitude node to a new Remap node. Set Out Low to 1 and Out High to 0. Drag the Out to Opacity on the UnlitSurface you created in the first step. Note: you can change the In Low property on the Remap node you created in the previous step to control when the gradient begins. If you set it to 0 the gradient will start in the center of the image. If you set it to 0.5 the gradient will start 50% from the center of the image. If you set it to 1, there will be no gradient. Please accep

Thank you. I decided to keep trying at it - as my code base was a little too much to simplify in order to share it. I couldn't solve it no matter what I did at a granular level. BUT, when I simply removed my measuringLayoutManager and had all code use a single layoutManager, the problems went away. Something in the text system really did not like it when I had more than one layout manager laying out the same text storage, even though I ensured that that second layout manager used a separate set of text containers, and even though those text containers were not tied to any views, nor ever passed as objects/references. Merely having a second layout manager assigned to the text storage, doing layout passes into its own containers in order to calculate sizes seemed to be the source of the problem. I simplified and am using a single layout manager now. My calculated sizes are the same as they were when calculated by my second measuringLayoutManager. So there was nothing wrong with the calculations there. But I no