Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 332480

Summary:	Move scrollbar api from ScrolledComposite to Scrollable
Product:	[RT] RAP	Reporter:	Austin Riddle <austin.riddle>
Component:	RWT	Assignee:	Austin Riddle <austin.riddle>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	ivan
Version:	1.4	Keywords:	api, consistency
Target Milestone:	M4
Hardware:	PC
OS:	All
Whiteboard:

Description Austin Riddle

2010-12-13 17:08:01 EST

Version: CVS HEAD 
Need to fulfill a note from Rudiger in ScrolledComposite about moving the scrollbar code to Scrollable to be in conformance with SWT.

Comment 1 Ivan Furnadjiev

2010-12-14 03:22:08 EST

At least, the following widgets will be affected - List, Tree, Table, ScrolledComposite. They have the same code for managing the scrollbars in all of them. Maybe we can consider this bug as duplicate of bug 264420.

Comment 2 Austin Riddle

2010-12-15 12:00:43 EST

(In reply to comment #1)
> At least, the following widgets will be affected - List, Tree, Table,
> ScrolledComposite. They have the same code for managing the scrollbars in all
> of them. Maybe we can consider this bug as duplicate of bug 264420.

I think that this bug is distinct from bug 264420. Although it may be an obscure case, we need it in our apps is because we use an org.eclipse.ui facade to bring in some binary compatible bundles into our apps and since the api does not match we get linkage related errors. Overall this bug just indicates a need for better RCP api conformance.

Comment 3 Austin Riddle

2010-12-16 14:10:56 EST

Added method stubs for scrollbar accessors from SWT to acheive greater binary compatibility.

Eventually the Scrollable type should create the scrollbars for its subtypes.
But for now the issue is resolved for us.