mIRC Home    About    Download    Register    News    Help

Print Thread
#36128 13/07/03 04:37 PM
Joined: Dec 2002
Posts: 2,809
C
Hoopy frood
OP Offline
Hoopy frood
C
Joined: Dec 2002
Posts: 2,809
This is easy to reproduce, type:

/echo #main,#chat

Now, move the mouse over the "#chat" part of that, you'd expect to join #chat, however mIRC joins #main. The problem is obviously due to the comma. Imho, it should work one of two ways, either join both #main and #chat, or it should detect "is the mouse over #main or is it over #chat?" it shouldn't always join #main.

#36129 13/07/03 07:05 PM
Joined: Jan 2003
Posts: 73
R
Babel fish
Offline
Babel fish
R
Joined: Jan 2003
Posts: 73
Yep... I think mIRC should conform with how it handles other channel lists and only join the channel the mouse is over.

Of course adding a space makes it a non-issue. smile

#36130 13/07/03 10:36 PM
Joined: Dec 2002
Posts: 127
F
Vogon poet
Offline
Vogon poet
F
Joined: Dec 2002
Posts: 127
Quote:
Of course adding a space makes it a non-issue.


you can only (practically, not exclusively) add a space if you entered the string, as in codemastr's example. however, in a more realistic situation, when someone else typed that in a channel or query, you could not just insert a space, and therefore are relying on the way mirc handles the hotlink.


------
deep down, i'm really superficial.

Link Copied to Clipboard