Here it is
1 Like
May be you have more blocks but in these you are showing, I see thereâs no need to make the ID of the sprite a random number. Is it necessary? Why not use a fixed ID? May be that way it will work. Or save the random number in a variable and use that variable instead of the LastIDUsed block.
1 Like
Already done and I already tried with a fixed integer , with no benefit; those listed are all the blocks needed to check the component (it does not work in thunkable also). I think there is some sort of bug related to Imagesprite component only(?) because it works with e,g, button component
2 Likes
I was using an another method to delete the components, but I just noticed it behaves weird for some components, so instead of removing them from view, I changed the behavior of Remove block and now it makes the component invisible (by changing Visible property) instead of trying to remove it from view. Both methods are the same in theory, only backend was different.
Thanks for informing me about that! Remove block is now remade and I will publish the new version today which fixes that bug along with new blocks! 
(and for public source code 
)
6 Likes
Please, think carefully about this choice, the remove method frees memory and let you reuse the id, indeed a very good achievement. The visibility of each component is already managed by its properties, so now we are advised that for some components, at present, is not possible to destroy them and we can decide ourselves which method is better for our goals. Maybe in a future time you could manage to find a solution. Just an idea: you can try to contact Evans at MIT in his blog on appinventor and discuss the matter with him. He is deeply involved in developping Appinventor and a very kind person.
1 Like
Hi. Yusuf. I tested this component and I think it brings Kodular to another level.
I change all dynamic componentes by it. Kodular didnât have dynamic arrangents but I got to produce a list using it in place of Dynamic CardView.
Now I get to see Kodular as an OOP (Object Oriented).
I will continue to explore possibilities.
Thanks.
3 Likes
I think you also meant Java 
Thanks to Java, it would be impossible to make such an extension without using Javaâs features!
Thatâs the spirit! Also you can be sure about that I will continue to explore what can I do more for App Inventor!
Youâre welcome 
4 Likes
Thanks for using my extension and for 50 likes! Glad youâre liked it 
Now after a month of releasing the extension, here is the new version along with new blocks as I promised!
Version 1.1
5 new blocks!
-
GetName
Returns internal name of the component. -
SetProperty
Allows you to set a property for a component, I made that as replacement for Any Component blocks. So you wonât need to use Any Component blocks for setting properties of the component. It is an experimental block for now due to some value types not supported at the moment, sorry. Also it works for the properties which doesnât have a Setter block in Blocks area but have a setter method in the code. -
GetProperty
Allows you to get the property value of a component. -
RemoveAll
Same as Remove block, but it does that for all created components. -
GetDesignerproperties
Maybe most people wonât use it because they wonât need it
but it is useful to display all property names along with variable types of a component in app directly.
I also fixed the Remove block bug as @Tiziano1960 reported. Thanks!
Now extension is open source!
Starting from now, extension is now open source on 
GitHub! (to support open source of course 
) It is released on MIT license, and if you want to use the code or do something different, you must follow the MIT licenseâs terms. 
I updated the topic, you can find the new release from first post.
17 Likes
how I can use this extension to load images from different lists?
I have three lists of images. I know that how to use this for one list.
1 Like
Which block will allow to click on CardView and get ID?
1 Like
Oh, got the solution, thanks for this awesome extension.
2 Likes
How to ignore This ID is already used error. I want if id already there, then donât create or donât show any error
1 Like
That makes no sense. ID needs to be unique, because it is the key which identifies created component. You use the ID to access/manage/remove the component. Overwriting to existing ID means, other created component will be forgotten, and you wonât able to control it anymore.
So, it is not and wonât possible to ignore this error. You can add different text to end or start of the ID, so you wonât see the error.
2 Likes
I am using a view pager, and creating some cardview and text list from airtable, when view pager position 1 is selected, showing some data, and later when I am going to viewpager position 2, it is showing data, but when I am returning to the same position again, it is giving this error.
1 Like
Solution 1:
Remove your old components before creating new ones with same IDs.
Solution 2:
Create two instances of DynamicComponents extension by dragging and dropping new one to the Designer.
Solution 3:
Add another text to the IDs for different ViewPages. For example add ViewPager1 text to the ID for your first ViewPager, then change it to ViewPager2 for other ViewPager component.
3 Likes
Not possible this way⊠when the same position is selected, I can only empty list my airtable list view data,
Here, viewpager arrangements are also dynamic.
please check the aia file I have messaged to u
1 Like
If you add RemoveAll block to your code, you can delete all created component with one block.
1 Like
I tried, showing error.
1 Like
Strangely, I couldnât get the same error in blank project. I will try later, and will let you know if I find the problem.
2 Likes