Bug 76735 - [Preferences] Need better warning/error dialog when saving of preferences fails
Summary: [Preferences] Need better warning/error dialog when saving of preferences fails
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0.1   Edit
Hardware: PC Linux
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2004-10-21 06:28 EDT by Marc CLA
Modified: 2019-09-06 15:36 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc CLA 2004-10-21 06:28:08 EDT
A custom code formatter profile is lost when Eclipse is closed and the built in
Java Convention profile is selected by next start.
Comment 1 Dani Megert CLA 2004-10-21 08:57:48 EDT
Works for me using I200410190941.
See also:
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-text-home/development/bug-incomplete.htm
Comment 2 Marc CLA 2004-10-22 08:58:20 EDT
I don't know why but some of the files in the .metadata dir were read-only.
After having fixed this, everything is now ok again.

Perhaps should Eclipse cry that it can't save preferences because of read-only
problems.
Comment 3 Martin Aeschlimann CLA 2004-10-25 04:39:04 EDT
good point. There should really be some warning/error dialog when Eclipse 
cannot save the prefenerces
Reopening
Comment 4 Martin Aeschlimann CLA 2004-10-25 04:44:28 EDT
Just tested. On windows, when I set the files in .meta to read-only I get an 
error dialog. The message is not very helpful tough and cut off

Moving to platform
Comment 5 Tod Creasey CLA 2005-01-05 14:48:30 EST
Reducing to P4 as the only remaining issue is how to handle the wrapping on 
Windows (which does not wrap paths).
Comment 6 Susan McCourt CLA 2009-07-09 19:26:39 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 7 Eclipse Webmaster CLA 2019-09-06 15:36:43 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.