Comment 1 Ivan Furnadjiev 2008-03-25 11:55:07 EDT

Created attachment 93410 [details]
Snippet175.java

Comment 2 Rüdiger Herrmann 2009-02-16 05:00:16 EST

To me this looks like a duplicate of bug 244942. Can you confirm this?

Comment 3 Ivan Furnadjiev 2009-02-16 07:18:50 EST

I don't think so. The problem is that using GridData.exclude = true initially, removes the button from the layout, but it is partly (part of the label, but not the button border) appears in the top left part of the shell title bar??!!

Comment 4 Ivan Furnadjiev 2009-02-19 04:05:42 EST

*** Bug 265416 has been marked as a duplicate of this bug. ***

Comment 5 Ivan Furnadjiev 2009-02-20 05:09:58 EST

The problem is that exclude just excludes the widget from layout, it doesn't hide it. In SWT initially the excluded control is hidden, but the Control#isVisible() and Control#getVisible() return true??!! As a workaround I suggested always to set the visibility of the excluded control as it is done in *handleEvent*.

Comment 6 Ivan Furnadjiev 2009-02-21 12:53:37 EST

The actual problem is the following. Initially when the control is in GridLayout with "exclude" set to true, the control bounds are (0,0,0,0) both in RAP and in SWT. In SWT the control with zero bounds is completely hidden, in RAP depends on the control JavaScript implementation some of the qooxdoo sub widgets (labels and etc.) are still visible or partly visible. That's way I propose the above workaround (when setting GridData.exclude to true always to set control visibility to false) and leave the bug as WONTFIX:
------------
GridData data = new GridData();
data.exclude = true;
bHidden.setLayoutData( data );
bHidden.setVisible( !data.exclude );
------------

Comment 7 Ivan Furnadjiev 2010-01-18 05:14:42 EST

Fixed with bug 299914.