Bug 395849

Summary:	[painting] Paint events and the GC
Product:	[Eclipse Project] Platform	Reporter:	Willem Duminy <willem.duminy>
Component:	SWT	Assignee:	Platform-SWT-Inbox <platform-swt-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3
Version:	4.3
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug
Bug Depends on:
Bug Blocks:	160904

Description Willem Duminy

2012-12-05 13:34:03 EST

I have a question regarding SWT's decision around the PaintListener of a Contol, i.e. Control::addPaintListener(PaintListener listener).

Is the a design decision made in SWT to ensure that the GC is restored after a  PaintListener is called.  In other words if I have two listeners on the same control and I modify the GC on the first listener does the second listener get the modified GC, or does it get a GC in exactly the same state that the original listener gets it?

There is a bug raised on draw2d that started a discussion that led to this question.  Have a look at https://bugs.eclipse.org/bugs/show_bug.cgi?id=160904 if you are interested in that discussion.

Comment 1 Willem Duminy

2012-12-05 13:42:31 EST

Maybe I can extend the question to also obtain an answer for the case where there are more controls.  Is the GC shared between controls?

Comment 2 Eclipse Genie

2018-12-16 09:47:24 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 3 Lars Vogel

2019-09-02 14:56:55 EDT

This bug has been marked as stalebug a while ago without any further interaction.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.