Join us in Beta Testing the new Layouts component! (Rows / Columns for the Drag and Drop Interface)

[mimostel]

more specific: container’s height fit contents, it’s width still fill container. If both fit contents, is working.

[mimostel]

@muneer

The main idea of the container is to change the layout behavior of the button

Well, as a “passionate” StP user trying to get to DnD, maybe my mistake is to look at new layouts literally as rows/columns … I’m doing this because if I wanna work with clones, I need to multiply, for example, a button on a row (horizontal layout)… and need to define source button’s height/width in connection with screen’s layout, so the final result will show, lets say, 9 butons equally sized, that horizontally fill the screen.

[muneer]

@mimostel

container’s height fit contents, it’s width still fill container.

Let me confirm your findings. When you set either height or width to fit content the button shows in the computer preview but not in the mobile app.

@mimostel

I need to multiply, for example, a button on a row (horizontal layout)

I do hope to reach this stage soon. Now we need to fix the issues in the layout and then move to the clone function to see how it can be incorporated in this solution.

[jon.fawcett8aghe]

[quote=“muneer, post:23, topic:1970795, full:true”]

@mimostel

container’s height fit contents, it’s width still fill container.

I am seeing this same issue. With a non-scrollable screen, you usually don’t want all containers with height of fill. Here is a simple example that doesn’t work.

header and footer containers: height fit contents
content container: height fill container.

This works fine on the web preview but on a device, it collapses the contents of the header and footer. Setting the item inside the row to fit, fill, or absolute all produce incorrect results if the row is set to fit contents. Probably related: switching the inside item width between fit/fill doesn’t change anything. But switching the height to fill expands the width of the button instead.

[vishruth-ram]

Can’t wait to check this out! See how easy it would be if features of both platforms come in one place.

[tthompson41231]

I definitely would love to try this. When is the release window for this update?

[tatiang]

Are there known issues with creating and then selecting custom Data Viewer List (DVL) layouts in Drag & Drop? The layouts appear as blank lines in the selection panel.

I showed the problem here:

Button not registering clicks properly

That sounds promising but I’m not having much luck. I created a layout with a container that has a button inside. I gave the button a background color and text and saved the Layout component as a custom layout: [image] But then when I go to select it as the DVL layout, it shows up blank (the last two or three entries are blank) and clicking in that area doesn’t do anything: [image]

[tatiang]

Okay, I’ve solved the issue with blank custom DVL layouts. I was saving the Layout in the component tree but it turns out that I need to save the Container in order for it to show up in the list of custom layouts within a project. I don’t know if I was supposed to be able to save a Layout but that part still isn’t working. Regardless, I can now use custom layouts created in DnD with Layouts as long as I select the Container before saving.

Edit: Except it’s not registering button clicks (a button inside the saved container) in the DVL.

[tatiang]

Does anyone have a custom data layout that works and was made in DnD that they can share with me?

Sorry, not trying to hijack this topic… but it is related to Layouts.

Edit: Thunkable Staff are looking into this for me. I did discover something interesting: the click event is detected for the Container that the Button is in but the Button itself does not register a click event. So since the Container is wider than the Button inside of it, that’s the reason that “edge” taps seem to work. It’s actually catching part of the container.