anyRemote · Control your computer with your phone
Description: anyRemote project page - Bluetooth remote control tool

Skip to content

# anyRemote

# Make(...) command

This command used to control local state of anyRemote

## Format description

    Make(exit|flush|stop|disconnect|mode|none|remote|var|alarm[,....])

Several examples:

    0=Make(flush)
    1=Make(stop)
    2=Make(disconnect)
    3=Make(mode,mode_2)
    4=Make(remote,on)
    5=Make(var,my_var,date)
    6=Make(alarm,/tmp/alarm,ALARM_MACRO)

## Make(flush)

This command used to flush all configuration information.

    0=Make(flush)

It is guarantied what current command sequence will be executed till the end. This means what in the following command sequence both commands will be executed:

    0=Make(flush);Set(title,all data flushed);

The typical use-case for Make(flush) is the following:

    0=Make(flush);Include(/path/to/another/configurational/file);

## Make(stop)

This command used to stop execution of command sequence.

    0=Make(stop);Exec(echo "Never executed");

In the example above Exec(...) command will not be executed because execution will be stopped on Make(stop) command.

## Make(disconnect)

This command used to close connection to the device. In server mode after 5 seconds anyRemote will be able to receive incoming connection. In AT mode anyRemote will try to reconnect to the pnone after timeout specified by RetrySecs parameter (default value is 1 minute).

    1=Make(disconnect)

## Make(exit)

This command used to stop anyRemote and exit. It is a synonym to the "Exit" command.

    #=Make(exit)

## Make(mode,...)

Change current mode (group of key-to-command mapping) (do not mix this with AT/Server mode !).

As a side effect (ExitMode) and (EnterMode) "events" can be executed.

Format:

    Make(mode,_mode_name_)

    2=Make(mode,_new_mode_)

## Make(remote,...)

Format:

    Make(remote,on|off)

Switch on/off command processing without disconnection from the phone.

    2=Exec(amixer -c 0 sset Master,0 mute);Make(remote,off)

Take a look to the order of commands above. Make(remote,off) command is the last one. If You change order to

    2=Make(remote,off);Exec(amixer -c 0 sset Master,0 mute)

then Exec(amixer -c 0 sset Master,0 mute) will not be executed because "remote control" functionality will be switched off before it.

## Make(var,...)

Format:

    Make(var,_var_name_,_command_to_execute_)
    Make(var,_var_name_,by_value,_value_)

Sets internal variable. To access to the previously set internal variable use $(_var_name_) syntax.

    2=Make(mode,my_var1,echo "Hello")
    3=Make(mode,my_var2,by_value,world!)
    4=Exec(echo "Value is: $(my_var1) $(my_var2))

There are exists several predefined variables. See this for details.

Note: There are collision of $(_var_name_) syntax and shell command substitution syntax $(...). So, do not call Your internal variables with names which can be treated as shell commands.

## Make(alarm,...)

Format:

    Make(alarm,_alarm_file_,_key_)

Sets an alarm handler. When file _alarm_file_ will be created, then specified key definition will be searched. Alarms are checked each 15 seconds.

    6=Make(alarm,/tmp/alarm,ALARM_MACRO)
    ALARM_MACRO=SendCKPD(E 1 1 1 1 1 1 1 S \
    	PAUSE PAUSE PAUSE PAUSE PAUSE PAUSE E E * 3 *)

## Make(none)

Dummy command, does nothing.

    0=Make(none)

Maintained by anyRemote. Website by m.lettner.