This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 120738 - Deleting a color profile does not delete all files
Summary: Deleting a color profile does not delete all files
Status: RESOLVED WONTFIX
Alias: None
Product: editor
Classification: Unclassified
Component: Options (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: issues@editor
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-31 23:24 UTC by devon_c_miller
Modified: 2009-11-02 11:00 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

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 devon_c_miller 2007-10-31 23:24:30 UTC 
This is with 6.0beta2

When a theme is created (Duplicate) it creates new directories bearing the name of the theme, each containing 
org-netbeans-modules-editor-settings-CustomFontsColors-tokenColorings.xml

When a theme is deleted, the xml files are deleted, but the directories are not.

Thus, by creating a theme "Foo", then removing it, it becomes impossible to create a new theme "Foo" because the
directories already exist.

Also, if the theme deleted is the current theme, and a new theme is not explicitly selected, the currentFontColorProfile
entry in config/.nbattrs is not changed. On next startup a non-existent theme will be applied, yielding black on white.
Comment 1 Jiri Prox 2007-11-01 10:32:48 UTC 
The black and white problem is already solved in daily build - see issue 119709

The second problem occur only when the new profile is created after deleting the old one w/o closing options dialog.
To workaround it close the options dialog once you have deleted the old profile and the you can create the profile again
-> so IMHO it is not so serious bug -> P4
Comment 2 devon_c_miller 2007-11-02 13:38:04 UTC 
Yes, a workaround does make it less serious. Thank you. I tried lots of things, but apparently not the right combination.
Comment 3 David Strupl 2009-03-31 15:51:28 UTC 
Resolving all issues with milestone "future" as LATER. If you feel strongly that
it should be implemented please reopen and set the target milestone to "next".
Comment 4 Quality Engineering 2009-11-02 11:00:23 UTC 
NetBeans.org Migration: changing resolution from LATER to WONTFIX