Le 22/12/2012 15:08, Charlie Reinl a écrit :
> Am Samstag, den 22.12.2012, 14:03 +0100 schrieb Benoît Minisini:
>
>> Sorry, but I don't understand: I can't see how a list of local variables
>> sticked to their values can be used to rewrite code... And I can't keep
>> an hidden pop-up menu with only
Am Samstag, den 22.12.2012, 14:03 +0100 schrieb Benoît Minisini:
> Sorry, but I don't understand: I can't see how a list of local variables
> sticked to their values can be used to rewrite code... And I can't keep
> an hidden pop-up menu with only one entry in the interface, so I must
> underst
Le 22/12/2012 13:54, Charlie Reinl a écrit :
>
> Oh, I see, you talk about the PRINT, isn't it.
> Yes that's left from Ctrl+C tests, I will clean up that code.
>
> For the need to list name and values of all local variables (out from
> the Clipboard).
> I have to split some huge procedures into lo
Am Samstag, den 22.12.2012, 13:23 +0100 schrieb Benoît Minisini:
> Le 22/12/2012 13:17, Charlie Reinl a écrit :
> >> But please explain why you have added that dump feature that print on
> >> the standard output with a pop-up menu with-only-one-entry interface?
> >> Very bad taste!
> >>
> >
> > Sal
Le 22/12/2012 13:17, Charlie Reinl a écrit :
>> But please explain why you have added that dump feature that print on
>> the standard output with a pop-up menu with-only-one-entry interface?
>> Very bad taste!
>>
>
> Salut,
>
> may be, but I wanted no change on the layout for one button, Ctrl+C on
Am Samstag, den 22.12.2012, 00:08 +0100 schrieb Benoît Minisini:
> Le 22/12/2012 00:01, Karl Reinl a écrit :
> > Salut Benoît,
> >
> > have you ever heard from NOT working breakpoints, and/or can you imagine
> > a reason why?
> >
> > Since yesterday, I'm not sure if it is always or only sometimes,
Le 22/12/2012 00:08, Benoît Minisini a écrit :
> Le 22/12/2012 00:01, Karl Reinl a écrit :
>> Salut Benoît,
>>
>> have you ever heard from NOT working breakpoints, and/or can you imagine
>> a reason why?
>>
>> Since yesterday, I'm not sure if it is always or only sometimes, but
>> actually the inte
Le 22/12/2012 00:01, Karl Reinl a écrit :
> Salut Benoît,
>
> have you ever heard from NOT working breakpoints, and/or can you imagine
> a reason why?
>
> Since yesterday, I'm not sure if it is always or only sometimes, but
> actually the interpreter don't stop on breakpoints!
>
> I remember some t
Salut Benoît,
have you ever heard from NOT working breakpoints, and/or can you imagine
a reason why?
Since yesterday, I'm not sure if it is always or only sometimes, but
actually the interpreter don't stop on breakpoints!
I remember some times ago I had remarked that, but after it reworked.
Wha
