[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ve-dev] Ambiguous ContainerTreeEditPart Helper
|
Hope you agree that initialization of the helper really should be
explicit. Not sure I can support LI given all the different ways
that methods in the helper may inferentially rely on the correct
container/editpart object -- and not just in my code, but also in the VE
standard subclasses as well.
Are there any events from the JavaBean view that could be filtered and
used as an "afterActivate" trigger?
In any case, what is the chance that
TreeVisualContainerEditpolicy.activate() can be fixed
in the near term to add an explicit
helper#setContainerPolicy(
containerPolicy) call immediately after
containerPolicy
.setContainer(getHost().getModel())? Or some other fix to
make helper initialization explicit?
At 06:56 AM 8/16/2006, you wrote:
Hi,
The only thing I can suggest is a lazy initialization. The
first time you need anything from the helper you can initialize at that
point. The model should be in the container policy by then.
Rich
_______________________________________________
ve-dev mailing list
ve-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ve-dev
