Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353905 - Scrollable.getClientArea() behavior differs greatly on Mac OS X
Summary: Scrollable.getClientArea() behavior differs greatly on Mac OS X
Status: CLOSED DUPLICATE of bug 333375
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.7   Edit
Hardware: Macintosh Mac OS X
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-04 11:18 EDT by Markus Tiede CLA
Modified: 2011-08-05 13:50 EDT (History)
2 users (show)

See Also:


Attachments
Fedora 8 GTK 32bit behavior (124.34 KB, image/png)
2011-08-04 11:18 EDT, Markus Tiede CLA
no flags Details
Windows 2008 32bit behavior (23.23 KB, image/png)
2011-08-04 11:18 EDT, Markus Tiede CLA
no flags Details
Mac OS X 10.6.8 64bit Cocoa behavior (112.63 KB, image/png)
2011-08-04 11:19 EDT, Markus Tiede CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Tiede CLA 2011-08-04 11:18:21 EDT
Created attachment 200923 [details]
Fedora 8 GTK 32bit behavior

The SWT API behavior differs greatly when running on Mac OS X:

Calling getClientArea() on a Scrollable, e.g. a List, returns different y-Coordinates for the rectangle representing the client area, as soon as the Scrollable is scrolled to display a list item.

See the attached screenshots for further information: I used Fedora 8 GTK 32bit and Windows 2008 32bit as reference platforms to show the "normal" behavior. In addition to that I started the same application on Mac OS X 10.6 Cocoa.

I "produced" the output as follows:
 - launch the snippet application, re-size it to show only e.g. 4 items, place it to the top (to avoid too big screen coordinates - easier to read and understand ;) )
 - select the first item 0 and successively select item n + 1 and so on
 - as soon as the scrolling starts (In my case item 3) the behavior differs on Mac OS X
Comment 1 Markus Tiede CLA 2011-08-04 11:18:54 EDT
Created attachment 200925 [details]
Windows 2008 32bit behavior
Comment 2 Markus Tiede CLA 2011-08-04 11:19:33 EDT
Created attachment 200926 [details]
Mac OS X 10.6.8 64bit Cocoa behavior
Comment 3 Felipe Heidrich CLA 2011-08-04 11:48:47 EDT
it is possible this is the correct behaviour on the mac, silenio ?
Comment 4 Felipe Heidrich CLA 2011-08-04 11:54:44 EDT
See Bug 353907 also
Comment 5 Felipe Heidrich CLA 2011-08-05 13:50:38 EDT
that is indeed the correct bevhaior on the mac, see bug 333375 for a more complete discussion on this problem.

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