| VE's behaviour when a VE visual class is instantiated from within another VE visual class [message #607272] |
Sun, 01 May 2005 02:43 |
Eclipse User |
|
|
|
Originally posted by: devmike.netcabo.pt
Hi everyone. I will try to explain my question this as clearly as I can.
Suppose I used VE to create a visual class (a composite, not a shell),
let's call it A. I assigned A a layout, either a GridLayout or a
RowLayout. If I create two sub-composites inside of A using VE's tool
palette everything works ok.
Now suppose I used VE to create two other visual classes (composites B
and C). What I wish to do is fill composite A with two instances of my
classes B and C, instead of the "stock" composites from the tool
pallete. I tried replacing VE's created code
composite = new Composite(A, SWT.NONE);
composite1 = new Composite(A, SWT.NONE);
with my own
composite = new B(A, SWT.NONE);
composite1 = new C(A, SWT.NONE);
When I do this, things work well at runtime, but I get null pointer
exception errors in Composite A's JavaBeans view and A's Design View
doesn't show B and C's contents. Is VE supposed to permit this kind of
thing? Any help would be greatly apreciated.
Thanks,
Miguel Barrosa
|
|
|
Powered by
FUDForum. Page generated in 0.03102 seconds
] 
Search
Help
Register
Login
Home
