Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are
spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the
password reset link.
Due to spam on this forum, all posts now need moderator approval.
Entire forum
➜ MUSHclient
➜ Bug reports
➜ telopts, print, next output line
|
telopts, print, next output line
|
It is now over 60 days since the last post. This thread is closed.
Refresh page
| Posted by
| Bast
(78 posts) Bio
|
| Date
| Mon 30 Aug 2010 02:15 AM (UTC) |
| Message
| I have a scenario:
Receive some input from a telnet option protocol (GMCP, ATCP, Aardtelopts) and then print or ColourNote something during the OnPluginTelnetOption (or anything called from that, such as printing from a broadcast from that function).
The next line sent to output after printing or colournote is not categorized correctly. It doesn't trigger any trigger even if it should. Sometimes it is in the same colour as the previous print, sometimes not.
It is especially annoying when I am on the test port on aard and printing all the new GMCP stuff and half my other triggers aren't working because of it.
Can you take a look at it Nick?
Thanks,
Bast
|
Bast
Scripts: http://github.com/endavis | | Top |
|
| Posted by
| Nick Gammon
Australia (23,165 posts) Bio
Forum Administrator |
| Date
| Reply #1 on Mon 30 Aug 2010 02:58 AM (UTC) Amended on Mon 30 Aug 2010 05:37 AM (UTC) by Nick Gammon
|
| Message
| Is that this issue?
You could also try using the new plugin Messages_Window which was published here and also just released in version 4.59.
This lets you send messages to a miniwindow, so the output doesn't interfere with the MUD output.
It wouldn't surprise me that if you mixed up Note calls with standard MUD output (especially in the middle of a line, which might happen with GMCP) that it will get confused.
Either using a notepad window, or a miniwindow, solves this.
Messages_Window plugin here:
|
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Fiendish
USA (2,541 posts) Bio
Global Moderator |
| Date
| Reply #2 on Thu 21 Dec 2017 07:38 PM (UTC) |
| Message
| | An Aardwolf player reports that this has happened to him too just recently. Same description. |
https://github.com/fiendish/aardwolfclientpackage | | Top |
|
| Posted by
| Nick Gammon
Australia (23,165 posts) Bio
Forum Administrator |
| Date
| Reply #3 on Thu 21 Dec 2017 08:06 PM (UTC) |
| Message
| |
| Posted by
| Fiendish
USA (2,541 posts) Bio
Global Moderator |
| Date
| Reply #4 on Thu 21 Dec 2017 08:51 PM (UTC) |
| Message
| | 5.06-pre |
https://github.com/fiendish/aardwolfclientpackage | | Top |
|
| Posted by
| Fiendish
USA (2,541 posts) Bio
Global Moderator |
| Date
| Reply #5 on Thu 21 Dec 2017 09:01 PM (UTC) Amended on Thu 21 Dec 2017 09:23 PM (UTC) by Fiendish
|
| Message
| | The user reports that the echo print from a Send (as opposed to SendNoEcho) triggered on receipt of a GMCP message both color bleeds into the next output line from the server and also causes a trigger that should be hiding that next output to not fire. Did the change in 4.99 also apply to the echo from Send? |
https://github.com/fiendish/aardwolfclientpackage | | Top |
|
| Posted by
| Nick Gammon
Australia (23,165 posts) Bio
Forum Administrator |
| Date
| Reply #6 on Thu 21 Dec 2017 09:30 PM (UTC) |
| Message
| No it doesn't apply to using Send. The deferred sending is for "note" lines, not echoing of sent text.
I suggest the user does a SendNoEcho and also a ColourNote which will make the sent text appear at the appropriate moment. However it will be tagged as a "note" line and not a "sent" line. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.
26,824 views.
It is now over 60 days since the last post. This thread is closed.
Refresh page
![[Go to top]](/images/gototop.gif)
top
