So you basically want SetProperty block to wait the app until extension is created?
It was just my thought. im not sure how things will work on async method. im fine with any method you bring for us
This table may help you a bit
Asynchronous | Synchronous (current) | |
---|---|---|
Execution Speed | Same | Same |
Execution Time | Same | Same |
Execution Method |
Doesnât hang the main thread, other blocks will be executed before previous has task completed. |
Hangs the main thread, other blocks will be executed after previous task has completed. |
What happens when executing Create block |
It is unknown if the component is created or not because Create block wonât wait until the component is created. | It is known that component is created because Create block will wait until the component is created. |
What happens when executing SetProperty block |
It may give an error if the component is still not created yet. | It never gives an error because Create block will hang app until the component has created. |
How to learn if the component is created without an event? | Use a Clock to check if the component is created continuously. Otherwise, you canât know without using an event. | When the next block executes. |
How to learn if the component is created with an event? | Use the related event. | When the next block executes, or use the related event. |
this is why i need async
You can also check this post.
That will need lots of logic if you creating components in an arrangement - Because you have to wait until the component is finally created.
So whatâs your decision?
I will wait for more feedbacks, let me see what others will think about it.
thatâs so kind. i hope some people will involve.
This a good idea, If users will know the difference between them, then it will be helpful.
And also think about my request about the
Component Created
Event.
Hey guys, Iâve been using this extension for my app to build out my forms dynamically based on lists so that I can easily update what needs to be in there and push out updates. This has worked great for previous forms, like the daily truck check lists for our field technicians (this app is for a small lawn company). I am trying to build another one and everything seems to work fine in the companion until I build the app. Then I get a series of errors referring to trying to get an item of index 0 from a list.
I get four of these each showing the list with a different number of items, I am trying to build four sections of radio buttons out
I have tried to locate what is causing this and am coming up empty-handed. My employer is looking to impliment this ASAP and Iâm hoping I can get someone to help me track this down? I think itâs related to this extension, which is why Iâm posting this here. When I disabel the procedure that uses this extension to build out the sections the error stops (but the form doesnât build dynamically).
I have the sections listed out in a Dictionary like this.
Then I grab the keys and put them in a list that I use to create each section in initialize
Then I create the section.
Each individual component has a procedure as well, like this
and this
And I have a procedure to build out each question with the radio buttons needed.
I know this is long, Iâm just really stumped. Any help would be appreciated.
Not this extensionâs fault⊠Apparently trying to update the Checked property of a toggle switch with the block is what is messing it all up. Who knew?
Can anyone say me whatâs the code to create horizontal arrangements?
HorizontalArrangement
Opps, sorry i mean horizontal scroll arrangement
HorizontalScrollArrangement
How to Know Component Names -
OR
Hi, i just used this extension and on Ball & ImageSprite Speed porperty doesnât work!
To explain further i set the ball property for speed to 5 i got no errors but the ball doesnât move!
any suggestions?
If I delete the main layout, do the components inside get deleted?
Can I use the ids again?
No. You need to delete them too.