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
➜ Freezing problem
It is now over 60 days since the last post. This thread is closed.
Refresh page
Posted by
| Unregistered user
(72 posts) Bio
|
Date
| Mon 14 Aug 2000 (UTC) |
Message
| I've recently upgraded to version 3.00, followed shortly by 3.02 and have noticed a problem when connected to servers. Whenever a large batch of text is coming in, paragraphs, code text, whatnot, the client hangs for an extended amount of time and doesn't respond. After a little while it will unfreeze and continue on normally. When it does this, i cannot switch worlds, or do anything inside the client itself. Has anyone else experienced this problem? Is there an easy solution? 3.04 doesn't seem to have fixed this either. BTW, it didn't happen in any of the other versions below.
- Kaeru | Top |
|
Posted by
| Nick Gammon
Australia (23,133 posts) Bio
Forum Administrator |
Date
| Reply #1 on Tue 15 Aug 2000 (UTC) |
Message
| You have two wildcards like this:
*** At * on the muck, * connected. ***
*** At * on the muck, * disconnected. ***
I think that your problem is these triggers. The asterisk is a wildcard, and I would say that having three in a row is making the wildcard matching routine go into a bit of a spasm.
If you edit those triggers, you will see that the execution time is listed as 11 seconds, after only a couple of minutes on the MUCK. By comparison, other triggers which don't have consecutive wildcards have only taken 0.001 seconds to execute.
You need to "escape" the asterisks. You can do this with a regular expression, like this:
^\*\*\* At .* on the muck, .* connected. \*\*\*$
The "^" says "match on start of line".
The "\*" is an escaped asterisk (ie. match on the asterisk, don't treat it as a wildcard.
The ".*" is a genuine wildcard - it says match on any number of anything.
The "$" says "match on end of line".
Make sure you check "regular expression".
This should fix it.
|
- Nick Gammon
www.gammon.com.au, www.mushclient.com | Top |
|
Posted by
| Unregistered user
(72 posts) Bio
|
Date
| Reply #2 on Tue 15 Aug 2000 (UTC) |
Message
| Woohoo! Thanks for the info, I had no idea those two small triggers could cause so much lag-time on the program. Once I changed them over to the newly escaped ones it had no problems at all.
- Kaeru | Top |
|
Posted by
| Nick Gammon
Australia (23,133 posts) Bio
Forum Administrator |
Date
| Reply #3 on Sun 03 Sep 2000 (UTC) |
Message
| One more point. If you are planning to use the data "captured" by the wildcards as part of your trigger (to echo to the screen, or use in a script) then you should put them in parentheses, like this:
^\*\*\* At (.*) on the muck, (.*) connected. \*\*\*$
That way, the first wildcard becomes %1 in your reply, and the second wildcard becomes %2. |
- 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.
14,578 views.
It is now over 60 days since the last post. This thread is closed.
Refresh page
top