I’m trying to clone a row, and then I need to get the components in the row. This doesn’t seem to be working. Here are my blocks: [image] I’m getting an empty list for “all Label in clone”, although “clone” itself is populated. The label in the clone is unchanged. This is definitely related t…

So… If I add a wait block as the first block within the clone’s ‘do’, it works. Exactly as expected. Apparently ‘clone’ needs some time to get populated? ARGH. Asynchronicity makes my head hurt!

I feel like that should work. And yet it doesn’t. The green clone block holds an object (a row, copied from the original). So you should be able to get the first list item from the list of “all Label in clone”. Yet it doesn’t change the cloned label’s text so I’m a bit baffled. A clue is that it’s …

See my comments about an issue with the calendar app. [image] Create a 2020 Calendar Tutorials and DIY Guides Nothing wrong in the code. I tested it. When you run it as is it would, most probably, 111111. The cloning in the makeCalendar function works asynchronously and …

Interesting that you found that a wait block after the cloning loop was necessary. So it’s almost as if the clone block starts the process but the “all buttons” list isn’t populated with the new objects until all of the cloning is completed. My assumption would be that the “do” section of the clone…

I wasn’t actually cloning in a loop, but in response to a button click. As a single event, it still needs that wait. I really like Thunkable, but it annoys me that an early step in my debugging process has become sprinkling wait blocks everywhere to see if the problem vanishes. I want a “no, seri…

I realize yours wasn’t a loop which is what surprised me about needing the wait block. I’ve seen this happen where someone has a clone block or database lookup block inside a fast loop and the requests they are sending don’t have enough time to complete. But the fact yours wasn’t in a loop was what…

I think what’s different about my case is that I need a wait to use the contents of the clone WITHIN the do block of the clone itself. I thought those asynchronous purple blocks at least didn’t start on their ‘do’ until they were done… The clone value is populated right away, but the contents of t…

There was a problem like this a while ago. I can’t remember if it was with the clone block specifically but it may have been. The “do” section was simply running immediately. It was fixed so hopefully this isn’t a difficult fix.

Cloning and any component block - error or newbie problem?

Questions about Thunkable X

tatiang March 30, 2021, 9:08pm 4

Somebody who looks a lot like me figured out a while ago that a wait block was needed when cloning components as part of a loop but… you weren’t using a loop so that’s surprising.

Topic		Replies	Views
Last item displayed first when Cloning Questions about Thunkable X	7	465	June 9, 2021
Clone problem when changing properties with any component Questions about Thunkable X beginner , image , label , any-component , clone	1	327	September 17, 2021
Problems with new clone block Questions about Thunkable X	1	374	September 20, 2019
The "clone" block don't seem to refer to the just-cloned column Questions about Thunkable X	2	318	July 30, 2021
Cloning internal blocks with detail Questions about Thunkable X	3	571	September 6, 2019

Cloning and any component block - error or newbie problem?

Related topics