Re: [ve-dev] Registry contribution occurs too late?

[Rich Kulp <richkulp@xxxxxxxxxx>]

Hi,
 
Are you talking about some type of dynamic
setting that will be different each time? If so then you current can't.
The contribution does occur before the editor gets the registry, but the
thing is we keep a spare registry laying around to speed up opening the
editor the second time, or after a classpath change. So the contribution
occurs when the spare registry opens up, and then at some later time the
editor uses that registry.

Typically the contributions are not
time-dependent or editor dependent. They are usually class path dependent.
For example when JFace is in the classpath the contribution will initialize
some JFace classes for us. Since at the time of creation of the registry
it is not known what editor will use it, there is no editor specific contribution.

It is a known problem that look and
feel doesn't change until we use up the spare registry and create a new
one.

Rich

Darren Hurt <darren.hurt@xxxxxxxxxx>
Sent by: ve-dev-bounces@xxxxxxxxxxx

05/31/2006 09:03 AM

Please respond to
Discussions people developing code for the Visual Editor project <ve-dev@xxxxxxxxxxx>

To	"'Discussions people developing code for the Visual Editor project'" <ve-dev@xxxxxxxxxxx>
cc
Subject	[ve-dev] Registry contribution occurs too late?

I have some eclipse preferences
that I pass to the target VM via the registry contribution mechanism.
However, in order for these changes
to take effect I have to open and close an editor first, before opening

up the editor that I actually
want to make changes in.
 
It seems that the registry contribution
occurs too late.
By the way, this is also true
when you change the look and feel visual editor configurations.
 
Is this something you are aware
of, and is there any way to make the registry contribution occur earlier?
I am working on top of VE 1.1.0.1.
 
Thanks,
 
    Darren Hurt 
 _______________________________________________
ve-dev mailing list
ve-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ve-dev