On Monday 19 June 2006 18:50, frame down under wrote:
> this explains a lot of trouble i had with forms not updating correctly.
> thanks for the clear explanation, ron and benoit.
Please do take note the misbehaviour in my project design.
I use a frame on a scrollview to represent something.
When I need those somethings I look in the scrollview.children
for the information related to something and take action on it.
This is missuse of the screen objects.
The real information should collected in my/your program in
arrays, collections or other way and NOT into the controls .Tag
as I (did) use. Changing this is in progress :)
In my program a button did delete the frame and after that
update the scrollview with the new information available.
And that information was the content of the not yet updated
If I had used the .Visible or .Enable I had not discover it.
The properties are working correct but the object is a real other
In VB this was allowed because it is multi tread and gambas is not.
I think you must assume, to be safe, the visible screen content
is updated as the interpreter finish all program loops and go
in idle state, waiting the user does something new.
You can see this visual if you use breakpoints and single step
through your program.
The window on the screen is not repainted inside.