On Sun, 04 Oct 2015, Beno??t Minisini wrote:
> >> It's not technically necessary to do that, but it avoids a lot of
> >> possible annoying bugs in your code.
> >>
> >
> > I understand. And by the way, that Timer trick works even in the following
> > form:
> >
> > --8<--[ ValidateBox.class]-
Le 04/10/2015 18:43, Tobias Boege a écrit :
> On Sun, 04 Oct 2015, Beno??t Minisini wrote:
>> Le 04/10/2015 18:29, Tobias Boege a ?crit :
>>> On Sat, 03 Oct 2015, Beno??t Minisini wrote:
> Is there a limitation, about raising events from constructors, I don't
> know
> of? Also note how
On Sun, 04 Oct 2015, Beno??t Minisini wrote:
> Le 04/10/2015 18:29, Tobias Boege a ?crit :
> > On Sat, 03 Oct 2015, Beno??t Minisini wrote:
> >>> Is there a limitation, about raising events from constructors, I don't
> >>> know
> >>> of? Also note how, in the demonstration project, I can very well
Le 04/10/2015 18:29, Tobias Boege a écrit :
> On Sat, 03 Oct 2015, Beno??t Minisini wrote:
>>> Is there a limitation, about raising events from constructors, I don't know
>>> of? Also note how, in the demonstration project, I can very well initiate
>>> the validation procedure just after the constr
On Sat, 03 Oct 2015, Beno??t Minisini wrote:
> > Is there a limitation, about raising events from constructors, I don't know
> > of? Also note how, in the demonstration project, I can very well initiate
> > the validation procedure just after the constructor finished.
> >
>
> The logic behind that
Le 03/10/2015 01:22, Tobias Boege a écrit :
> Hi,
>
> I'm puzzled by some behaviour of the interpreter when objects raise events
> from their constructors.
>
> The following big block of text just gives the rationale of my question. I
> think what I'm doing is not too strange. There is a short demo
