Support
All support resources for our products. Here you can find answers to frequently asked questions, discuss with other users, recover a lost license code or file a support request.
Forum closed
This forum was closed and turned into an archive effective April 21, 2018. It is no longer possible to create new topics or reply to existing topics.

Thanks everyone for all the great questions and contributions over the years.

Please use the Contact form to get in touch.

Remote Buddy Forum

Overview 

AuthorThread
User

30.09.2010 03:08:39
behavior htpc1 does not support application quitting
View

This posting is older than 6 months and can contain outdated information.
Hello,

I've been trying to create a behavior that will launch an action and the first set of the action is "Behaviour Action: Quit currently controlled application" when it try to activate that action I get the following error "behavior htpc1 does not support application quitting." Any help on overcoming this problem would be greatly appreciated. 

These entries from the FAQ may be relevant to this topic:

Behaviours
User

01.10.2010 12:21:47
Re: behavior htpc1 does not support application quitting
View

This posting is older than 6 months and can contain outdated information.
Thanks for asking.

The currently controlled application is determined by the Behaviour based on how you set it up. For Behaviours created with the BCK, the currently controlled application is identified using the bundle identifier you entered at

Behaviour Construction Kit > Behaviour Factory > Specification and metadata > Application recognition > Bundle identifier

If this entry is empty or invalid, then it's impossible for Remote Buddy to find out which application this Behaviour is targeted at - and consequently also can't perform any application actions like quitting.

Best regards, 
Felix Schwarz 

User

03.10.2010 01:06:09
Re: behavior htpc1 does not support application quitting
View

This posting is older than 6 months and can contain outdated information.
Thank you for the information.

Has anyone in this Forums implemented the miniharmony setup as described at the http://miniharmony.blogspot.com/ and if so how did you get around the above problem?