Re: New control structure "Do Next..."

[Fabien Bodard <gambas.fr@xxxxxxxxx>]

Fabien Bodard

Le sam. 17 mai 2025 à 12:39, Benoît Minisini <
benoit.minisini@xxxxxxxxxxxxxxxx> a écrit :

> Le 17/05/2025 à 10:29, Fabien Bodard a écrit :
> > Hem...
> >
> > I understand the idea as the procedure is like stored in a trigger array
> > for post activation.
> >
> > So the loop continue until the end and then the procedure is called.
> >
> > But I don't understand the need.
> >
>
> I use this pattern for a lot of things, especially with GUI toolkits.
> For example :
>
> - Raising a Click event outside of a MouseDown event handler.
>
> - Reparenting a window after it has been closed, because GUI toolkits
> seems not to like reparenting directly in the Close event handler.
>
> - Raise a "Modified" event once, and not for each modification during
> the same event loop.
>
> ...and so on.
>
> It's funny that you don't understand the need, whereas you wrote the
> DocumentView class which uses this pattern constantly. Just search for
> the "Trigger" method applied on Timers. There are fourteen occurrences!
>

Got it 😅

But I just wanted to be sure of my understanding.

In fact you formalize the timer trigger tip to avoid the need to declare
many timer for single trigger use.





> Regards,
>
> --
> Benoît Minisini.
>
>
>