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.
Summary: | NbPreferences don't reload when underlying file is changed | ||
---|---|---|---|
Product: | platform | Reporter: | Jaroslav Tulach <jtulach> |
Component: | Options&Settings | Assignee: | Theofanis Oikonomou <theofanis> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | err, jmilkiewicz |
Priority: | P3 | ||
Version: | 7.1 | ||
Hardware: | Other | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | 200114 | ||
Bug Blocks: | 197594 | ||
Attachments: | Test and impl for automatic reload if underlaying store file is changed |
Description
Jaroslav Tulach
2011-05-17 07:58:02 UTC
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/abdf3b52a520 User: Yulia Novozhilova <ynov@netbeans.org> Log: Fix #198665 - NbPreferences don't reload when underlying file is changed Thanks to Jarda and Jakub for the patch! Your welcome. It was a pleasure to develop with Jaroslav. I hope we can organize some hacking at least next year. I think this change has problems, see bug 197594 comment 21 Integrated into 'releases' Changeset: http://hg.netbeans.org/releases/rev/1cdc8b3c5503 User: Yulia Novozhilova <ynov@netbeans.org> Log: Fix #198665 NbPreferences don't reload when underlying file is changed > I think this change has problems, see bug 197594 comment 21 Yes, we know this is not full solution to bug 197594 (especially the delivery of events is missing). Jakub and me had just one morning to implement this. Thus I reported this new bug rather modifying the old one. (In reply to comment #6) > ... this is not full solution to bug 197594 ... I was thinking more of the performance and synchronization issues introduced by a file modification rather than a file replace approach. The discussion in bug 197594 indicated that this fix should *not* be in 701. It was added 701 on 2011-06-14 as indicated in comment 5. Was it taken out? This should be now fixed. See comment 40 in #197594 |