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

Bug 346610

Summary:	[Preferences] prferences non-modal
Product:	[Eclipse Project] Platform	Reporter:	arne anka <eclipse-bugs>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	Michael_Rennie, prakash, remy.suen
Version:	3.6.2
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description arne anka

2011-05-20 05:17:47 EDT

i often find myself changing options in the preferences (most notably defining shortcuts), which require me to close the prefs dialog to check the effect and open the prefs dialog again to change it again.
key configuration in particular is tedious and not very user friendly -- havin the go through the whole open->close->test->open->... circle several times does not really improve those issues.

so, please, make the prefs dialog non-modal (and most other dialogs too, there are probably _very_ few dialogs requiring being modal).


-- Configuration Details --
Product: Eclipse 1.3.2.20110218-0812 (org.eclipse.epp.package.jee.product)
Installed Features:
 org.eclipse.platform 3.6.2.r362_v20110210-9gF78Gs1FrIGnHDHWkEcopoN8AmxeZflGDGKQi

Comment 1 Prakash Rangaraj

2011-05-23 02:59:48 EDT

I personally feel Preferences should be modal. But thats just me :-)

Comment 2 arne anka

2011-05-25 03:50:18 EDT

well, i think "modal" is way overrated and rather used in a way "if you have no idea what to do, make it modal (and disable text selection -- if the user really wants the text that bad, let him type it again!)".

Comment 3 Lars Vogel

2019-11-14 02:22:22 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.