Re: Splash screen

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Tom Krueger [MSFT] (a-tkrueg_at_online.microsoft.com)
Date: 01/19/05 

Date: Wed, 19 Jan 2005 13:14:04 -0800

The DoubleBuffering does not work completely in Whidbey Beta 1. I beleive
the solution for now is setting SetStyle(ControlStyles.AllPaintingInWmPaint,
true). I believe in Beta 2, the DoubleBuffering property will do this.

Did you acutally get the flickering to stop by putting the code in
InitializeComponent? 

-- 
Tom Krueger
My Blog - http://weblogs.asp.net/tom_krueger
Smart Client DevCenter - http://msdn.microsoft.com/smartclient/
Mobile DevCenter - http://msdn.microsoft.com/mobility
This posting is provided "as is" with no warranties and confers no rights.
"Juan Ignacio Gelos" <msnews@juanignaciogelos.com> wrote in message 
news:OWdcmGj$EHA.960@TK2MSFTNGP10.phx.gbl...
>I turns out I *was* actually doing some work setting up a control (the
> larger one <g>) in a base form class after InitializeComponent(), and 
> doing
> SuspendLayout() ResumeLayout() on my own. It's been a couple of months I
> designed that base class and had forgotten about this little method...
>
> I was forced to do this because the control wouldn't work in the windows
> form designer. So now I found the workaround to make it work with the
> designer, moved the initialization code inside InitializeComponent... 
> added
> a couple Application.DoEvents() before doing some heavy work (calling
> webservices to load global data, etc), and finally the form  looks like it
> comes up as a whole the first time its displayed...
>
> In any case, regarding my initial question... it would be nice to have a 
> way
> for us to plug into InitializeComponent before it does all those
> .ResumeLayout() and .EndInit() 's, or some way of doing a double-buffer on
> the entire form (I did try Form.DoubleBuffered but didn't seem to have any
> apparent effect). Any pointers on that?
>
> Juan
>
> PS. the Remarks for DoubleBuffered state that (emphasis mine) "Buffered
> graphics can reduce or eliminate flicker that is caused by *progressive
> redrawing of parts* of a displayed surface. Buffered graphics require that
> the updated graphics data is first written to a buffer. The data in the
> graphics buffer is then quickly written to displayed surface memory. The
> relatively quick switch of the displayed graphics memory typically reduces
> the flicker that can otherwise occur."... however it didn't seem to do the
> trick for me at Form.... I'm xposting this to the whidbey ngs.
>
>
> "Juan Ignacio Gelos" <msnews@juanignaciogelos.com> wrote in message
> news:uY1vOtc$EHA.1404@TK2MSFTNGP11.phx.gbl...
>> Hi Tom,
>>
>>     I'm not doing the layout myself (I'm not setting any properties or
>> calling any methods), rather it's the standard way the controls behave
> when
>> shown the first time that bothers me. e.g. I see a panel resizing to fill
>> where they are docked to Fill, another panel that paints the background a
>> few seconds after it's shown, etc... looks like the form is being drawn
> part
>> by part. I realize this is just ~1.5 secs. but it really doesn't make the
>> application look solid.
>>     Maybe this is because I'm using the whidbey beta1 version of the
>> framework, but a way to 'hide' the form should be common to .net 1.1 I
>> think... or maybe its the other custom controls I'm using 
>> (divil.co.uk's),
>> but none of this should really matter if there's a way to hide the form
> from
>> the user while this layout work is being done for the first time...
>>     Apparently these controls (Panel, ToolStrip+RaftinContainer, etc.)
> only
>> resize and paint the background once they've been made visible, and I
> can't
>> make them do it with Form.PerformLayout() or Form.Refresh(), etc... it's
>> only the first time the form is made visible that they start resizing +
>> painting... After that, when I minimize the form and restore it any of
> this
>> things happen, as the controls have their sizes already, and neither does
>> this happen when I resize the form.
>>     What I'm looking for is a way to show the form for the first time
>> instantaneously, like it was a bitmap... and I'm starting to think for
> that
>> I'd need a way to double buffer the entire form... if that's even
> possible.
>>     BTW, this is the application's main form, so it'd be frm.Show();... 
>> or
>> maybe there is a reason I'd want to use ShowDialog regarding this?
>>
>> Thanks for your help,
>> Juan
>>
>> "Tom Krueger [MSFT]" <a-tkrueg@online.microsoft.com> wrote in message
>> news:ODyhqNc$EHA.2552@TK2MSFTNGP09.phx.gbl...
>> > Hello,
>> >
>> > Can you handle all the control layout work in the constructor?  If you
>> don't
>> > want to do that you could create a public method that can be called
> before
>> > the form is shown.
>> >
>> > Form frm = new Form();
>> > frm.Layout();
>> > frm.ShowDialog();
>> >
>> >
>> >
>> > -- 
>> > Tom Krueger
>> >
>> > My Blog - http://weblogs.asp.net/tom_krueger
>> > Smart Client DevCenter - http://msdn.microsoft.com/smartclient/
>> > Mobile DevCenter - http://msdn.microsoft.com/mobility
>> >
>> > This posting is provided "as is" with no warranties and confers no
> rights.
>> >
>> > "Juan Ignacio Gelos" <msnews@juanignaciogelos.com> wrote in message
>> > news:Oo28XmC$EHA.1392@tk2msftngp13.phx.gbl...
>> > > Hi,
>> > >
>> > >    I'm trying to 'hide' the main form of an application until all the
>> > > layout work is done and all the controls have their final sizes and
>> > > locations (once the form is displayed you can see the several
> toolbars,
>> > > panels and docking sections being resized, drawn for the first time,
>> etc,
>> > > and makes it looks really unprofessional). What I'm looking for is to
>> only
>> > > display the form when everything is ready and the form can be
> displayed
>> > > instantaneously, just like when a window is restored after being
>> > > minimized.
>> > >    I've tried the following in Main but yields the same result:
>> > > MainForm frm = new MainForm();
>> > > frm.CreateControl();
>> > > frm.PerformLayout();
>> > > Application.Run(frm);
>> > >
>> > >    I'm guessing I need to go deeper and set some window styles or 
>> > > play
>> > > with
>> > > double buffering, but maybe there's an easier way. Anyone has any
>> pointers
>> > > on this or (much better) any sample code?
>> > >
>> > > Thanks in advance,
>> > > Juan
>> > >
>> > >
>> >
>> >
>>
>>
>>
>
>
>
>
>
>

Relevant Pages

  • Re: Storage of html markup code in database
    ... UIs may include reports and database management tools, ... The details of your desired HTML-encoding may change over time. ... may also differ between display locations within your application. ... While it's unfortunate that the built-in controls are not ...
    (microsoft.public.dotnet.security)
  • RE: Display a record - several questions
    ... ObjectDataSource set up to get the correct record on a select. ... sub controls in the certain tepmlate and modify them. ... How do I display a RadioButtonList and CheckBox value where it is ...
    (microsoft.public.dotnet.framework.aspnet.webcontrols)
  • Re: Kneisner and Doering KWZ30-2
    ... The controls of the KWZ-30/2 are much more comfortable than the controls of ... colour display with a resolution of 320 x 240 pixels. ... passed though a low pass filter, a switchable high pass filter and an ... mixers are followed by two A/D-converters with a dynamic range of 120 dB. ...
    (rec.radio.shortwave)
  • Re: Is it a habit we prefer mechnical instruments?
    ... Converting the display to a form fit for human consumption ... graphics on standard PC using C++, and you can see the difference. ... simulator that is rendered by a digital display showing analog ... controls are rendered digitally. ...
    (rec.aviation.homebuilt)
  • Re: Create Dynamic Controls and Displaying Page by Page on the for
    ... My computer is client and other is server. ... I want to display all recevied values for parameters ... > I'm saying this because dynamically creating a few thousand controls might ... >> row data format will be same. ...
    (microsoft.public.vsnet.general)