FAQ
From ProxiPedia
All other topics
- See navigation on the left
General Questions about using Proxi can be asked, and answered, here or by emailing proxi@griffintechnology.com. This "article" page will contain the FAQ. Click on the "discussion" tab above to add your question to the "Talk" page, or to answer questions.
Contents |
[edit] Backing up your settings
Proxi stores its settings in a regular blueprint file in your user folder/Library/Application Support/Proxi/Store. As of Proxi v1.0 this file is backed up (Store~) but accidents can happen and it's very frustrating to lose all of your settings that you've meticulously configured. You make want to periodically make your own backup of the Store file or alternatively select all your triggers in the Proxi's main window and Save As Blueprint for the trigger popup menu or simply drag them to your Desktop to make a Blueprint containing all of your settings.
[edit] Proxi and other control panel settings
Proxi is meant for users that want to replace the basic software that comes with Griffin products. It removes the original driver during installation. Proxi doesn't require any drivers to communicate the device.
[edit] Powermate
If you have proxi installed this will override any settings you have configured in the powermate control panel.
You'll need to reinstall the PowerMate software if you'd like to use it instead of Proxi.
[edit] What is a "Fallback" trigger?
A fallback trigger is one that executes if no other identically defined trigger fires. Consider the following example:
Suppose you have several triggers assigned to the Play button on an AirClick and you want to designate one of those triggers to only execute if no other AirClick play button trigger fires. For example, you might define a AirClick trigger volume up and down to increase or decrease the volume in iTunes, but only if it is the active application. You define another set of volume up/down buttons and designate them as fallback triggers that adjust the system volume up or down. These triggers will not fire if iTunes is the active application. You could continue adding volume up/down triggers for various situations safe in the knowledge that if none of those trigger's conditions (filters) are satisfied then execution would fall back to the "fallback" triggers. I hope that makes sense :)
[edit] Using Proxi with Automator
Proxi can execute Automator workflows by following these steps:
* Save your Automator workflow as an application * Create the desired trigger in Proxi and add a Launch Application task to it * In the Launch Application task "Choose..." the Automator application you just created
