Bug 40178 - Remove SetFrontProcess call in Display after switch to 1.4.1
Summary: Remove SetFrontProcess call in Display after switch to 1.4.1
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.0   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Silenio Quarti CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 40003
Blocks:
  Show dependency tree
 
Reported: 2003-07-16 04:46 EDT by Andre Weinand CLA
Modified: 2004-03-01 15:19 EST (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 Andre Weinand CLA 2003-07-16 04:46:57 EDT 
As soon as we are requiring Java 1.4.1 and the java_swt launcher,
I suggest to remove these lines from Display's static initializer and move it to java_swt.c:

		int [] psn = new int [2];
		if (OS.GetCurrentProcess (psn) == OS.noErr) {
			OS.SetFrontProcess (psn);
		}

I have to call GetCurrentProcess() in java_swt anyways and the earlier we call SetFrontProcess(..)
the better, because it becomes less likely that an SWT application inadvertently comes to front.
Comment 1 Andre Weinand CLA 2004-03-01 15:19:29 EST 
Since we are in the process of removing java_swt, we shouldn't remove this code from Display.
In fact we'll have to add more stuff to Display.
Closing.