Bug 181723 - [Program] Update API (Program.getImageData) to get bigger icons.
Summary: [Program] Update API (Program.getImageData) to get bigger icons.
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Steve Northover CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-10 04:58 EDT by Nicolas Richeton CLA
Modified: 2019-09-06 16:05 EDT (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 Nicolas Richeton CLA 2007-04-10 04:58:46 EDT 
While 16x16 icons are perfect for table and tree, there is some case where bigger icons are needed. 

For example, it is possible to use Nebula's Gallery widget to create a file browser like windows explorer, but 16x16 icons are just too small.

Currently, on windows icons are 48x48 - 64x64
on osx : 256x256

It would be great if we could ask for the best icon for a specific size.
(Program.getImageData( size))
Comment 1 Steve Northover CLA 2007-04-10 12:13:29 EDT 
No new API for 3.3.
Comment 2 Eric Zimmerman CLA 2007-04-10 12:47:14 EDT 
Duplicate https://bugs.eclipse.org/bugs/show_bug.cgi?id=162314

Not exactly the same resolution request though...
Comment 3 Nicolas Richeton CLA 2009-06-10 10:36:48 EDT 
On SWT 3.5 Cocoa, I now get 256x256 images, which is GREAT. But the API as not changed. Should this be considered as the new behavior or is this just a bug ?
Comment 4 Steve Northover CLA 2009-06-10 10:48:37 EDT 
This seems like a bug.  New API should be added to query a requested size.  Applications can use Display.getIconSizes() to determine the recomended icon sizes for a platform.
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:05:26 EDT 
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.