[chandler-users] Location field completed with the wrong location

Owen Kelly owen at owenkelly.net
Wed May 20 11:34:21 PDT 2009

Graham Perrin wrote:
> Graham Perrin wrote:
>> In Chandler Desktop 1.0.3 RC1 I found that auto-completion in the
>> location field caused more problems than it solved:
>> <https://bugzilla.osafoundation.org/show_bug.cgi?id=12729>. As a result
>> of the conflict, the vast majority of locations were wrong, I had to
>> correct all such entries. 
>> 1.0.3 final appears to be without that problem :)
> I spoke too soon. This morning the bug bit me again. 
> Every time I enter a location then key tab (to progress to the next
> field), Chandler Desktop enters the wrong location. 

And I have only just noticed (because I was following up what you just
wrote) that Notes that aren't events don't have location fields - even if
they have tickler alarms set.

Why would I want this?

Example: I notice that a new Dilbert collection has been published and think
"I'll pick that up next time I am in the city centre". In RTM I dealt with
this by entering an unscheduled task with a location of @city. Then when I
was about to go into the city centre I looked at a filtered smart-list
showing all the undone tasks with a location of @city. Bingo: a lot of
little errands bubbled to the surface just when I was in a position to do

I know I could write @city in the main text field. It just seems
inconsistent to me :)

View this message in context: http://n2.nabble.com/Using-Chandler-successfully-%28was%3A-Unscheduled-%27to-do%27-lists%29-tp2938080p2947837.html
Sent from the Chandler users mailing list archive at Nabble.com.

More information about the chandler-users mailing list