Designer Quick te preview not same as actual built code?

[Bach]

Hi,
Using WindowPro I have screen with lables and textfields. All labels contain same size and the text fileds come in two sizes. The layout is Gridbaglayout.
When testing the screen using the "quick test" button of windowpro, everything look exactly as designed. But actual compiled codes show the labels/textfields on the left hand side of the screen being wider.
Would I need to set the preferred size? if so, how would I know what the preferred size should be since I designed the screen using Windowpro GUI.

How reliable is the quick test button?

[Eric Clayberg]

Using WindowPro I have screen with lables and textfields. All labels contain same size and the text fileds come in two sizes. The layout is Gridbaglayout. When testing the screen using the "quick test" button of windowpro, everything look exactly as designed. But actual compiled codes show the labels/textfields on the left hand side of the screen being wider. Would I need to set the preferred size? if so, how would I know what the preferred size should be since I designed the screen using Windowpro GUI. How reliable is the quick test button?

Have you modified the code in any way or added any runtime behavior to it?

The quick test button does not run your code; it shows the same layout that is shown in the design view (which is itself based on parsing your code).

Without seeing an actual example (source code plus scree screen shots of run mode and test mode), it would be hard to know exactly what might be causing the difference.

[Bach]

"The quick test button does not run your code; it shows the same layout that is shown in the design view (which is itself based on parsing your code). "

No I haven't added any runtime behavior I just draw the screen using the designer and then run it....

The only thing I did was to add constraint factor. I "only" added WeightX anf fill horizontally. Yes this can affect the display but only when you resize.
Anyway, I went back to remove the weightx and reset the fill to none...it actually gotten worst at run time....but the quick test always looks perfect
The best it looks is when I had the weightx in on all components with equal amount of 0.3
I wish I had a way to show an image of the screen.
Oh well, wish me luck

[Eric Clayberg]

I wish I had a way to show an image of the screen.

If you are using Windows or Linux, the Print Screen function should do the trick.

Without seeing a test case, I have no way of knowing what is going on or what to suggest.