| Summary: | [ScrolledComposite] The content of ScrolledComposite partially disappears when scrolled programatically | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Ivan Furnadjiev <ivan> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P1 | CC: | tbuschto |
| Version: | 1.5 | ||
| Target Milestone: | 1.5 M2 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Ivan Furnadjiev
Fixed by moving the check for the parent beeing ScrolledComposite to the client, property-handler for "bounds" in AdapterUtil.js. Its not quite as simple as on the server, since
a) The parent is set by the scrolledComposite ("setContent") after everything else bas been renderd, so that you cant check for the actual parent until that happend, and
b) ScrolledComposite is actually not the parent on the client, the ScrolledComposites "clientArea" is, wich is a normal CanvasLayout.
Solved by setting the scrolledComposite as userData in AdapterUtil#setParent. (Which was ported from WidgetUtil#setParent, where the case was originally ignored). Widgets not yet using the protocol are still using the old method where the switch happens on the server and there is no userData set.
|