Well, you might add some code that shows the problematic behaviour.

Lukas Geyer wrote:

Well, you might add some code that shows the problematic behaviour.

And what does proper resp. improper painting mean for you? Can you provide a screenshot showing how it should look like and how it actually looks like?

Why do you use an eventfilter for painting? That seems wrong.

Lukas Geyer wrote:

And what does proper resp. improper painting mean for you? Can you provide a screenshot showing how it should look like and how it actually looks like?

ya for image see the link below
http://www.imgplace.com/viewimg221/4369/95paint.png
The white color around the qlineedit widget corresponding to emil-id and password is the problem.

Andre wrote:

Why do you use an eventfilter for painting? That seems wrong.

Actually i am making a general class inheriting from qobject. Inside that i have child window which i am painting. Can you please say me what is wrong in doing that?

Much. Widgets are supposed to paint themselves. You return true from your filter, which means that the widget cannot take responsibility for painting its contents or its borders or its children.

Andre wrote:

Much. Widgets are supposed to paint themselves. You return true from your filter, which means that the widget cannot take responsibility for painting its contents or its borders or its children.

so how can i solve this problem?

Just use the system as it was designed to be used: by letting each widget paint itself.

Andre wrote:

Just use the system as it was designed to be used: by letting each widget paint itself.

Andre wrote:

Just use the system as it was designed to be used: by letting each widget paint itself.

I have tried as you told but i am getting the same problem but the problem is coming in mac only not in windows.But one thing i noticed that when we press tab key the paint event is called infinite number of times.

Sorry, my crystal ball is broken, so I cannot see your code without you posting it.

Andre wrote:

Sorry, my crystal ball is broken, so I cannot see your code without you posting it.

How about you start out with a call to QWidget::paintEvent(event); between your lines 2 and 3? Replace the QWidget with whatever is the base class of your widget. That way, the base class also gets a chance to do painting.

Andre wrote:

How about you start out with a call to QWidget::paintEvent(event); between your lines 2 and 3? Replace the QWidget with whatever is the base class of your widget. That way, the base class also gets a chance to do painting.

I have tried this also but same problem persists. Do you have mac system? If you have i will post you the sample code so that you can check.