Missing preference about ResourceManager

[sdatchley]

There used to be a preference "Add ResourceManager class to existing project as necessary"

With this documentation:
This preference determines whether the ResourceManager class is added to the project any time it is needed.

We currently have one plugin that has the current versions of both of the resource classes, and don't want the 2 classes generated each time
we do something with designer in our plugins. How can we turn off the auto generation like in previous versions?

Thanks,
Dean

[Eric Clayberg]

We currently have one plugin that has the current versions of both of the resource classes, and don't want the 2 classes generated each time
we do something with designer in our plugins.

That isn't the way it works now, so I'm not sure what such a preference would actually accomplish.

[sdatchley]

We currently have one plugin that has the current versions of both of the resource classes, and don't want the 2 classes generated each time
we do something with designer in our plugins.

That isn't the way it works now, so I'm not sure what such a preference would actually accomplish.

So in our RCP app I have a plugin A that has ResourceManager and SWTResourceManager, plus alot of common images..

And 3 dozen other plugins that use this plugin A (which exports the com.swtdesigner package)

Now whenever we use swtdesigner in any of the other plugins, the 2 files are being generated in those plugins. We still want the code generated in designer to use either ResourceManager or SWTResourceManager when we pick images, fonts etc, but we want don't want copies of the 2 files in all of our plugins. When you say it isn't the way it works now, are you saying it shouldn't generate the 2 files or we have to have a set of these files in each of our plugins all referencing plugin A again that has the images? Currently, I am deleting the files when they show up, but this is tedious.

What would be nice is to be able to specify a interface implementation in the preferences to allow us to use our own resource management classes that designer could work with.

Thanks,
Dean

[Konstantin.Scheglov]

So in our RCP app I have a plugin A that has ResourceManager and SWTResourceManager, plus alot of common images..

And 3 dozen other plugins that use this plugin A (which exports the com.swtdesigner package)

Now whenever we use swtdesigner in any of the other plugins, the 2 files are being generated in those plugins. We still want the code generated in designer to use either ResourceManager or SWTResourceManager when we pick images, fonts etc, but we want don't want copies of the 2 files in all of our plugins. When you say it isn't the way it works now, are you saying it shouldn't generate the 2 files or we have to have a set of these files in each of our plugins all referencing plugin A again that has the images? Currently, I am deleting the files when they show up, but this is tedious.

This should not happen - WindowBuilder should not generate ResourceManager if it is already in classpath.
See in attachment archive with two projects, note that project_useResourceManagers has no resource managers, it uses ones from project_withResourceManagers.
Code for Dialog_2 was generated using WindowBuilder, and no copies of resource managers were added.

[sdatchley]

Hi Konstantin,

1) I created a new workspace, imported the 2 projects.
2) Opened Dialog_2.java with designer
3) Added a button to the "container" composite in designer
4) changed font...
--> added button.setFont(SWTResourceManager.getFont("Garamond", 12, SWT.BOLD | SWT.ITALIC));
5) SWTResourceManager.java was added to "project_useResourceManagers"... but when I F3 (windows) SWTResourceManager in the editor
it takes me to the SWTResourceManager in the "project_withResourceManagers" project.
6) Tried restarting eclipse, F3 still takes me to the SWTResourceManager in the other project, although one exists locally.

If I delete the newly created SWTResourceManager, everything is fine and it uses the original one from your other project.

Briefly,
running sun jdk 6 release 16 (tried jdk 5 initially, same results), galileo sr1 (RCP distro)

I can send the full output configuration if you need it, don't want to post it here.

As for instantiations products, I'm running RCP Developer (and it's windowbuilder, showing SWT Designer 7.1.0.200909140923 for eclipse 3.5), CodePro A.P.(6.3.0.200908241812 for eclipse 3.5)

Thanks,
Dean

[Eric Clayberg]

SWT Designer 7.1.0.200909140923

Please give this a try using the latest SWT Designer v7.2 build.

Also note that is the resource manager files that you are using are out of date, the tool will automatically update them to keep them in sync.

[Konstantin.Scheglov]

If I delete the newly created SWTResourceManager, everything is fine and it uses the original one from your other project.

OK, I've reproduced and fixed this.
WindowBuilder checks that if resource manager exists, but not latest one, then it should be replaced with latest.
But there was not perfect implementation - we check manager in "has" project, but add in current project, i.e. in "use".
Fixed, now we will update existing copy.

As Eric already told, you should download latest build, which will include this fix.