[F/OS] - Dynamic Components Extension (for every component) 2.3.0

I would use the name as the ID, so just put GetID in the start value
For me, the ID will always be unique

using these blocks I was able to reach a satisfactory result, each list ID was defined as unique (Using 1 “DinamycComponent” for each item in the layout)

A example

How do I know that it is a dynamic and not real
blocks (5)

Try this
blocks (2)
Or change the “-1” to number “-1”
image

Edit: I tested just now, but I found that it returns an empty string instead of “-1”

1 Like

My bad, I fixed the block description for next release.

4 Likes

He has already show all blocks in the procedure, what do you expect?

If he didn’t call procedure, then the error won’t occur

No.

You should do it, the photo shows the full block of procedure block (tap in the photo and download it, look carefully, the photo is height is 10889 pixels.)

blocks1
I don’t know if it is

1 Like

These are my full blocks

I am getting hs result

1 Like

can i make same to same this picture



i need it fully dynamic.
i want to post from firebase like this.

wdym? You can always do it. Just use Card view, or different arrangment.

You can’t use the same ID to every component.

1 Like

@yusufcihan, I need your help please.
Why is this not working? I tried everything I can think of already.
The component is a ball. Is created successfully.

Try removing spaces from X

1 Like

There’s no spaces.

The Set Property block does not work reliably
 Try using a “set Any Ball.x of component” block.

Ok, that works, but for some properties.
For speed, doesn’t. I mean, I can set the x,y of a ball that way but not the speed. Could it be something in the extension that is not linked to that property?

1 Like

And this brings up another problem.
In the standard AnyBlocks, we still don’t have the SetOriginAtCenter property for the balls. I was really hoping to be able to set it from the extensions blocks.
@Vishwas, do you know if that property block will be added soon?

3 Likes

I’m not very sure. @Conor might have more info as the property has been ported over from App Inventor

3 Likes