The Omni Group
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!

Go Back   The Omni Group Forums > OmniFocus > OmniFocus Extras
FAQ Members List Calendar Search Today's Posts Mark Forums Read

 
Leopard-baked applescripts on Tiger machines Thread Tools Search this Thread Display Modes
It seems that there is at least one potential problem with running Leopard-compiled applescripts on Tiger-powered machines.

As far as I can tell a workable solution may be to distribute such scripts in plain text .applescript form rather than as compiled .scpt files.

Tiger users should then be able to compile the scripts successfully in Script Editor, and save them as .scpt

Last edited by RobTrew; 2007-12-19 at 12:35 PM..
 
People have complained that my scripts, written and functional in Tiger, don't work in Leopard. Do you know if going the opposite direction is also a problem?
 
Quote:
Originally Posted by MB_UST View Post
Do you know if going the opposite direction is also a problem?
There is certainly at least one problem if you distribute Leopard-compiled (.scpt) scripts rather than text (.applescript) scripts - Tiger tends to choke on some special characters like ≠ and if the script was compiled on Leopard.

In addition there may be some residual fragility and non-portability surrounding scripts which refer to selected trees of content, even though a previous thread ended on an optimistic note.

A script which worked on Leopard with:

Code:
tell application "Omnifocus"
tell front window
			set lstTrees to selected trees of content
			if (count of lstTrees) = 0 then
had to be rewritten (for at least one Tiger system) to the more explicit:

Code:
tell application "Omnifocus"
tell document window 1 of front document
			set lstTrees to selected trees of content
			if (count of lstTrees) = 0 then

Last edited by RobTrew; 2007-12-22 at 10:43 AM..
 
Quote:
Originally Posted by MB_UST View Post
Do you know if going the opposite direction is also a problem?
There is certainly at least one problem if you distribute Leopard-compiled (.scpt) scripts rather than text (.applescript) scripts - Tiger tends to choke on some special characters like ≠ and if the scripts was compiled on Leopard.

In addition there may be some residual fragility and non-portability surrounding scripts which refer to selected trees of content, even though the a previous thread ended on an optimistic note.

A script which worked on Leopard with:

Code:
tell application "Omnifocus"
tell front window
			set lstTrees to selected trees of content
			if (count of lstTrees) = 0 then
had to be rewritten (for at least one Tiger system) to:

Code:
tell application "Omnifocus"
tell document window 1 of front document
			set lstTrees to selected trees of content
			if (count of lstTrees) = 0 then
 
 


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads
Thread Thread Starter Forum Replies Last Post
AppleScripts questions jphalip OmniOutliner 3 for Mac 8 2010-05-15 06:35 PM
Using your own icons for your applescripts fudster OmniFocus Extras 0 2009-07-30 12:58 PM
Syncing Leopard and Tiger Ward OmniFocus Syncing 2 2008-08-27 11:27 PM
Leopard Bookmark Folders shown in Tiger Chiller OmniWeb Bug Reports 0 2008-03-15 07:12 AM
Several applescripts for OF spnyc OmniFocus Extras 2 2007-07-09 02:51 PM


All times are GMT -8. The time now is 10:44 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.