Vb net screen updating secret to speed dating
I therefore believe this is another of those "can't be done" instances and the users will just have to live with the ugly form load.
On the plus side, though, containing the objects in a panel not only makes it much faster to hide the controls and also significantly reduced the amount of code involved, from 80 or so Visible=False statements to 1. If nothing else, the processing time is marginally faster. Having worked with many MSFT people directly, I can tell you customer input IS valued and one person CAN make a difference in how a product is released... NOT a Wiley/Wrox Employee Thanks for the suggestion, Hal.
Usually, this is not recommended as you may end up with an object in an undetermined state, but there are situations where it might be useful.
So, if you didn't have to include the statement at all, there is no way to not call it if you didn't want to. Visible = True From what I can see, this would result in 1 single paint action, that will take place when you show the Panel. Imar --------------------------------------- Imar Spaanjaars Everyone is unique, except for me. Visible = True From what I can see, this would result in 1 single paint action, that will take place when you show the Panel. Ron's response: Funny you should suggest this as I was just trying it before I received your post.
This even seems to be occuring when the form is first displayed, leaving large white spots on the form until the details for each object are filled in. So, is there some way to suppress the form refresh until all my interface changes have been made, so that the screen just refreshes once, instead of after each change?While typing this post, I was listening to: Providence by Godspeed you Black Emperor!(Track 3 from the album: F# A# Infinity) What's This? I omitted that I set the default property to FALSE so that the panel is invisible when the form is first loaded.Hiding the panel occurs almost instantaneously and in one step, whereas adding it repaints each control in turn (in opposite order, in fact, from bottom to top) in the same way as occurs when the form is first loaded.I tried playing with the VS generated interface code a couple of different ways and nothign seemed to work.