Confirmed users
293
edits
| Line 35: | Line 35: | ||
So, suppose we matched a filter. What can the user tell us to do from the first field? | So, suppose we matched a filter. What can the user tell us to do from the first field? | ||
* | *Display on: | ||
* | ** the target tab (passed in by the caller, usually server / channel / user) | ||
* | ** the source tab (for example, the user who sent the message) | ||
* | ** the current tab. (whatever's current when display is called) | ||
* | ** the handling tab. (the tab display was called on) | ||
* | ** the parent of the handling tab. This is the network/server tab for users/channels/dcc, and the client tab for networks/servers. | ||
* | ** the client tab. Plain, simple. | ||
*Get Attention. Will flash the window. Ignores other fields. | *Get Attention. Will flash the window. Ignores other fields. | ||
*Set the tab state. Will use the other field to pick a state and | *Set the tab state. Will use the other field to pick a state for this, and a list of views to try and set (same options as the display action). | ||
*Play sound. Takes the second field into account: beep or url to sound file | *Play sound. Takes the second field into account: beep or url to sound file | ||
*Dispatch. Takes the second field as the parameter. | *Dispatch. Takes the second field as the parameter. | ||
*Run function | *Run function. | ||
=== Existing things that could be done using filters === | === Existing things that could be done using filters === | ||