By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,306 Members | 1,657 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,306 IT Pros & Developers. It's quick & easy.

.Net 2.0 - Webbrowser control flickering on resize....

P: n/a
Has anyone seen a fix for the flickering effect you get when resizing a
Webbrowser control?

It's really irritating and doesn't make for a professional-looking
application.
Dec 10 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Evidentially the flickering has to do with the Microsoft tab control that I
used to host the Microsoft webbrowser control. If I use a 3rd party tab
control (like DotNetBar) the flicker is almost non-existent.

But......if you know how to remedy this Microsoft tab control flicker
problem, please let me know.

"Jim Hubbard" <Ji*@notmyaddress.com> wrote in message
news:YE***************@bignews7.bellsouth.net...
Has anyone seen a fix for the flickering effect you get when resizing a
Webbrowser control?

It's really irritating and doesn't make for a professional-looking
application.

Dec 10 '05 #2

P: n/a
I just tried putting the WebBrowser control on a Panel on top of the Tab control and that was really bad.
It seems that the WebBrower control does best(least amount of flickering) on a form itself. Too bad, I can
see where having a Tabbed browser would be nice ( FireFox).
james

"Jim Hubbard" <Ji*@notmyaddress.com> wrote in message news:qa***************@bignews7.bellsouth.net...
Evidentially the flickering has to do with the Microsoft tab control that I used to host the Microsoft webbrowser control. If
I use a 3rd party tab control (like DotNetBar) the flicker is almost non-existent.

But......if you know how to remedy this Microsoft tab control flicker problem, please let me know.

"Jim Hubbard" <Ji*@notmyaddress.com> wrote in message news:YE***************@bignews7.bellsouth.net...
Has anyone seen a fix for the flickering effect you get when resizing a Webbrowser control?

It's really irritating and doesn't make for a professional-looking application.


Dec 11 '05 #3

P: n/a
In general, setting these styles on a .Net Control will eliminate flicker:

ControlStyles.DoubleBuffer
ControlStyles.AllPaintingInWmPaint

--
Greg McPherran
www.McPherran.com
"Jim Hubbard" wrote:
Has anyone seen a fix for the flickering effect you get when resizing a
Webbrowser control?

It's really irritating and doesn't make for a professional-looking
application.

Dec 11 '05 #4

P: n/a
There is a DoubleBufferd property that is evidentially overridable
(according to
http://msdn2.microsoft.com/en-us/lib...buffered.aspx).

As I am just learning .Net (starting with .Net 2.0) I'll have to figure out
how to do this and if it will give the desired effect.

After all, if I override a protected property, aren't I just replacing it's
internal code with my own? And, if that is the case, I won't be changing
any internal settings of the Webbrowser class and won't have any effect on
its double buffering.

Does that make any sense?
"Greg" <gm@mcpherran.com> wrote in message
news:C8**********************************@microsof t.com...
In general, setting these styles on a .Net Control will eliminate flicker:

ControlStyles.DoubleBuffer
ControlStyles.AllPaintingInWmPaint

--
Greg McPherran
www.McPherran.com
"Jim Hubbard" wrote:
Has anyone seen a fix for the flickering effect you get when resizing a
Webbrowser control?

It's really irritating and doesn't make for a professional-looking
application.

Dec 11 '05 #5

P: n/a
"Jim Hubbard" wrote:
There is a DoubleBufferd property that is evidentially overridable
(according to
http://msdn2.microsoft.com/en-us/lib...buffered.aspx).

As I am just learning .Net (starting with .Net 2.0) I'll have to figure out
how to do this and if it will give the desired effect.

After all, if I override a protected property, aren't I just replacing it's
internal code with my own?

No. Whenever you create a control it is based on (derived from) the .Net
control. The properties such as DoubleBuffer are there to be set in any way
you like. You're not "overriding" the property you are just setting its value
to what you want it to be.

You are confusing overriding with setting a value. Yes you are "overriding"
the value in a sense but in C#/C++ the word "override" means to replace the
implementation of a function/method/property.

It's fine to set the value of the property - that's what it's there for.
Jan 7 '06 #6

This discussion thread is closed

Replies have been disabled for this discussion.