Push and Hold Macros
Any macro can be programmed so that nothing will happen if the button is simply tapped. You can force the client to
press and hold for any time between .1 and 99 seconds to issue a macro. For most clients, this would be a bad idea
since it makes things more difficult and more time consuming. However, here is an application that we think you
might find useful for particular clients:
PPuusshh aanndd HHoolldd ffoorr AAccttiivviittyy MMaaccrrooss aanndd TTaapp ttoo SSwwiittcchh DDeevviicceess
If you have a hobbyist client, a power user who is constantly switching devices and making adjustments to different
components, this can improve operation for him/her.
Here’s how this application works:
Program all of the MAIN MENU Activity Macros with the Macro Window in PRESS Mode and the option
bar set to AFTER .This ensures that the client will have to Press and Hold the button to issue the Macro.
With the option bar set to BEFORE, program a jump to the device only.
When the client simply taps a MAIN activity button, he/she simply switches devices.
OOnnee BBuuttttoonn IIssssuueess TTwwoo DDiiffffeerreenntt MMaaccrrooss
Since you can program 255 steps in either the BEFORE or the AFTER macro, you really have complete freedom to
program anything you can think of.
Status Messages for Impatient Clients with Long Macros
For clients who have problems waiting for long macros to finish, it is helpful to design the system to give a dramatic
status message while the macro is working, otherwise they may put the remote down in the middle of the macro, frus-
trating themselves. All you need to do is create some extra pages and place big buttons with text or graphics or even
animated graphics on each page. Insert jumps to the appropriate pages in your macro and the result is that the client
sees a slide show with your messages on it as the macro plays back.You can do a smaller version, by programming text
in the macro itself, text shows up only on the button, so may not be visible enough for clients
Helping Confused Clients
When do clients get confused? When their system is full of old gear they couldn’t afford to replace! When the
salesmen sell components without discrete codes! When the manufacturer of a cool new product blows it and
incorporates hard to use, but vital features!
In any event, by using MXEditor you can often solve some problems very effectively.
TTOOAADD -- TTVV IInnppuutt ““SSccrroollllss”” oorr ““TTooggggllee”” aanndd hhaass nnoo WWoorrkkaarroouunndd
When you have a component that is difficult to automate, it helps to call it names (TOAD, for Toggle Only Actuated
Device, has been suggested). Once you have vented your feelings, get out MX3000 Editor and go to work.There is a
relatively simple way to make operation of a device like this much less confusing. Here’s how to go about it:
5500
TTyyppee iinn SSeeccttiioonn TTiittllee
U
S
I
N
G
M
X
3
0
0
0
E
D
I
T
O
R
T
O
P
R
O
G
R
A
M
AAddvvaanncceedd PPrrooggrraammmmiinngg TTeecchhnniiqquueess aanndd IIddeeaass
To Next Page
Loading...
Need help?
General
