Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368084 - Omitting the scroll style flags for the ScrolledComposite breaks clients
Summary: Omitting the scroll style flags for the ScrolledComposite breaks clients
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.5   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: 1.5 M5   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-07 10:06 EST by Moritz Post CLA
Modified: 2012-01-07 11:09 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Post CLA 2012-01-07 10:06:14 EST 
The rap protocol has been changed in request to 

https://bugs.eclipse.org/bugs/show_bug.cgi?id=367495

This breaks clients that need to know on creation time of a ScrolledComposite what scroll directions are desirable.

Only relying on "scrollBarsVisible" is not sufficient because the property is not send when the ScrolledComposite is created. At that point there is nothing in the scroll area so the default value of false, false (which is omitted) does not provide the required information.

I would suggest to send the STYLE flags given in the ScrolledComposite constructor as has been the case previously.
Comment 1 Ivan Furnadjiev CLA 2012-01-07 11:09:00 EST 
ScrolledComposite H_SCROLL and V_SCROLL style flags are rendered again.