It was probably the use of egcs 1.03 compiler that help keep the bug
down. ;-)
Keep us posted. I would be glade to alpha test again if you need.
Later,
Dave
Albrecht Kleine wrote:
> May be you are right, but anyway: it is a bug in tya.
> Tonight I've no solution for you, but as workaround
> tr
You wrote:
Sorry for late answer, but I've spent some nice holidays
far away from home.
> > I've tested this small application (jdk116-v2 with a RH 5.1) and
> > I've discovered a memory corruption:
> > when the focus is lost from the TextField I assign 0 to the local
>
> Might be related to j
[EMAIL PROTECTED] wrote:
>
> Hi,
> I've tested this small application (jdk116-v2 with a RH 5.1) and
> I've discovered a memory corruption:
> when the focus is lost from the TextField I assign 0 to the local
> variable var1, if the parseInt throws an exception (i.e. I don't
> write ant value in TF
Hi,
I've tested this small application (jdk116-v2 with a RH 5.1) and
I've discovered a memory corruption:
when the focus is lost from the TextField I assign 0 to the local
variable var1, if the parseInt throws an exception (i.e. I don't
write ant value in TF) the content of var1 is corrupted: it a
