Why are there flattened tasks, project, contexts, etc? Several seemingly simple query work with flattened item and I don't understand why they wouldn't work with the not flattened items.
These forums are now read-only. Please visit our new forums to participate in discussion. A new account will be required to post in the new forums. For more info on the switch, see this post. Thank you!
|
|
FAQ | Members List | Calendar | Today's Posts | Search |
What is the point of "flattened" things? | Thread Tools | Search this Thread | Display Modes |
Member
2013-06-24, 07:23 PM
Why are there flattened tasks, project, contexts, etc? Several seemingly simple query work with flattened item and I don't understand why they wouldn't work with the not flattened items.
Post 1
|
Guest
2013-06-24, 11:33 PM
The non-flattened versions are nested tree-like structures, and you would have to write a recursive function to 'walk' through them in order to visit every context, or every project in every folder, rather than just the top-level nodes which are immediate children of the document.
The 'flattened' versions are full lists of every node in the tree.
Post 2
|
Member
2013-06-25, 12:20 PM
Quote:
Code:
set theProject to project named "fooglebar" Code:
set theProject to flattened project named "fooglebar" or is the actual name of the project the full path?
Post 3
|
Guest
2013-06-25, 12:32 PM
This will work:
Code:
tell application id "OFOC" tell default document set oProj to project named "top level project" end tell end tell To find a project in a folder you would have to "tell" that folder to Code:
set oProj to project named "contained in folder"
Post 4
|
Member
2013-06-25, 01:04 PM
Thanks you, that completely explains it.
Post 5
|