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
➜ General
➜ 'omit from output' triggers slightly delayed
|
'omit from output' triggers slightly delayed
|
It is now over 60 days since the last post. This thread is closed.
Refresh page
Pages: 1
2
3
| Posted by
| Nick Gammon
Australia (23,173 posts) Bio
Forum Administrator |
| Date
| Reply #30 on Sat 12 Oct 2019 08:59 PM (UTC) Amended on Sat 12 Oct 2019 09:01 PM (UTC) by Nick Gammon
|
| Message
| |
| Posted by
| Alisa
(20 posts) Bio
|
| Date
| Reply #31 on Sun 13 Oct 2019 01:29 AM (UTC) |
| Message
| | I am heading home now and will take a look shortly after I arrive! I'll post back here once I get settled in for the night. | | Top |
|
| Posted by
| Nick Gammon
Australia (23,173 posts) Bio
Forum Administrator |
| Date
| Reply #32 on Sun 13 Oct 2019 04:39 AM (UTC) |
| Message
| | Just to be clear, the new version fixes the bug with Pueblo, but you still need the plugin if you want to combine multiple packets into one, to avoid the timing issue. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Alisa
(20 posts) Bio
|
| Date
| Reply #33 on Sun 13 Oct 2019 04:46 AM (UTC) |
| Message
| Good timing! I just settled into my office for the night and grabbed the latest 5.07-pre. At least I hope it is the latest! The upload showed that it was made almost three years ago but it was still somehow the most recent and specifically mentioned the MXP change, so I will assume the date is wonky.
As you said, I still noticed the odd timing on the omitted lines on the new version without the plugin. I've since added the plugin and reset everything, so now we play the waiting game.
On the plus side, yesterday's chaos with the < and > seem to be fixed! Channel names display fine, as do exit shortcuts. Now I will wait 20 or so minutes to see if any of the jerkiness still occurs and then make another post here. | | Top |
|
| Posted by
| Fiendish
USA (2,555 posts) Bio
Global Moderator |
| Date
| Reply #34 on Sun 13 Oct 2019 05:27 AM (UTC) |
| Message
|
Quote:
The upload showed that it was made almost three years ago but it was still somehow the most recent
Yeah that's just a quirk of reusing the same release tag over and over again. |
https://github.com/fiendish/aardwolfclientpackage | | Top |
|
| Posted by
| Alisa
(20 posts) Bio
|
| Date
| Reply #35 on Sun 13 Oct 2019 05:51 AM (UTC) |
| Message
| As an update, I am still watching. I think there is something amiss, as on two occasions during my dinner (while watching an idle MUSHclient window on the second monitor) a peculiar thing happened.
The displayed text hopped up a line as if something were appearing at the bottom but only a blank line appeared there, and when this happened the black 'MORE' flag appeared at the bottom of the client as if I were scrolled up and/or paused and not viewing the most recent text. Trying to scroll down at this time doesn't seem to do anything and the 'MORE' flag remains until something else finally comes through the pipe to be displayed so that I have something I can scroll down to and be 'caught up'.
I was delaying a bit before reporting this in the hopes of catching debug of the packets immediately prior to the quirk (it wasn't on at the time) but it hasn't happened since I enabled packet debug. Still watching though! | | Top |
|
| Posted by
| Nick Gammon
Australia (23,173 posts) Bio
Forum Administrator |
| Date
| Reply #36 on Sun 13 Oct 2019 07:40 AM (UTC) |
| Message
| What I am interested to know is: does the plugin largely (or almost completely) solve the original problem?
What you are describing sounds a bit odd - and possibly the code for displaying "MORE" is not totally working in conjunction with omitted lines. Possibly "MORE" is displayed and then with the line omitted it isn't taken away.
But without staring at the screen, looking for discrepancies, is the result satisfactory when just MUDding in general? |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Nick Gammon
Australia (23,173 posts) Bio
Forum Administrator |
| Date
| Reply #37 on Sun 13 Oct 2019 07:48 AM (UTC) |
| Message
| |
| Posted by
| Alisa
(20 posts) Bio
|
| Date
| Reply #38 on Wed 16 Oct 2019 12:48 PM (UTC) |
| Message
|
Nick Gammon said:
What I am interested to know is: does the plugin largely (or almost completely) solve the original problem?
What you are describing sounds a bit odd - and possibly the code for displaying "MORE" is not totally working in conjunction with omitted lines. Possibly "MORE" is displayed and then with the line omitted it isn't taken away.
But without staring at the screen, looking for discrepancies, is the result satisfactory when just MUDding in general?
Hello again! I haven't had much time to MUSH these past several days but it does seem like the original issue has been resolved by the combination of the 5.07-prerelease and the plugin you wrote.
I still want to try examining packet debug for the other issue when I have more time though, as I think it might cause trouble in some situations. Whenever that blank line suddenly appears at the bottom of the output screen, it will go away and correct itself on its own if you leave it be for long enough.
On the other hand, if you were to try scrolling down or otherwise correct the output display, you end up with that 'MORE' scenario I described before. Once that happens, your output won't scroll down even if you have it set to automatically unpause on activity. It will freeze like that and not show any new output until A) there is something new to show and B) you manually scroll down to force this new output to display.
So it's far from a dealbreaker but it could cause trouble for those who might be waiting for new activity while watching TV or otherwise doing a thing to pass the time -- you could have 3000 lines of new activity, yet you won't see a thing until you manually punt the screen downward. Even if you're actively watching for activity, you will still have to tap page down from time to time until a new line arrives and the resulting scrolling down temporarily corrects the odd pausing behavior.
To be clear, this rarely seems to happen, maybe once or twice an hour. With such rarity, I should be able to reliably get some packet debug for whatever packets immediately preceded the issue, which will hopefully be enough to isolate the cause. Just a matter of my getting some good ol' lazy time soon! I'll post back here again once that happens and I have some mystical mumbo jumbo code sorcery to share.
Beyond that, thank you muchly for solving the original problem! It is soooooooo much nicer now, as I am usually doing some work on the primary monitor while MUSHclient sits open on the second monitor. No matter how hard I tried to train myself to ignore that second screen constantly jumping up and down, I never managed to do it and my focus was constantly being disturbed as a result, not to mention my motion sickness! Hopefully this means I can now get more work done without having to minimize MUSHclient again. | | 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.
112,714 views.
This is page 3, subject is 3 pages long: ![[Previous page]](/images/thin_prev.gif)
1
2
3
It is now over 60 days since the last post. This thread is closed.
Refresh page
![[Go to top]](/images/gototop.gif)
top