New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Area lost on update #1
Comments
As another note: if I explicitly try to set it after save, all good:
|
just noticed this issue, I'll take a look after work |
First of all, massive thanks for playing with this code and finding the bug. The bug was caused by a specific behavior of Things - when a Todo was saved without a project, Things moved it to the Next list and removed the area. I've corrected it by doing 2 things:
Hope that fixes the issue on your end too :) |
Awesome; looks pretty good. I'll give it a try shortly, make sure it works in my setup, and update this if I run into any more troubles. Cheers, by the way; really well-designed library you've got here. |
This correctly sets up "New Todo" inside of "Existing Area". But then:
I can see Things flicker as it adds "New Todo" inside of "Existing Area", but immediately it reassigns it to a nil area (ie, re-finding the todo and calling
#area
on it returns nil).Looks like the library's properly setting the area in creation, and possibly doing it correctly in update (the AppleScript references get passed correctly in
Things::Reference::Record
L72)- have you run into this at all before? Maybe just an irritating Things bug?The text was updated successfully, but these errors were encountered: