Bug 319391 - Running Zest on multiple displays can cause thread access exceptions
Summary: Running Zest on multiple displays can cause thread access exceptions
Status: NEW
Alias: None
Product: GEF
Classification: Tools
Component: GEF-Legacy Zest (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: gef-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-09 09:51 EDT by Matthew Wright CLA
Modified: 2010-07-09 09:51 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Wright CLA 2010-07-09 09:51:44 EDT 
Build Identifier: 1.1

When running Zest on a second monitor I got a thread access exception. Digging into the code revealed extensive use of Display.getDefault() rather than Display.getCurrent()

Reproducible: Always

Steps to Reproduce:
1.Fire up a zest application on a second monitor
2.Using a view that includes a graph viewer I get the exception firing as part of createPartControl
3.