Bug 79072 - JavaBeans launcher doesn't pick up the preference L&F
Summary: JavaBeans launcher doesn't pick up the preference L&F
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: VE (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Joe Winchester CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-19 09:44 EST by Joe Winchester CLA
Modified: 2011-06-13 11:37 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Winchester CLA 2004-11-19 09:44:47 EST
JVESMOKEO1 - open TestSwingToDoList.java
The workbench prefs for the look and feel are that "Windows" is the default
the VE editor is fine
Run AS JavaBean
the GUI doesn't use Windows - it uses metal
go into the configuration and "Windows" is selected and shown as the one being 
used, however Run still shows it in Metal.
Comment 1 Peter Walker CLA 2004-11-29 16:13:50 EST
TestSwingToDoList.java only extends Object... not AWT or Swing. So the following
lines of code in JFCLauncher.java don't have any affect:
	UIManager.setLookAndFeel(lookAndFeelArg);
	SwingUtilities.updateComponentTreeUI((Component) javaBean);
Also this code is called after the bean has been instantiated so the
setLookAndFeel doesn't apply. Only the updateComponentTreeUI works if the bean
is a Component. But in this case it's an Object.

So if you explicity set the L&F in the configuration page, it doesn't have any
affect on the running application for classes that don't extend Component or
JComponent unless the L&F is set in the actual code by the user.

Please reassess whether this needs to be fixed for 1.0.2 since it's a not a very
common scenario to use Swing or AWT in this manner.
Comment 2 Peter Walker CLA 2004-11-29 17:22:46 EST
I'm moving to be fixed in a future release since this is not a common problem
and the L&F is a minor problem in itself.