🚀 go-pugleaf

Fabian:

Can you give me a snippet of code?  Off the top of my head I'd say
that in the designer the insets for the Frame aren't being figured
properly and when the application gets into the "real world" there is
a slightly different result in the calcualtion.  However small, 12
pixels would be noticed.

Fabian Beutin wrote:
> 
> Rich Wilkman wrote:
> 
> > If you size something down so that either it's height or width is the
> > same as the preferred size you will get a -1 for that portion of the
> > constraint.  Why?  Because preferred size is the more proper java
> > mechanism.
> >
> > Bug?  Difference of opinion there.  It's working the way it was
> > designed to work.
> 
> ...and howcome the component has a different size when the program is
> executed than it has in the designer?
> This happens only when there's one of those -1's in the constraints.
> There shouldn't be anything wrong with what doLayout reprots since the
> component is a simple BorderLayout.
> Conclusion? A bug I'd say - in your XYLayout -!
> For (once again) there is abolutely *no* reason to go for default values
> (which don't always match as described above) when the user is giving
> absolute values by hand. To be absolutely clear on this: whenever
> somebody specifies something directly, with absolute values, a XY layout
> should just take those and not mess around with em...
> A layout (and a designer) which don't result in programs looking exactly
> the same as at design time certainly *are* buggy.
> 
> Regards,
>         Fabian.

-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rich Wilkman
Senior Quality Assurance Engineer
Borland JBuilder Team

If you see something that looks like an opinion up there,
it's mine and mine alone.

Mail sent to me from the newsgroups won't bounce but will
be ignored.  If I have time, I'll respond, but you  have
a better chance if you confine your posts to the newsgroups
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=