Detect if SL viewer is the active window?

[Noel Loordes]

I am trying to write and refine a relay, that relays local chat to Growl for desktop notifications. Since the only such possibility is to mirror all local chat in an llInstantMessage() to the llGetOwner(), which spams the chat console for the user of the script, I was wondering if any of these things is possible:

1. Detect if the SL Viewer is the active window.
2. Display instant messages from the relay as a separate tab.
3. (Firestorm specific) Relay messages to Growl explicitly, without making them visible inside the client.

Is there any such facility?

Things that did not work

Querying the AFK status with llGetAgentInfo. The script is supposed to forward all local-chat messages the user has received while not having SL in the foreground, starting the moment they tabbed out. AFK won't kick in until at least 2 minutes after doing so, and it will also kick in if the user just doesn't make any inputs. Also, it is not desirable to be considered AFK, while being able to instantly react to local chat because of the relay.

Disabling Firestorm's "Show Growl Notifications while Firestorm is active" option. This reduces the notification spam, but the relay script would still spam the local-chat log of the user with duplicate messages, while the client is actually the focused window.

Edited May 26, 2019 by Noel Loordes
Added "relay messages to growl" question.

[Whirly Fizzle]

I showed this to one of the Firestorm developers & he said there is no way for a script to get if the agent has an SL viewer active or not.

You should file a feature request on the Firestorm JIRA for all local chat messages to be able to come through Growl.

[Lucia Nightfire]

10 hours ago, Whirly Fizzle said:

I showed this to one of the Firestorm developers & he said there is no way for a script to get if the agent has an SL viewer active or not.

You should file a feature request on the Firestorm JIRA for all local chat messages to be able to come through Growl.

There is this bug though, heh. I've used it to tell if AFKer's are really AFK or not. Yes, there can be other possible false positives associated with it.

Edited May 28, 2019 by Lucia Nightfire

[Noel Loordes]

14 hours ago, Lucia Nightfire said:

There is this bug though, heh. I've used it to tell if AFKer's are really AFK or not. Yes, there can be other possible false positives associated with it.

Doesn't look like this bug can be used to detect the AFK status from within an attachment I am wearing myself

[Noel Loordes]

As an intermediate workaround I am reducing chat-log clutter by using the @recvchat_sec and @recvemote_sec RLV settings. This was, the names still are duplicated, but at least the messages are not. Hope I will eventually find a better method, that doesn't require RLV...

Edited June 1, 2019 by Noel Loordes