Thanks Jussi, Now I think I really understand :)
Dominique Simonart
Jussi Lahtinen a écrit :
> No, I think it is exactly same problem.
>
> Here is the reason (just like in my code):
> PUBLIC hMyClass AS NEW Object[]
>
> Only difference is how we populate that array.
> I use fResult.Add(aa) and
No, I think it is exactly same problem.
Here is the reason (just like in my code):
PUBLIC hMyClass AS NEW Object[]
Only difference is how we populate that array.
I use fResult.Add(aa) and you use hMyClass[i] = NEW MyClass (and
hMyClass.Resize(9)).
Result is very same.
Read my post and followups
Oups, forget to join the source!
Dominique SIMONART a écrit :
> Jussi (sorry for the preceding Julien)
>
> I wonder if our problems are really the same!
> Here is more details of my situation. As you can see, the READ should
> know that the datatype of hMyClas[i].X *is* a byte
>
>hMyClass.Resi
Jussi (sorry for the preceding Julien)
I wonder if our problems are really the same!
Here is more details of my situation. As you can see, the READ should
know that the datatype of hMyClas[i].X *is* a byte
hMyClass.Resize(9)
FOR i = 0 TO 8
hMyClass[i] = NEW MyClass
' using these two
Hi Julien,
You are right!
I read your post and I understand the reason,
but you don't speak about Signal 11, so I was thinking for
another problem although similar
regards,
Dominique Simonart
Jussi Lahtinen a écrit :
> Hi!
>
> Is hMyClass declared as Object[] ?
> If so, READ cannot recognise hMy
Hi!
Is hMyClass declared as Object[] ?
If so, READ cannot recognise hMyClass[i].X as byte.
See my earlier post "Minor bug with READ & WRITE commands?".
I think you have same problem than I did, and in fact it is not bug.
Jussi
On Thu, Jan 22, 2009 at 1:06 AM, Dominique SIMONART
wrote:
> Hi e
Hi everybody,
Gambas 2.8, OpenSuse 11.0, Kde 3.5, with Qt
If I initialize my property with the next 2 lines, it's OK ( N and
the X property are defined as Byte, i is an Integer)
READ #hFile, N
hMyClass[i].X = N
But if I want to write it shorter with the line below, it ends w
