[chandler-users] Alarms beating sync!
mimi at osafoundation.org
Tue Aug 12 15:37:15 PDT 2008
Ouch. That is a problem.
There isn't a workaround for this right now. Jeffrey, Grant: How hard
would it be to create a menu item that applies all conflicts in one
As you've noted, support for "sharing with yourself" is a bit behind
"sharing with others".
If this doesn't cramp your style too much, you could try not sharing
alarms under Share>>Manage... Of course that would only work if you
mostly only need to set and receive alarm notifications from 1 of
On Aug 7, 2008, at 5:16 PM, Paul Mattal wrote:
> I first want to say-- Chandler is amazing! I'm not sure how I ever
> accomplished anything without it. It's made me massively more
> productive, and I hope one day to have enough time to dive into the
> code and give something back to the project.
> There's a class of problems that occur for me, I think because I
> use several machines to access a few collections from 3 different
> computers (home, work, laptop). There might be some things to think
> about for this usage pattern in general, which ties into some other
> things I've heard suggested here about storing preferences
> (collection colors) and/or syncing the Dashboard.
> The biggest problem from this category for me is that the following
> scenario is very common for me:
> 1) Come in to work. Touch many items in my NOW bucket. Most of them
> end up LATER with new alarms set for future dates. Close Chandler
> at the end of the day (or not).
> 2) Go home and open Chandler at home.
> 3) First, Chandler processes all of its alarms.. the OLD ones for
> all the items above. This kicks them all into NOW.
> 4) Then Chandler syncs the collections and gets the new alarms.
> However, since the state change was more recent (I think), the
> LATER state stored in the collection is applied as a "pending change".
> 5) I spend at least 10 minutes clicking each item and applying the
> pending changes and getting myself back to the state I was looking
> at when I left work.
> Is there any way around this? Something that blindly applied all
> pending changes would even be fine for me. Or some way to keep the
> alarms from triggering before the first sync.
> Any workaround, or even advice that I should be doing this
> differently, would be greatly appreciated! It seems like the
> simplest thing would be to have a single action to apply all the
> pending changes without confirmation.
> P.S. Thanks to the list for the suggestion on fixing timezone
> confusion. I think it's helping.. as I work through items, there
> seem to be fewer and fewer with confused time zones.
> chandler-users mailing list
> chandler-users at osafoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the chandler-users