More clients and interfaces

On this page I am mentionning a few other clients shipping with the Theme-O-Matic. They are usually scripts requested by customers I found would be useful to the Theme-O-Matic community. All these scripts are full permissions and configuration instructions are included as comments inside them, as well as version history where appropriate.

Do you need help or a specific custom script? Contact me!

Remote Control

This client is used to control the Theme-O-Matic by touching another object or another prim from the same object. Typical uses are remote control HUDs and on-wall switches.

This client manages no menu, instead it focuses on which prim is touched to determine which theme to apply. It is made of two scripts:

• T-O-M-SC RemoteControl goes into the object you want to touch to have the themes applied

• T-O-M-SC RemoteRelay goes inside the prim containing the Theme-O-Matic scripts.

The principle is that when someone touches the remote control, a message containing the toucher's identity and the name of the touched prim is sent (over a private channel or as a link_message, please read the details inside the comments). The Remote relay receives this messages and determines what to do depending on its configuration.

What is important to remember is that you have to name your controlling prims to something meaningful, just don't leave the default name "Object"!

As an alternative (originally requested by a customer), the T-O-M-SC RemoteControl script may be replaced by the T-O-M-SC RezControl. The difference compared to the former is that a message is sent to the T-O-M-SC RemoteRelay immediately when the object is rezzed. It may prove useful when your objects are rezzed by another script. It features very simple configuration options inside the script, the comments will help you, again.

AVSitterMenu

In the previous section a method to interface AVSitter™ and Theme-O-Matic was described that requires no extra script, only a direct message sent from AVSitter™ to Theme-O-Matic. This method is rather rigid and has drawbacks like the menu not reopening after a theme is selected for example.

To have more elaborate possibilities a new client script was created to create a specific menu that can be opened thanks to a BUTTON directive in AVSitter™. The client script, called T-O-M-SC AVSitterMenu, manages this menu and performs the message sending to the Theme-O-Matic by itself. You will find it is much more flexible:

• you define the expected BUTTON parameters (so you can have several instances of AVSitterMenu in the same prim) to react to;

• you define the list of themes to explicitely preload if required;

• you define the menu buttons, pagination is automatic;

• you control how verbose the script is and other parameters like what to do when a theme is applied: do nothing, reopen the themes menu, or reopen AVSitter™'s own menu.

Again everything is explained in the script comments, do not hesitate to contact me if you need further help.

By request of a customer, a synchronization ability was added in the form of a "slave" script named T-O-M-SC AVSitterMenu Slave that is intended to go into "props" as defined in AVSitter. This offers a way to synchronize the themes between the master object and the props, no matter if they are rezzed prior or after to the activation of that theme.

The configuration is a bit subtle with theme grouping (they actually define groups of themes that may be synchronized with certain props and not others, for example), but hopefully the extensive comments will help you.

SetThemeOnPose

The T-O-M-SC SetThemeOnPose is yet another complementary client script designed to work between AVSitter™ and Theme-O-Matic.

It is a very simple script; its job is to wait for a message from AVSitter™ saying a pose has begun, and activating a specific theme when this happens. It supports multiple such poses and is also able to send initial commands for example to explicitely preload specific themes.

This client has been used to adapt the local position and orientation of prims when someone uses furniture: cushions, handcufs...

[zED]~MPS~Multisit Pose System™

The [zED]~MPS~Multisit Pose System™ (MPS for short) is another popular system used for furniture, much like AVSitter™. On demand by a customer a specific client script called T-O-M-SC MPS to TOM was written to allow easy usage of the Theme-O-Matic from the MPS menu.

It is a very simple script derived from the official MPS API script to support sending messages to the Theme-O-Matic. Customization is somewhat less obvious than other standard clients though, although the comments try to help. Reading the scripting reference section of this site will help too.

Linkmsg_interface

Sometimes for various reasons you cannot get the exact link_message you need to be sent from a third-party script to the Theme-O-Matic, but you receive an inappopriately-formatted message. In that case you can configure the T-O-M-SC Linkmsg_interface script so that it translates the message into something the Theme-O-Matic understands.

This process is based on a translation table that is documented in the comments of the script, please refer to them.