QGrid | 🎛 QGrid : The missing SwiftUI collection view | iOS library

Try using onAppear instead of init

You need to initialize canales variable inside the VerCanales view init.

Since this question has a bounty on it, I can't mark it as duplicate. To show the dataframe in another tab, you can use a little JavaScript. According to this post, here is a code that will show the dataframe in another tag:

Try the following (cannot test it due to many dependencies absent, so just idea)

Note that interact behaves differently to the interactive decorator. When using interact, the first argument should be a function/callable that gets called when you change any of the widgets. You passed in the dataframe df as the first argument, and therefore interact is trying to call df as a function with the start_date and end_date keywords. Hence the error, as dataframes are not callable.

Have a look at the documentation for examples, you probably want to build a simple function to filter your dataframe, and use that function name as the first argument to interact.

https://ipywidgets.readthedocs.io/en/latest/examples/Using%20Interact.html#Basic-interact

You can try the Qtable widget:

GeometryReader may be a "hacky" solution, but it is the solution we have at the moment. It is possible to create a solution that reflows a small number of items dynamically, or a large number of items with a delay. My demo code would be unwieldy here, but it sounds like describing my approach may be useful.

Behind the scenes, SwiftUI is doing all kinds of optimized constraint solving to layout your views efficiently. In theory, reflowing content like you describe could be part of that constraint solving; in today's SwiftUI, it is not. Therefore, the only way to do what you are describing is some variant of the following:

1. Let SwiftUI lay everything out based on our data model.
2. Get the widths that SwiftUI decided on using Geometry reader and preferences/callbacks.
3. Use these widths to solve our reflow constraints.
4. Update the data model, which will trigger step 1.

Hopefully, this process converges to a stable layout, rather than entering an endless loop.

After playing around with it, here's what I've gotten so far. You can see that a small number of items (29 in my example) reflow almost instantaneously as the width is changed. With a large number of items (262 in my example), there is a noticable delay. This shouldn't be much of an issue if the content and view width don't change and won't need to be updated frequently. The time is spent almost entirely in step 1, so until we get proper reflow support in SwiftUI, I suspect this is as good as it gets. (In case you're wondering, the vertical scrollview scrolls with normal responsiveness once the reflow is finished.)

Essentially, my data model starts with a [String] array and transforms it to a [[String]] array, where each internal array corresponds to one line that will fit horizontally in my view. (Technically it starts with a String that is split on whitespace to form the [String], but in a generalized sense, I've got a collection I want to split into multiple lines.) Then I can lay it out using VStack, HStack, and ForEach.

My first approach was to try to read the widths off the actual views I'm displaying. However, I quickly ran into infinite recursions or weirdly unstable oscillations because it might truncate a Text view (e.g. [Four] [score] [and] [se...]), and then un-truncate once once the reflow changed, back and forth (or just end in a truncated state.

So I decided to cheat. I lay out all the words in a second, invisible horizontal scrollview. This way, they all get to take up as much space as they want, never get truncated, and most importantly, because this layout only depends on the [String] array and not the derived [[String]] array, it can never enter a recursive loop. You may think that laying each view twice (once for measuring width and once for displaying) is inefficient, but I found it to be dozens of times faster than trying to measure the widths from the displayed views, and to produce proper results 100% of the time.

You cannot use the package to create a grid without data. If you look at its code, there is only one QGrid initializer, and it requires data.

Here's a minimal example:

You are adding dashes between class names, where no such dashes exist. The element you are selecting has two classes, perhour and rowmargin, but you are selecting on a non-existing class perhour-rowmargin. The same applies to the td elements; they have separate classes fulltime and innerTableCell

Just pick one or the other for both; the following returns the cells you want: