Hello Christian and Marcos,
Christian López Espínola wrote:
Hi again,
I tested it again with the Sequence2 module, and it still fails.
Have you tested this with any module? If yes, which module?
This error only occurs (and ocurred) when a external module that uses
the GUI loads (in Seq module and other module where I worked in the
past I used
Yes, I have the same thing in the C++ module and the SettingsCpp. It
calls the GUI.getInstance()
which triggers all GUI to be loaded.
In my profiles spike I'm also being responsible for creating the
ProjectManager via ProjectManager.getManager()
and ProfileManager via its ProfileManagerImpl.getInstance().
Brace yourself, I'm preparing a post about *singletonitis* and its
shortcomings in an Argonaut's life! :-D
I think that the problem is still there, and I'll continue
investigating about some registering system like Linus pointed before
in this thread. For now, the patch I did works with loading, but not
reloading, modules.
Cheers.
Christian López Espínola
The idea of registering might work... Since the problem is access to
GUI.getInstance() to register parts of GUI from
modules, maybe we might add a GUI.register(GUIComponent) and
GUI.unregister/remove(GUIComponent),
similar to what Marcos created for ProfileManager for registering and
removing profiles.
Then, it is up to the GUI to call GUIComponent's show(Container) method
that actually triggers the internal construction
of the module's GUI parts.
Just my "not so much thought out" idea for this problem.
Luis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
