Claims of activity when there are none...

Like the subject says, MUSHClient will flash on the taskbar saying there's activity, and when I flip back over to check it, there's /no/ activity on /any/ of my MU*'s... I'm kinda compulsive about checking the activity when it's flashing, and it /really/ gets to be annoying after a while.. :) Right now I'm running Version 3.04 on my Windows 2000 Server system.. Suggestions? Pwease...?

Strange, I've never had this report before.

Do you have a trigger there that gags lines or something like that?

A new line that arrives would register as activity, even if it is subsequently discarded (I think).

*shakes his head* Nope.. No triggers to gag lines... Any other suggestions?

How many worlds do you have open? What version of MUSHclient are you using?

I usually have 5 to 7 worlds open and I'm running Version 3.04

No further suggestions for my problem?

I'll have to investigate the cirumstances where it flashes the "new activity" icon, however I thought it was when new input arrived.

I've seen this happen if you have activity, alt_tab to MushCLient, see thea ctivity, and alt-tab out again quickly, like, within a blink of the button. It'll either stick to blue, or continue blinking.
I forced this to happen only a few seconds ago, with version 3.12, the taskbar button stayed blue.

As far as I can see the only reason MUSHclient will flash the icon is if:

a) A world has new lines; and
b) That world has set the option to flash the icon

"New lines" means a non-zero number of lines shown in the "Activity List" (Shift+Ctrl+L) under the column "New".

Also these same conditions will cause the appropriate button to change colour in the "activity button bar".

Can you confirm that when the icon flashes, there are (or are not) "new" lines shown in the activity window? If you leave the activity window at the front (ie. the title bar is blue) then switching to MUSHclient will not cancel the figure, as the "new" count is only set back to zero when you actually activate the appropriate window.

Either of two things would cause this problem, and it would help to know which it was:

1. The number of "new lines" is erroneously shown as non-zero when it should be zero; or
2. The icon flashes even if there are no new lines.

I've had the same thing happen. It occurs if you alt-tab to Mushclient and then quickly (Read ~1 sec or less) alt-tab back away.

Well... When I have the MUSHClient window minimized it's either always blue, always flashing blue, or always just normal even when there is activity.. What Tox and Cip say is true about the flipping in to MC and right back out real quick causing it to falsely flash.. I can assure you that there are no new lines of input to cause it to flash.. It's just annoying that it won't tell me when there's activity when I'm out of the window... Again, this is on Win2K Both Professional and Advanced Server, and I am now using the latest 3.15, (As of 7-17-2001)

I suspect that the FlashWindow operating system calls works differently in Windows 2000.

All I can suggest is to instead play a quick sound when there is new activity. On the "Sounds" configuration tab you can set it to play a sound on new activity.

I think it's something to do with the titlebar being "MUSHclient (Registered to Username) - [Mud Name]" while active in the program, and when you minimize it's "MUSHclient - [Mud Name]"..
Seems a bit unnecessary to put (Registered to Username) in the titlebar when active.. maybe that's just me.

Nick, you look into this at all?
Maybe win2000 handles title bar changes differently.

I'm monitoring this thread, however I don't have Win2000 installed at present, so I can't test it thoroughly.

Just a quick update.
It dosen't flash as it does when there is new activity.. it just fills with a solid color until you activate that window.

I'm very certain it does this in Windows 2000 because of the title bar changes (detailed in my previous message).

I know there is a different operating system call for flashing the title in Windows 2000, but I haven't used it because a lot of people will still use Windows 95/98/NT/ME.

Hmm, do you have worlds closed? I just submitted a RF because, on the activity bar, you cannot distinguish "closed, no activity" and "closed, activity (which causes the bar to flash)".

How do you get activity on a closed world anyway?

I also have been experiencing this on Windows 2000. I don't even have "New activity flashes taskbar icon" turned on, and as others have said, it happens when I alt-tab into MUSHclient, and within a second or so, alt-tab back out. It also works by clicking/clicking off in the taskbar itself.

For me, the taskbar icon stays blue permanently until I go back into MUSHclient. This happens whether there has been activity or not. I would have assumed by turning "New activity flashes taskbar icon" off, no blinking would have been possible at ALL(?)

Dave

This is a fairly well known bug (feature) of 2000. They changed the way it works some how and a lot of programs that use that feature tend to blink when nothing is happening. Either ignore it or turn it off. Either way, it won't work right on 2000, as I have been informed by a large number of people. ;)

That's just the problem. It WON'T turn off. :/

Can't you turn off the "flash the taskbar icon" option on the Output configuration?

Assuming you mean "New activity flashes taskbar icon" in Appearance|Output (alt+5), yes it is turned off, but the problem persists.

Pesky thing. That shouldn't happen then. :)

This problem occurs in WinXP as well... I've found that of you take your time when switching windows it does not occur... Also if you minimize the program it shouldn't claim that there is activity... Its still rather frustrating that you can't quickly switch windows without it making false claims... I'm currently running the latest version of MUSHClient...

Szereck

I too have been having this same problem with MUSHclient + Windows 2000.

MUSHclient will flash the taskbar for me even though I've explicitly set this option off for all worlds.

Ah, OK, I see what is happening here.

Contrary to the documentation, which is a bit vague anyway, some code is possibly flashing the icon when MUSHclient becomes active.

See bug #456.

However on my reading of the code, it should only happen when the world becomes active, but I will change it so that the FlashWindow function is only called if it is explicitly needed.

Just a follow-up to this thread. It's now April 2002, and I can attest to this bug *still existing*. I use Windows XP.

I only use mushclient for one MUD, and believe me, there is *no* activity.

The easiest way to test this is to simply click on the "MUSHclient" entry in the title bar while the application is maximized (which will in turn minimize the application).

It seems to me that the application "randomly" sets activity in the taskbar. If you click the "MUSHclient" title bar entry over and over, after a few times it will stop flashing (until you minimize it again ;-) ).

This quite possibly has something to do with the fact that when you click on the title bar, randomly the actual *title itself* changes. In my case, the title bar seems to flip between the title "MUSHclient" and "MUSHclient (Registered to <my name> - [World I am in]".

This should definitely get fixed sometime soon, being as I just coughed up $20.00 for this thing. zMUD is just bloated, plain and simple.

Whoa. For some reason the entire thread wasn't shown (otherwise I wouldn't have posted what I did). Geez, don't I feel like a sod. :-)

Threads are broken into pages and this is a long one. :)

I can see it is time for a new version of MUSHclient, if only to fix this bug. :)