CODEWITHSUNDEEP
c#winformsonload-event
bsh152s
bsh152s

Reputation: 3208

Is there a Form event that gets called right before anything is drawn to the screen?

I've tried overriding the OnLoad event, but the form is getting drawn before this method finishes. I am calling the base.OnLoad method. But, the form is partially getting drawn (artifacts are seen) during the event. I notice this because I'm hitting the database and it is taking some time. In the event, I'm getting some data and binding it to the form's controls. Please don't tell me to use a separate thread. For simplicity, I would rather just show a busy cursor while the data is being loaded.

UPDATE:

Ok, I think you guys/gals have convinced me. I'll use a separate thread. I wasn't aware of the BackgroundWorker and it was very easy to implement. Now my form is loading quickly. And then, all of a sudden my combo boxes are populated. But, I'd like prevent the user from clicking on the combos before they're populated. What is the best way/standard way of doing this using Winforms? Is there a way to turn off input events in the form until the background worker is finished?

Upvotes: 2

Views: 1527

Answers (6)

James King
James King

Reputation: 6343

The ComboBox has a BeginUpdate() and EndUpdate() that can be called when adding large amounts of data or slow data to the control. SuspendLayout() and 'ResumeLayout()` on the form may also help with your redraw issues.

You can also disable the control, if all you want is to prevent the user from clicking it. If you disable the form itself, all contained controls will also be disabled.

If you're using background threads, you'll have to make sure you call these from the main UI thread before starting the thread, and again from the main UI thread when the background worker is complete.

Upvotes: 0

Brad Bruce
Brad Bruce

Reputation: 7807

The Shown event is good for this. Your form will be completely displayed, then the Shown event is fired. This will give the user a clean screen without partially drawn fields while you load your data.

In your Shown event handler, turn on the hourglass, do your work and then turn off the hourglass.

Upvotes: 0

Tomas Petricek
Tomas Petricek

Reputation: 243041

You should be able to solve the problem by placing your loading in the constructor code before the call to IntializeComponent(). At this point, the controls on the form have not yet been created (because this is what InitializeComponent does).

However, the form is also not yet visible in this phase. If you want to show a blank form, then I think a possible solution (I haven't tried that, but I think it should work) would be to call this.Show() (to display the form) and Application.DoEvents() to let WinForms process events and display the form.

Upvotes: 2

Adam Lear
Adam Lear

Reputation: 38758

You could try doing your expensive operations in the form's constructor, so that when it's time to show the form, it already has the data it needs to render. Also look into SuspendLayout/ResumeLayout methods.

But none of these solutions will be as graceful as using a different thread to perform expensive operations.

Upvotes: 1

D'Arcy Rittich
D'Arcy Rittich

Reputation: 171351

I am not sure if this will help or not, but the Move event is called before Load.

Upvotes: 0

SLaks
SLaks

Reputation: 887195

I would recommend that you cover the form with a Loading label before you start loading.

Upvotes: 2

Related Questions