102921 – Table scrollbar selection listener does not get Event.detail

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

Bug 102921 - Table scrollbar selection listener does not get Event.detail

Summary: Table scrollbar selection listener does not get Event.detail

Status:	RESOLVED DUPLICATE of bug 51995

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	SWT (show other bugs)
Version:	3.0.2
Hardware:	Other Linux-GTK

Importance:	P3 major (vote)
Target Milestone:	---
Assignee:	Platform-SWT-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-07-06 15:39 EDT by DC
Modified:	2005-07-06 15:46 EDT (History)
CC List:	1 user (show)

See Also:

Attachments
Example file (1.90 KB, text/java) 2005-07-06 15:43 EDT, DC	no flags	Details
View All 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 DC

2005-07-06 15:39:47 EDT

Hi,

I am using Linux-GTK Version and the table's vertical scrollbar(& maybe 
horizontal scrollbar) is not behaving.

I have added a selection listener to the table's vertical scrollbar and I am 
capturing its events. But the Event.detail is always set to zero. So I am 
unable to make out whether it was a SWT.ARROW_DOWN, SWT.ARROW_UP ... or 
SWT.PAGE_DOWN.

Is this is a bug or is there a work-around ?

Comment 1 DC

2005-07-06 15:43:20 EDT

Created attachment 24397 [details]
Example file

Here's an example for what I am trying to do.

By the way, I already tried on Eclipse 3.1 and also GTK2.2 and GTK2.4

Comment 2 Billy Biggs

2005-07-06 15:46:47 EDT

The information is not being exposed by GTK+ until version 2.6, so you'd need
yet another upgrade, but unfortunately we aren't yet returning it. :(

I'm going to put this feature in ASAP though -- I had it ready near the end of
3.1 but the signal signature is a little different than others so it would have
required some low-level tweaks that were too risky to go in so late.

*** This bug has been marked as a duplicate of 51995 ***