Extension For Any Event

[Aarush_Kumar]

@Kumaraswamy

if I change that to "Initialize" it will break things.

Maybe make the block name InitializeExtension or InitializeAi2Tools

[Anke]

The Completed event is triggered about 80ms later than with the Player component.

[Kumaraswamy]

Hmm that is because the extension needs to find the procedure and do some internal changes. I will do some changes if possible.

[Anke]

[oseamiya]

Good Work @Kumaraswamy !
Will love to see the source code to know how it works internally if you make it open-source

[Aarush_Kumar]

@oseamiya

Will love to see the source code to know how it works internally if you make it open-source

[Extension Suggestion] Can anyone make an extension where there is a common block for event?

One possibility is that you've made a loop by catching all of the events and reporting them via your new extension's event block, which will trigger your code again, ad infinitum. Your extension is observing the same system it's a part of and therefore things can get tricky. Another approach might be to replace form$Mnenvironment with a special subclass that will return a function object that can be applied when an event name style signature is detected. Again, you'll want to make sure you aren…

read the topic from the post i gave. it might give you a idea.

[Kumaraswamy]

Fix 1.2

• Fixed the latency issue, now extension takes much less time to post events

xyz.kumaraswamy.ai2tools.aix (10.2 KB)

[Kumaraswamy]

GitHub - theItoO/Ai2Tools: Ai2Tools adds a few extra abilities to appinventor

Here is the source code of the extension

---

@Aarush_Kumar, It is a different approach as that one didn't work correctly as expected.

[oseamiya]

Thankyou @Kumaraswamy .

[Anke]

It doesn't seem to work with Kodular (Companion, APK not tested).

[Kumaraswamy]

I checked it in Kodular companion and it works fine.

[Anke]

@Kumaraswamy

I checked it in Kodular companion and it works fine

No, not for me:
eventTest.aia (12.6 KB)

Summary

[Kumaraswamy]

Hmm Im not sure if this has to do only something with kodular since an event KeyboardVisibility seems to trigger infinitely.

Edit: Can you test if the same things work on Ai2?

[Anke]

Of course it works with AI2.

[Kumaraswamy]

The reason is just after the button is clicked other events get triggered and the label changes, adding a compare logic solved it.

[Kumaraswamy]

Okay got it, its because kodular is calling an event continually which causes this behaviour.

Keyboard Visibility Event triggered endlessly

[Anke]

@Kumaraswamy

The reason is just after the button is clicked other events get triggered and the label changes, adding a compare logic solved it

[patel]

Can you attach an aia example where you NEED to use this extension ?

[Aarush_Kumar]

@patel

where you NEED to use this extension ?

This extension can listen for events for all components

[patel]

OK, but for Button click I can use When Button Click, in which cases would I NEED to use this extension