Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340699 - Need possibility to set the disabled icon on Buttons
Summary: Need possibility to set the disabled icon on Buttons
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.5.2   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-22 15:27 EDT by Daniel Migowski CLA
Modified: 2019-11-08 04:40 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Migowski CLA 2011-03-22 15:27:02 EDT
Hi,

I have an application with a lot of buttons, many of them very small with icons on them, and often many of them are disabled.

Here comes the problem: Each diabled button takes my image (the same nearly every time), and renders a disabled version of the image, over and over again. Completely useless. I would love to be able to set the disabled image for myself, so I can reuse these images across my app.

Advantage 1: I believe my own disabled images will look better that the ones SWT creates by just using a threshold on each pixel and rendering it transparent or opaque. 

Advantage 2: Each disable button image has to send through RDP connections when using the app. If I reuse the images, only the handle has to send through RDP. I know this is fine tuning, but why shouldn't I be able to do this? 

If disabled images are not supported on a platform, just stick with your current approach there, and note it in the docs (Hey, some Style bits are hints, too), but for everyone else this would be a huge win!

Thank you very much for your time,
Daniel Migowski
Comment 1 Lars Vogel CLA 2019-11-08 04:40:50 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.