Closed
Bug 292676
Opened 20 years ago
Closed 20 years ago
make composite calendar persist its membership and default-calendar settings
Categories
(Calendar :: Internal Components, defect)
Calendar
Internal Components
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: shaver, Assigned: shaver)
Details
Attachments
(1 file)
|
7.71 KB,
patch
|
vlad
:
first-review+
|
Details | Diff | Splinter Review |
I want to teach the composite calendar to take a "preference prefix" from its creator, and then initialize/track changes to its membership and default settings. In fact, I have done that teaching. Patch coming up.
| Assignee | ||
Comment 1•20 years ago
|
||
So one thing about this patch that might not quite be right is that we don't persist the "implicit" default setting that comes from being the first calendar added. So if you get the calendars back in a different order later, the first one added is the new default, again. I think that's fine -- if you want an explicit default, please to be asking for it! -- but someone else might not.
Attachment #182437 -
Flags: first-review?(vladimir)
Comment on attachment 182437 [details] [diff] [review] store $pref-in-composite and $pref-default in the calmgr prefs Please remove one of the two notifyObservers function definitions, but other than that r=vladimir
Attachment #182437 -
Flags: first-review?(vladimir) → first-review+
nm on the removal, didn't see there were 2 separate classes in the diff
| Assignee | ||
Comment 4•20 years ago
|
||
Fixed, way to read the diff!
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•