debugging UI display, or What To Do When Your Controls Are Invisible [message #439328] |
Sat, 10 July 2004 03:10 |
Tom Roche Messages: 160 Registered: July 2009 |
Senior Member |
|
|
Can someone provide, or point me toward, suggestions for debugging
when one's controls are just not visible? What I mean:
I recently inherited a wizard page, written by another developer, that
is contributed to a wizard, written by yet another developer, which
uses a framework developed by yet another developer, none of whom is
presently available. The code for these pages hasn't changed much, if
at all, since the previous release (which was 2.x based, though I
suspect that's incidental); in that release the wizard (and all the
contributed pages) were functional.
But now, when the user hits Next, the page I now maintain displays no
controls: there's a big blank space in the page. I have stepped
through its createControl(Composite), and the *code* looks OK--in
particular everything is getting setVisible(true) and it's calling
setControl(Composite) on the nested Composite. Yet none of the created
UI is actually *visible* :-(
This smells familiar. I can remember times when I've been writing UIs
and they just weren't showing up--layout problems, nesting problems--
but it's been a year since I've actually *written* any UIs, and I've
forgotten how to debug this kind of problem. Some things I've tried
are:
* preventing previous pages from displaying, so that my page is page 2
instead of page 5
* making the controls layout in the parent passed to createControl,
instead of the nested Composite which is created by createControl
* setLayout(null) on the nested Composite
* comment out everything after the first control
but no love. So I'd be grateful for suggestions regarding Things To
Do, and a pointer to a tutorial on What To Do When Your Controls Are
Invisible would be even better. If possible please post to me as well
as the newsgroup, and TIA.
|
|
|
Powered by
FUDForum. Page generated in 0.01807 seconds