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

Extensions
,
#1037

Screenshot_20200806-184152
Screenshot_20200806-1841521080×2160 355 KB

It is a component in the unities.

Then drag the set margin.
Set to 0 or lower

3 Likes
#1038

I would be happy to send me blocks :heart_eyes:

#1039

is it’s correct ?

Screenshot_20200806-162206
Screenshot_20200806-162206770×419 51 KB

#1040

Yes, or you can specify which side. The format is
(Top),(left),(bottom),(right) as I remembered. Tru
0,5,0,5

#1041

:sweat: :sweat: :sweat: :sweat:
not working

#1042

not working help please

Screenshot_20200806-162206
Screenshot_20200806-1622061147×577 93.1 KB

#1043

Try 0 or -5

#1044

yes trying

#1045

love you :heart: :heart: :heart: :heart:
its working

1 Like
#1046

When we keep value 0 there is no noticeable difference when we keep -4 or greater then it affect.

As per my experience with decoration component

1 Like
#1047

Please add a option to create the components async (maybe UI thread will not be paused if created async?)

also,maybe another version of extension that works async?

#1048

I think @yusufcihan has explained why async is not needed in the first post.

#1049

yes, i’ve seen that but still async will help in some ways like when loading a large listview with a lot of components in it? it is just my opinion.

#1050

How it will help? :thinking:

#1051

i’ve already mentioned that.

#1052

I ask in terms of what will it help? Time consumption?

#1053

Just understand how loading async works. i asked for that benefits. let’s wait for @yusufcihan to look into my suggestion. also, it is not really needed in most cases but in some. and…

1 Like
#1054

Async tasks have limitations along with benefits.

You won’t learn when/if the component has created without using an additional event.

EDIT:
I’m thinking of publishing the new versions with two releases, as asynchronous and as synchronous. So people can use any release that they want. And both can be updated together, maybe? :thinking:

#1055

Exactly.

Because you are such a amazing developer who broke the limitation of custom listview on MIT, i really hope you can find a way to deal with it. you’ve done that no one else did.

when setting properties, is it possible that the extension first checks if the component has been created and set only when done? or any other way that will set properties of component created with async method?

did you know if the listview of popular apps like facebook created with async method?

#1056

Yes, but it is not needed for synchronous. If it is asynchronous, it needs a additional event block to trigger. To know if the component has been created, check if the ID contains in the UsedID list.