Thank you. Worked.
I do find this to be an odd use of memory resource. I noticed that I can
still go back and use EditField1(index) and access all properties 0 to 81. I
now have an array taking up memory and the Editfield1(index) in duplicate. Any
wise member of the board know the rational for the redundancy? Maybe it isn't?
thanks
Derek
FreeFL <[EMAIL PROTECTED]> wrote:
| 26/09/06 ~ 18:13 -0700 :
| D P,
| " Dynamic loading of arrayed controls in window on open "
> I suspect the dynamic loading of e is not kept in memory after
>finish and this makes me sad.
Do not dim your e array in the open event but as properties of the window :
Declaration : e(8,8) as editfield
In the open event, you initialize the fields :
dim x, y, xx, yy as integer
For y = 20 to 180 step 20
For x = 20 to 180 step 20
yy = (y/20)-1
xx = (x/20)-1
e(yy,xx) = new EditField1
e(yy,xx).Left = x
e(yy,xx).Top = y
e(yy,xx).text = str(e(yy,xx).index)
e(yy,xx).Visible = True
Next x
Next y
_______________________________________________
Unsubscribe or switch delivery mode:
Search the archives of this list here:
________________________________________________________________
A man's own manner and character is what most becomes him.
- Marcus Cicero.
www.drunkenpoets.com
www.soundtower.com
---------------------------------
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
