RatAttack: not deprecating the pipe file for now
Passing parameters to VoiceAttack through the command line is not thread safe. For RATSIGNALS coming in in rapid succession (either because, well, several cases at once or when using an IRC bouncer, like I do) it completely messes up the data. see #51
This commit is contained in:
parent
dc263686e2
commit
2dd74ec19e
3 changed files with 0 additions and 9 deletions
|
@ -73,9 +73,6 @@ README. Yay!
|
|||
|
||||
* Is now set up to overwrite an old version on import. See “Updating”
|
||||
instructions in the README.
|
||||
* Passing RATSIGNALs via pipe file is now considered deprecated and will be
|
||||
replaced by passing it as a parameter on command invocation in a future
|
||||
version. Later down the line pipe file support will be removed.
|
||||
* All logging to the VoiceAttack event log is now properly encapsuled. See the
|
||||
docs for instructions on how to enable logging.
|
||||
|
||||
|
|
|
@ -66,12 +66,6 @@ through IRC. When off duty, it won’t.
|
|||
|
||||
#### Getting Case Data From IRC ####
|
||||
|
||||
**Note**: Passing RATSIGNALs through the pipe file is now considered deprecated
|
||||
and will be removed in a future version in favor of passing it as a parameter
|
||||
when invoking the VoiceAttack command. This is currently an experimental feature
|
||||
in VoiceAttack β 1.8.6.5. This section will be updated once it is working
|
||||
reliably.
|
||||
|
||||
You can setup your IRC client to pass incoming RATSIGNALS to VoiceAttack by
|
||||
writing them to a file (`%appdata%\Ratattack\ratsignal.pipe`), then calling the
|
||||
appropriate command (`RatAttack.announceCaseFromRatsignal` for notification,
|
||||
|
|
Binary file not shown.
Loading…
Reference in a new issue