ScrolledComposite cause the visual editor to freez

[allawy]

Hi Eric;

long time since I posted anything here, I was so busy doing web applications ...

Anyway, I installed the latest SWT builder (8th Dec. version) on Eclipse 3.1 M3, I had to do a form that scroll cause it has so many fields, when I just create an ApplicationWindow, and add a ScrolledComposite to it, the Visual editor freez, even if I close eclipse or add it by code, it just freez with ScrolledComposite, I tested that on my both Intel and AMD machines with windows XP.

I would appreciate if this is fixed, and I would appreciate if I can morph the main composite to scrolled composite just like I can morph it to a group.

Thanks allot!

[Eric Clayberg]

Anyway, I installed the latest SWT builder (8th Dec. version) on Eclipse 3.1 M3, I had to do a form that scroll cause it has so many fields, when I just create an ApplicationWindow, and add a ScrolledComposite to it, the Visual editor freez, even if I close eclipse or add it by code, it just freez with ScrolledComposite, I tested that on my both Intel and AMD machines with windows XP.

Any exceptions in your Eclipse ".log" file?

Can you send us a test case?

Try this new build and let me know if it makes any difference.

[allawy]

Eric;

Thanks for the fast reply...

The bug is still there, the code that cause it

Code: Select all

protected Control createContents(Composite parent) {
        Composite container = new Composite(parent, SWT.NONE);
        container.setLayout(new GridLayout());
        //_
        scrolledComposite = new ScrolledComposite(container, SWT.BORDER | SWT.H_SCROLL | SWT.V_SCROLL);
        scrolledComposite.setLayout(new GridLayout());
       
        return container;
    }


there is a "Designer internal error: null" when I switch to the design view...

I'm using

XP
eclipse 3.1 M3
j2sdk1.4.2_06
Designer_v3.0.0_for_Eclipse3.1 (files show that there were build on 13th Dec)

I downloaded it from the same link you provided switching 3.0 to 3.1

[Eric Clayberg]

I'm using
XP
eclipse 3.1 M3

Yes. This appears to be a serious problem under Eclipse 3.1. Interestingly enough, it works fine under Eclipse 3.0. We are investigating.