Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340395 - FontDialog.open() returns null when only color is changed
Summary: FontDialog.open() returns null when only color is changed
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.1   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2011-03-17 23:27 EDT by qiulin CLA
Modified: 2020-03-11 13:59 EDT (History)
4 users (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 qiulin CLA 2011-03-17 23:27:20 EDT 
Build Identifier: 3.6.1.v3657d-RCP20110311-1452

Usually FontDialog.open() returns an object containing changed attributes. However, if the user changes only color (not size, font name, .etc), it will return null. This looks to me that the FontDialog thinks nothing is changed by the user. This is not correct.

Reproducible: Always

Steps to Reproduce:
1. Invoke FontDialog.open()
2. The font dialog pops up. Make change on color only. Close the dialog.
3. The open() method returns null.
Comment 1 mukundan desikan CLA 2011-03-21 15:40:13 EDT 
This issue is reproducible on SWT3.6.2 by Lotus team on mac 10.6
Comment 2 Lakshmi P Shanmugam CLA 2011-03-29 07:18:14 EDT 
When only the font color is changed, open() method returns null, but FontDialog.getRGB() returns the color that was selected in the dialog. 
Same behavior is seen on both Cocoa and Carbon.
Comment 3 Lakshmi P Shanmugam CLA 2017-07-03 07:46:02 EDT 
Bug triaged, visit https://wiki.eclipse.org/SWT/Devel/Triage for more
information.
Comment 4 Eclipse Genie CLA 2020-03-11 13:59:16 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.