🚀 go-pugleaf

    I'm not sure exactly what your saying here.  Most of my visual classes are
PDSFrame which directly inherits from JPanel. I also have a Proxy object for
this. Then, I put widgets directly onto this PDSPanel.

    Are you saying I should first put down a second JPanel on the parent panel?

    Thanks.

Greg Hamer wrote:

> In order to be all java, the designer had to  stop using the native trick of
> blasting a Frames windows style bits so that it could be embedded into the
> design surface. As a result, the desinger can no longer directly design
> objects that extend from Frame/JFrame. For JFrame extended objects, this
> should be transparent as the ContentPane is stolen from the JFrame and added
> to the design surface. For Frames, there would need to be an Container that
> is the only direct child of the frame and this would be the object that the
> designer would design. Just select it in the component tree and choose
> activate designer. Then the desinger should look just like previous JBuilder
> versions except no title bar since the Frame is not there. Is this the sort
> of thing you are seeing or is your problem something else? Another major
> change is faking out heavyweight components into using lightweight peers so
> that the object being designed does not include anything heavyweight that
> could paint outside of the designer's borders.
>
> Timothy Reaves wrote:
>
> >     I just downloaded the version released yesterday, and moved my
> > existing JBuilder 3.0 project over from Windows NT.  When I go onto
> > design mode on about any window with more than five or six widgets, it
> > just doesn't display properly.  I'll usually end up with a single
> > component filling the JPanel.
> >
> >     If I select one of the other widgets from the left hand browser,
> > nothing happens - I assume because it isn't being displayed properly.
> >
> >     Any clue as to how to correct this?  Otherwise, JBuilder on linux is
> > failing.