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

[oseamiya]

Example :

It can be used to set the property or invoke the component function of the components we have made using Dynamic component.

[luv.ak.tech (Aarush Kumar)]

@oseamiya

Example :

Lol you made before me but still example is example lol.

[iamwsumit (Sumit Kumar)]

It can do both jobs of GetProperty and SetProperty blocks. Even this block can call all the method and events blocks of the component that you can not do with only SetProperty blocks.

@luv.ak.tech

you made before me

Same here

[oseamiya]

Yeah

Also, there are some improvements in a pull request by @Xoma .

Fix bugs and improvements

[dora_paz (Dora)]

Well in most cases when I don’t use schema, I use set properties and dictionary blocks so I’m not familiar with that block. I will try to use it in order to understand better

[Xoma (Kumaraswamy)]

I had also addressed a bug in Dynamic Components:

[bodymindpower (Anke)]

I’ve only worked with DC a few times before (something simple with labels or buttons). So I’m not very familiar with it. Since I couldn’t find anything about this block either in the AI2 forum or here, there seems to be hardly anyone who has used this block before.

Thanks to all for the helpful hints on how this block works and for unveiling the secret (at least for me) surrounding this block.

[bodymindpower (Anke)]

And many thanks to @dora_paz, who is tirelessly busy on both forums (AI2 and here) and giving me some deeper insights into the DC extension (via PM).

[yusufcihan]

@oseamiya

It can be used to set the property or invoke the component function of the components we have made using Dynamic component.

Thanks for explanation!

@bodymindpower

Any idea what this block is about and how to use it?

Looks like it is already explained, but I will explain it anyway In simple terms, it is used to call a component’s function by using its name. It may be sometimes useful because in AI2, you define which method to call or which property to set/get before building the application. You can’t call a method dynamically in runtime.

Another example:

However, I don’t always recommend using “Invoke” instead of component’s own methods because Invoke block only supports basic types (int, string, boolean etc.) of parameters.

@bodymindpower

Since I couldn’t find anything about this block either in the AI2 forum or here, there seems to be hardly anyone who has used this block before.

You’re right, even including the above example, there is no actually perfect scenario that this block would be useful, I actually added this block for my own use, but is not needed for me either anymore.

@Xoma

I had also addressed a bug in Dynamic Components:

I merged the PR, here is the new build that includes your minor fixes if someone is interested. However, I don’t currently plan to announce as a separate version right now (the version name is 2.2.3 anyway), as it just contains few minor additions/fixes.

com.yusufcihan.DynamicComponents.aix (30.1 KB)

[bodymindpower (Anke)]

Thank you for the explanation!

[oseamiya]

Also In Thread Property, why there is UI and Main ? Aren’t main thread and UI thread are same? I guess one of the value name should be Async, or am i missing something?

[dora_paz (Dora)]

@oseamiya see …

@yusufcihan

Switching between async and sync are renamed as “UI” and “Main”.
They can be changed from the Designer. “UI” stands for asynchronous, and “Main” stands for synchronous.

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

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 …

[oseamiya]

I mean the terms UI thread and Main thread are same.

[hammerhai (Nathan)]

@oseamiya

why there is UI and Main ?

I’m sure you got this question from @Xoma, so here’s your answer…

Fix bugs and improvements

The property chooser has UI and Main as options because their references in Android documentation are alike. They’re also shown in the code itself (ex: runOnUiThread).

TL;DR: They’re self-explanatory.

[Xoma (Kumaraswamy)]

runOnUiThread refers to the main app thread. They are basically the same.

This is from Android blog:

[oseamiya]

@hammerhai

I’m sure you got this question from @Xoma,

I’d always a doubt whenever i have used DynamicComponents extension. I have known that Xoma has presented same question in his PR but I didn’t know it has been answered by you already.

@hammerhai

The property chooser has UI and Main as options because their references in Android documentation are alike

Btw, I don’t get it. Why there is UI and Main thread in property chooser if they are same?

@hammerhai

runOnUiThread

As far as I know, Activitiy’s runOnUiThread execute the Runnable code in the Main/UI thread.

---

Edit : Thankyou for explaining hammerhai at #1937 …

[hammerhai (Nathan)]

The problem is @oseamiya and @Xoma, that they might both be the same threads in the way they work, but they aren’t the same.

Difference between Main thread and UI thread in android

Turns out, UI and Main threads are not necessarily the same.

Dynamic Components isn’t misleading developers by having “two of the same thing, but differently named,” they’re just different. Developers at Google wouldn’t include a useless runOnUiThread for no reason, as from your standpoint, everything should already be running there… right?

F.Y.I @Xoma, in response to your pull request “They are basically the same, instead, it should be ‘Main’ and ‘Async.’” They aren’t and won’t ever be… not that I’m stopping you from submitting that change to your heart’s desire. There’s no such thing as “Async Thread” in Android.

[Xoma (Kumaraswamy)]

The thing is UI and Main may not be the same (by exact meanings).

@hammerhai

There’s no such thing as “Async Thread” in Android.

Generally speaking, “a new thread”.

[oseamiya]

Thankyou for the explanation !

[vladislav.svetailo (Владислав Светайло)]

Good day. I’m trying to create dynamically LineString inside Map.

But, it shows this error:

Is it possible to create components dynamically in Map?