|
|
You're in the
visual studio .net debugging
group:Open Form Flickering
visual studio .net debugging:
I have three forms, a MDI Parent and 2 MID Child forms.
When i initially load my MDI Parent with the initial MDI Child, everything looks fine. But, when I click on a button in my first MDI Child that opens another MID Child, the new form flickers and jumps. It seems my MDI Child is opening in Normal Mode possibly and then being MAXIMIZED, which is what I specified for the form to do. Is there a way to open the form in a non-visible manner and then make it visible after eveyrthing has been rendered. It just looks a bit tacky for the form to jump around and flicker the way it does.
Hi Greg,
Yes, I can reproduce this behavior. Further reseach shows that this flicker is caused by twice paint behavior of MDI forms in VS2005. The bug below reported this issue: "MDI client forms with FormWindowState.Maximized paint twice upon calling Form.Show()" https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Feedba ckID=96015 I have tried many ways to work around it, but all failed. For example, I added a timer in the application and delayed the showing of the form after several seconds, but the flicker still exists. Currently, we have no good solution to workaround this problem yet. I would recommend you to submit a bug feedback in the link below. This feedback will be routed to the Winform dev team for consideration: https://connect.microsoft.com/VisualStudio/ Thanks. Best regards, Jeffrey Tan Microsoft Online Community Support ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
OK, I gave your code a try and unfortunately it doesn't give me the desired
result. One thing I did notice though is that even though I set the Maximize and Minimize buttons to false, they still appear, although you can't use them. I also noticed that the button between them allows the user to size the window, which is something I don't want. 1. How can i HIDE the Max, Min and other buttons. I used the frm.FormBorderStyle = Windows.Forms.FormBorderStyle.None statement and I still see are reserved for the child form caption within the parent form. How can I hide this entire caption for the child form? [quoted text, click to view] > Hi Greg,
> > Yes, I can reproduce this behavior. > > Further reseach shows that this flicker is caused by twice paint behavior > of MDI forms in VS2005. The bug below reported this issue: > "MDI client forms with FormWindowState.Maximized paint twice upon calling > Form.Show()" > https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Feedba > ckID=96015 > > I have tried many ways to work around it, but all failed. For example, I > added a timer in the application and delayed the showing of the form after > several seconds, but the flicker still exists. Currently, we have no good > solution to workaround this problem yet. > > I would recommend you to submit a bug feedback in the link below. This > feedback will be routed to the Winform dev team for consideration: > https://connect.microsoft.com/VisualStudio/ > > Thanks. > > Best regards, > Jeffrey Tan > Microsoft Online Community Support > ================================================== > Get notification to my posts through email? Please refer to > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > ications. > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > where an initial response from the community or a Microsoft Support > Engineer within 1 business day is acceptable. Please note that each follow > up response may take approximately 2 business days as the support > professional working with you may need further investigation to reach the > most efficient resolution. The offering is not appropriate for situations > that require urgent, real-time or phone-based interactions or complex > project analysis and dump analysis issues. Issues of this nature are best > handled working with a dedicated Microsoft Support Engineer by contacting > Microsoft Customer Support Services (CSS) at > http://msdn.microsoft.com/subscriptions/support/default.aspx. > ================================================== > This posting is provided "AS IS" with no warranties, and confers no rights. > > >
One more questioin related to the code snippet you sent me.
I usually open my forms as such. Form1.MDIParent = me.MDIParent Form1.Show Where you defined an object named frm. dim frm as NEW Form1 frm.MDIParent = Me.MDIParent frm.show Now, I find that both ways work. Is there any advantage do doing it either way? [quoted text, click to view] ""Jeffrey Tan[MSFT]"" wrote:
> Hi Greg, > > Yes, I can reproduce this behavior. > > Further reseach shows that this flicker is caused by twice paint behavior > of MDI forms in VS2005. The bug below reported this issue: > "MDI client forms with FormWindowState.Maximized paint twice upon calling > Form.Show()" > https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Feedba > ckID=96015 > > I have tried many ways to work around it, but all failed. For example, I > added a timer in the application and delayed the showing of the form after > several seconds, but the flicker still exists. Currently, we have no good > solution to workaround this problem yet. > > I would recommend you to submit a bug feedback in the link below. This > feedback will be routed to the Winform dev team for consideration: > https://connect.microsoft.com/VisualStudio/ > > Thanks. > > Best regards, > Jeffrey Tan > Microsoft Online Community Support > ================================================== > Get notification to my posts through email? Please refer to > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > ications. > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > where an initial response from the community or a Microsoft Support > Engineer within 1 business day is acceptable. Please note that each follow > up response may take approximately 2 business days as the support > professional working with you may need further investigation to reach the > most efficient resolution. The offering is not appropriate for situations > that require urgent, real-time or phone-based interactions or complex > project analysis and dump analysis issues. Issues of this nature are best > handled working with a dedicated Microsoft Support Engineer by contacting > Microsoft Customer Support Services (CSS) at > http://msdn.microsoft.com/subscriptions/support/default.aspx. > ================================================== > This posting is provided "AS IS" with no warranties, and confers no rights. > > >
Hi Greg,
Have you reviewed my reply to you? Does the sample make sense to you? If you still need any help, please feel free to feedback, thanks. Best regards, Jeffrey Tan Microsoft Online Community Support ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |