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

oseamiya · February 16, 2022, 2:06pm

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 · February 16, 2022, 2:07pm

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

iamwsumit · February 16, 2022, 2:09pm

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.

Same here

oseamiya · February 16, 2022, 2:18pm

Yeah

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

github.com/ysfchn/DynamicComponents-AI2

Fix bugs and improvements

ysfchn:beta ← XomaDev:beta

opened 03:41PM - 23 Oct 21 UTC

XomaDev

+120 -124

Fixes some bugs and overall improve the code. Highlights: ![23 10 2021_20 …16 35_REC](https://user-images.githubusercontent.com/71964026/138562749-3d84dc26-4959-47c0-ab5e-2d644504322b.png) This is a current bug that affects invoke results that have spaces and are not fully empty. The behaviour expected is for it to return an empty string same as, set to the Button1.Text. This was because the `isEmptyOrNull` also checked if a string is empty by replacing spaces. And why does the Thread property chooser in the extension has the value "Main" and "UI"? They are basically the same, instead, it should be "Main" and "Async". (Note I haven't changed the names in this PR).

dora_paz · February 16, 2022, 2:20pm

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 · February 16, 2022, 3:25pm

I had also addressed a bug in Dynamic Components:

bodymindpower · February 16, 2022, 5:41pm

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 · February 16, 2022, 5:49pm

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 · February 17, 2022, 11:05am

Thanks for explanation!

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.

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.

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 · February 17, 2022, 1:19pm

Thank you for the explanation!

oseamiya · February 19, 2022, 2:27am

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 · February 19, 2022, 10:52am

@oseamiya see …

oseamiya · February 19, 2022, 12:44pm

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

hammerhai · February 20, 2022, 1:56am

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

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 · February 20, 2022, 6:43am

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

This is from Android blog:

oseamiya · February 20, 2022, 2:32pm

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.

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

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 · February 20, 2022, 10:57pm

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.

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 · February 21, 2022, 3:43am

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

Generally speaking, “a new thread”.

oseamiya · February 21, 2022, 12:50pm

Thankyou for the explanation !

vladislav.svetailo · February 21, 2022, 3:56pm

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

blocks(3)

But, it shows this error:

Снимок экрана от 2022-02-21 17-52-43

Is it possible to create components dynamically in Map?