Long push on button

[Nico595]

Ok, I designed a macro to monitoring the Interrupt and restart it when the Interrupt is frozen.

It's not a good solution but without more help from Matrix about the Interrupt, I can't do better.

[medelec35]

Hello.
I have replicated the issue and this will be looked into.
Many thanks for reporting this.

[medelec35]

Hello.
We have identified the cause of the bug and will ensure it is fixed in the next Flowcode release.
The bug can't be fixed by updating a component, it requires an exe fix.

[Nico595]

If I understand good, the next release is FC11.

Must I buy the FC11 Pro to use the Interrupt in the PC APP ?

I bought FC10 Pro but I ask me why ...

[Nico595]

I will contact my legal department in France.

It's not serious from Matrix. You can't sell a software with function failure and write, "fixed in the next release".

[Steve-Matrix]

While you wait for the the next release, be it v10.2 or v11, would like us to help find a workaround that allows you to progress with your project?

[Nico595]

Hello Steve,

Thank you for your message and your support.

I stopped my production in February to design the PC App project with Flowcode. I work on this project many hours ago and as you know, I am very happy to work with Flowcode.

If you design a simple software to control led, FC10 PC App is probably perfect. But if you want use the intelligence of the diagram to design a complex App, with keyboard, screen, filebuffer, timer, network control, you have necessary need interrupt function.

With my monitoring macro, the interrupt is restarted but it's not a good solution.

I only need the Interrupt functionality ready to use in the FC10 PC App and your support with fix job when we found a bug in the FC10. I am professional user, I can't accept buy the next version only because the FC10 PC App have a bug.

Thank you for your understanding.

[medelec35]

Hello I have attached a work around, If you are happy with it, I will then write instructions on how to add the timer function(which is very accurate) to your PD developer projects.
The timer can be expanded so you can have multiple timers running at different speeds will call different user macros.
I will have to created such example.

There timer will trigger from every 20ms to every 4294967295ms = 1 Month, 2 Weeks, 5 Days, 6 Hours, 57 Minutes, and 59 Seconds
So its very versatile.

The timer will stop when you stop the simulation, or you can add a button to stop the timer, which is simple to do.

To set your own time you what a macro to be triggered just set the Timer Milliseconds variable.
If you like the idea it could even be made into a component to make the process even simpler.

[Nico595]

Thank you so much Martin,

I think it's perfect.
I want check it in my project but the built in function is not run. I can read "Called back on the panel command System.TimerStart" at the top of the EvTimer macro page. How to do it ?

Edit: I find in the macro detail. I must add var in parameter in Event macro.
In my project Event macro are not called. Where is the panel command ?

Thank you

[Nico595]

I find how to do to place the Event with the Wiki.

I tried in my project, the Event Timer is not stopped but progress slow when I push a long time on a button.
This method is less fast than the timer with delay and less stable than the Interrupt.

I think use the Event Timer to run small tasks in background of the App. For the main clock, I will stay with my Interrupt and my monitoring macro waiting the Interrupt fix.

A Timer Event component is welcome.
Thank you.