Re: Odd behavior with WindowState

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

... I would suggest it's better to solve the
problem than apply a workaround to every form whether it needs it or not.

I disagree, see below for why.

Can you post some code that demonstrates this problem?

Ok, here's one. Make a form with no controls. In its load event, put

ControlBox = True ' forces a draw normal state
Threading.Thread.Sleep(1000) ' so you see it if your machine is very fast
WindowState = FormWindowState.Maximized ' later, a maximized draw

For what follows, I assume that you are able to reproduce the double draw
effect.

My earlier post stated that setting Visible to true will force a draw in the
load event. The above ControlBox assignment is a second case. I assert
that there are more double draw cases, and I don't know what they are, so
don't ask me to dig out any more. Knowing two leaves me uncertain about the
whole picture, and if I come up with a third, I will still be uncertain. The
burden is not on me to do this research, testing, and documentation, it is on
Microsoft. Nowhere in the documentation about Visible and ControlBox is the
idea of an immediate draw discussed. Also, please don't tell me that I
should set ControlBox in the designer. It will probably fix this problem,
but the documentation gives no reason to prefer the designer over code. I
see no merit in replacing my workaround (with no basis in the documentation)
with a 'do it in the designer' workaround (also with no basis in the
documentation).

As far as the load event goes, the double draw phenomenon is what the
workaround addresses. So, once more and with gusto, I stand by visible false
at the top and true at the bottom. It takes care of all of the double draw
behaviors, including those that I know about and those that I don't know
about. The workaround has never failed me, although it sounds like it is not
helping the OP solve his problem. FYI, I started using this workaround a
while ago, back in the vs2003 fw1.1 days. One could argue that it is time
revisit it - against that, this roof ain't broke, so why fix it?

.

Relevant Pages

  • Re: Odd behavior with WindowState
    ... The above ControlBox assignment is a second case. ... Nowhere in the documentation about Visible and ControlBox is ... idea of an immediate draw discussed. ... with a 'do it in the designer' workaround (also with no basis in the ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: glDrawPixels bug?
    ... OpenGL only draws the bottom 400 rows or so, ... The best way to draw 2D images is to make a texture ... The other workaround which is easier to implement ...
    (comp.graphics.api.opengl)
  • Re: Line Numbers and Tables
    ... The only workaround I've found is to use tabbed text with borders ... but you can draw them in with the line tool if you want. ... HTH |:>) ...
    (microsoft.public.mac.office.word)
  • Re: Screen Capture With Mouse , Mouse Position Capture
    ... > Draw it. ... but in witch way i can get the Mouse Position over the screen? ... but when the mouse is outside the component (outside the applet, ... Any Workaround? ...
    (comp.lang.java.programmer)
  • RE: MS Security update 891781 - Microsoft Security Bulletin MS05-0
    ... There is virtually no documentation on this from Microsoft, ... and moved it to it's calling page, ... I know it's not as pretty, but it's a workaround, ... var properties = new Object; ...
    (microsoft.public.windowsxp.security_admin)