I seem to be having a problem with Omit from Output and my screen reading program. The program is set to read all text as it comes in, with echo turned off on mushclient's side so it won't echo my command after I press enter. If I have a trigger set to omit from output, when the trigger fires, the client does something with the last line of output in the window so my screen reader will read it.
example:
trigger: *blah*
omit from output checked
You say 'test'
I type say blah
the screen reader reads "You say 'test'"
Is there anything I can do about this? these will be an important part of my mudding experience.
Whats the problem?
what are you trying to have happen?
You're triggering the server echoing back your say command? And then after that the first line is read? or what?
when the gagged text wants to be shown, the window must do some
behind the scenes redrawing - because it speaks the last line that
wasn't gagged. Repeated invocations of the gagged
line says nothing.
This has been discussed at some length in the past. Basically MUSHclient initially draws (on the screen) all text it gets, and then when it gets a newline character triggers are processed. If the trigger decides to omit from output, the line(s) in question are then removed from the output window.
If it didn't do that, lines with no newline (such as the initial prompt for your name and password) would never be seen. However a side-effect of this could be that screen readers will read out the line before it is omitted.
I'm not sure what a good work-around will be. Maybe some sort of trigger that catches all output you want to see (ie. that omits the offending lines) and sends them to a notepad window. Then the screen reader could read the notepad window instead. Or, instead of screen-reading the main window, have a trigger send lines to the screen-reader instead, omitting lines you don't want to hear. Not having used one, I'm not sure how to go about doing that.