Bug 357917 - Tree#setTopItem doesn't work with SWT.NO_SCROLL
Summary: Tree#setTopItem doesn't work with SWT.NO_SCROLL
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.2   Edit
Hardware: PC Windows 7
: P3 normal with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: ui
Depends on:
Blocks:
 
Reported: 2011-09-16 05:51 EDT by Joachim Butz CLA
Modified: 2020-05-04 19:33 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joachim Butz CLA 2011-09-16 05:51:37 EDT
Build Identifier: 20110615-0604

Table#setTopIndex can be used even when the table is created with SWT.NO_SCROLL. However, Tree#setTopItem silently does nothing as long as there's no scrollbar visible.

Less important information (background):
I created a table and a tree table with frozen columns (just like here http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet234.java?view=co ), however, I can't remove the ugly "middle" scrollbar because of the bug mentioned above.

Reproducible: Always

Steps to Reproduce:
1. Create a SWT Tree with the SWT.NO_SCROLL flag set
2. Put more items in it than can be displayed
3. Call Tree#setTopItem with any item (except the top most) -> nothing happens
4. Try again without SWT.NO_SCROLL (see step 1) -> the tree content moves
Comment 1 Lars Vogel CLA 2019-11-27 07:39:52 EST
This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.
Comment 2 Anthony DELHELLE CLA 2020-05-04 19:33:37 EDT
Bug still present...