Propagating form toolkit to the children?

[a.shneyderman]

I was trying to create a view part. I got to the point where it became too complicated, so I started to break the view into panels and find myself unable to create composites that accept toolkits as arguments to the constructor of the form composite.

I can add the composite fine (thru Choose Bean plaette item) if I let the designer create a default composite and a new toolkit instance inside it, but if I do manual change of code to add extra parameter to the constructor of the child (toolkit), I get some weired message saying something is null in the designer and the child panel is not displayed, while if I run the app everything works just fine.

Any clue as to what might I do to circumvent theese problems. I really would hate to keep creating toolkits all over.

Thanks,
Alex.

[Eric Clayberg]

I was trying to create a view part. I got to the point where it became too complicated, so I started to break the view into panels and find myself unable to create composites that accept toolkits as arguments to the constructor of the form composite. I can add the composite fine (thru Choose Bean plaette item) if I let the designer create a default composite and a new toolkit instance inside it, but if I do manual change of code to add extra parameter to the constructor of the child (toolkit), I get some weired message saying something is null in the designer and the child panel is not displayed, while if I run the app everything works just fine. Any clue as to what might I do to circumvent theese problems. I really would hate to keep creating toolkits all over.

Designer currently does not support sharing form toolkits in this way. Currently, each panel / window must have its own toolkit.

We are investigating adding support for shared toolkits.