[F-Script-talk] Odd solution (was Unable to use F-Script Anywhere)

[Peter J. H. <hph...@ju...>]

Philippe,

I finally managed to use F-Script Anywhere successfully.
The solution, however, is odd: I launch the app from the terminal using

sudo /Applications/Programming/FScriptBin/F-Script\ Anywhere.app/ 
Contents/MacOS/F-Script\ Anywhere

Why is this? Why is it, that for other users there seems no need to do.

I am running it from an Admin-Account.
F-Script Anywhere therefore is running as root, whereas all the target  
apps are running under my admin log-in name.
Both F-Script Anywhere and the target apps have read-write-access from  
my admin account and the admin group.

What might be happening.
Repairing access privileges using Disk Utility made no difference.

Thanks again,

Peter

Am 23.06.2008 um 22:37 schrieb Philippe Mougin:

> Hi Peter,
>
> It works well for me (Mac OS X 10.5 Intel, F-Script Anywhere  
> 1.3.1).  What platform are you running on ? Which version of F- 
> Script Anywhere ?
>
> Philippe
>
> Le 20 juin 08 à 21:52, Peter J.Hartmann a écrit :
>
>>
>> Hi,
>>
>> I'd have liked to make Preview.app somewhat scriptable.
>>
>> I downloaded the most recent F-Script binary but it turns out that I
>> am unable to inject F-Script into any application but itself (i.e. F-
>> Script Anywhere).
>>
>> I invariably get the following message:
>>
>> F-Script Anywhere was unable to install itself in the selected
>> application (process ID 492), because F-Script Anywhere must be
>> installed in a Cocoa application running as the current user.
>>
>> You may be attempting to install in a setuid application, which is  
>> not
>> supported.
>>
>> This is a bit cryptic.
>>
>> Preview.app, Mail and all the others shown in the list of running
>> applications certainly are Cocoa apps.
>> They are all launched from my user account and run under my user  
>> name.
>>
>> Furthermore, what is a setuid application?
>>
>> I suspected a conflict with input managers, removed them and rebooted
>> the machine.
>>
>> No avail.
>>
>> Any ideas?
>>
>> Thanks a lot!
>>
>> ___ Peter Hartmann ________
>
>
>


___ Peter Hartmann ________

mailto:hph...@ju...