Extension For Any Event

[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

[Aarush_Kumar]

@patel

in which cases would I NEED to use this extension

For logging purposes or maybe if you have a huge amount of components and cant drag blocks for every single one then?

[patel]

what's the use of args ? In my test it's always empty

[Aarush_Kumar]

@patel

args ? In my test it's always empty

it means arguments some events return some variables that what args return. but if event does not return anything it is empty.

[ABG]

Is it possible to have mercy on subsequent readers of blocks using this extension, to make it easier for them to see the event delivery method?

For example, if the proc event() block were replaced with a
ExtensionName.EventLogged event block, that would reduce the possibility of sending an unsuspecting reader chasing through all the blocks searching for a call event() block.

[Wes_Savage]

Dreamin' (Johnny Burnette 1960)

I must admit that having one of my screens 2,000 blocks long and none of the logic written down I, mentally, know "the picture" and can trace but there is always that lingering thought "what if I missed something". Recompiling, using, tweeking and recompiling is very lengthy and variable chasing can be bothersome.

WISH:
It would be really great if there were an AnyVariableEvent Extension.
When developing, the first phase (alpha not beta ) the developer is also the tester of the viability of the app. To be able to listen for when a variable changes state (and which module it changed in) would seriously decrease development time?

In my vision adding the extension then having a module which would contain the named variables to watch and putting each of the variables changes in a file or list for viewing would be the way to go. After detecting a problem the developer could call to show the VariableEvents. The module for naming the variables to watch should only be one singular module. No calls in any of the routines of the particular screen.

@Kumaraswamy. @ABG