Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Rich Client Platform (RCP) » Wizard dialog resize weirdiness
Wizard dialog resize weirdiness [message #498975] Thu, 19 November 2009 12:01 Go to next message
Marco Maccaferri is currently offline Marco MaccaferriFriend
Messages: 132
Registered: July 2009
Senior Member
Hi.

I have a weird issue with a wizard that is using WizardSelectionPage as
the first page: when the user selects one of the available wizards,
click next button (the new wizard page is displayed correctly) then
resizes the dialog, the page is switched back to the first
WizardSelectionPage but the wizard still thinks that the page was not
switched (i.e. next button doesn't work because the new wizard isn't
completed).

It seems that the dialog doesn't know what is the topmost composite when
reisizing. I don't think it is an internal issue but I can't find any
reason of this behaviour.

Anyone has an idea or some suggestions on how to debug this issue ?

Regards,
Marco.
Re: Wizard dialog resize weirdiness [message #498984 is a reply to message #498975] Thu, 19 November 2009 12:40 Go to previous messageGo to next message
Wim Jongman is currently offline Wim JongmanFriend
Messages: 418
Registered: July 2009
Senior Member
Hi Marco,

This can be caused by not setting the control in your wizardpage:

public void createControl(Composite parent) {
Composite composite = new Composite(parent, SWT.NONE);
// Draw on composite
// call setControl
setControl(composite);

I hope this solved it,

Best regards,

Wim Jongman
> Hi.
>
> I have a weird issue with a wizard that is using WizardSelectionPage as
> the first page: when the user selects one of the available wizards,
> click next button (the new wizard page is displayed correctly) then
> resizes the dialog, the page is switched back to the first
> WizardSelectionPage but the wizard still thinks that the page was not
> switched (i.e. next button doesn't work because the new wizard isn't
> completed).
>
> It seems that the dialog doesn't know what is the topmost composite when
> reisizing. I don't think it is an internal issue but I can't find any
> reason of this behaviour.
>
> Anyone has an idea or some suggestions on how to debug this issue ?
>
> Regards,
> Marco.
Re: Wizard dialog resize weirdiness [message #499024 is a reply to message #498984] Thu, 19 November 2009 15:03 Go to previous messageGo to next message
Marco Maccaferri is currently offline Marco MaccaferriFriend
Messages: 132
Registered: July 2009
Senior Member
On 19/11/2009 13:40 Wim Jongman ha scritto:

> public void createControl(Composite parent) {
> Composite composite = new Composite(parent, SWT.NONE);
> // Draw on composite
> // call setControl
> setControl(composite);

All pages sets the control correctly, if I'm not wrong the wizard throws
an exception if the control is not set.

In addition, this issue appears only when I'm using a
WizardSelectionPage and only on Windows platform. The same application
running on Linux works fine.

Regards,
Marco.
Re: Wizard dialog resize weirdiness [message #499163 is a reply to message #498975] Fri, 20 November 2009 08:29 Go to previous message
Marco Maccaferri is currently offline Marco MaccaferriFriend
Messages: 132
Registered: July 2009
Senior Member
On 19/11/2009 13:01 Marco Maccaferri ha scritto:

> I have a weird issue with a wizard that is using WizardSelectionPage as
> the first page: when the user selects one of the available wizards,
> click next button (the new wizard page is displayed correctly) then
> resizes the dialog, the page is switched back to the first
> WizardSelectionPage but the wizard still thinks that the page was not
> switched (i.e. next button doesn't work because the new wizard isn't
> completed).

I found the cause: the WizardSelectionPage was composed of a single
table so I used the table widget as the page control. Believe it or not
this caused the resize issues in Windows, I had to add a composite
container around the table and use that composite as the page control.

So today's lesson is: always use a composite to wrap controls, even if
you believe it is not necessary and is a waste of resources.

Regards,
Marco.
Previous Topic:Opening a plain file in filesystem in org.eclipse.ui.DefaultTextEdtior
Next Topic:Compute Dependencies for Feature
Goto Forum:
  


Current Time: Thu Nov 27 23:28:23 GMT 2014

Powered by FUDForum. Page generated in 0.03752 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software