Description Stefan Xenos 2016-07-20 13:49:34 EDT

There were several suggested features that didn't make it into the initial version of the SWT layout spy, and after testing I've discovered some follow-up items that should be addressed.

I'm recording them here so that I can follow up on them.

- Suppress warning about controls outside parent bounds for the immediate children of scrollable controls.
- Warn about scrollable controls embedded within other controls that are scrollable in the same dimension.
- Warn about missing width hint on wrapping controls
- Warn about wrapping controls without horizontal fill alignment
- Warn about controls with missing width hints + fill alignment which contain user-editable content (text boxes, etc).
- Controls with the incorrect layout data type.
- Warn about missing fill alignment on interior layout nodes.

Also, we should add a diagnostics button which performs a set of tests on the selected widget:

- Controls that return a different value from computeSize(true) than computeSize(false), indicating a stale cache.
- Controls which reposition any child more than once per layout pass.

Finally, we should write a step-by-step guide for using the layout spy to correct layout problems. 

The process is basically:

1. Use Select Control to click on the control with a problem, or something near it.
2. Navigate the widget hierarchy until you've found a layout whose bounds is correct (the red rectangle) with a child that has incorrect bounds (the yellow rectangle).
3. Look for any warning messages in either the layout pane or the child pane. They may locate the bug.
4. Look at the results of computeSize. If the result of computeSize is correct, the problem is in the parent layout or its attributes. Otherwise, the problem is in the child widget.