Forums mIRC Help Bug mIRC 6.3 $cid?

Hi! I made a custom treebar using MDX and some docking-options. My problem is, it was working with $cid to recognize the server.
It seems that $cid is malfunctioning with mIRC 6.3.
If I use $cid on a server, it's telling me it's number 29!!! And I'm only connected to 4 servers, there are also only 4 status windows open.
So I was curious and tried: //echo -a $scid(1..25).$server
The results:
1: irc.4chat.be
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
15:
16:
17:
18:
19:
20:
21:
22:
23: irc.totov.ath.cx
24:
25:
26: irc.chattersweb.nl
27:
28:
29: nexus.ircworld.nl

You can see that the 4 servers are there, but with MUCH empty $server's
In mIRC 6.21 it wasn't, and I searched in the whatisnew.txt for updates, but I can't find something related to $cid.

Regards,


Miyako

CIDs are not supposed to be in any particular order - they are connection IDs. An ID is usually a unique identifier to identify something, hence the name ID.

Whilst the behaviour may have changed, connection IDs were never supposed to be in any particular order. To do what you want, use $scon() instead of $scid()

how can I return the active ID of $scon and what are all those empty ID's?

They're not empty. $scid() takes a connection ID as a parameter, and connection IDs are not in the order of 1, 2, 3, etc. $scon() however, does accept numbers in that order.. $scon(1) is the first server, $scon(2) the second, etc.

$cid is the active connection ID.

Hey Miyako ltns

$scid is a unique identifier each time you open a new status(server) window. $scon(N) is the collection of all the open scids so $scon(1) returns the first scid $scon(2) the 2nd and so on.

I know the difference between $scon and $scid, but my question to you: Why do I have 29 ID's while I have 4 server windows (connected or not) open That's why I think it's a bug.
I have to use $cid in my treebar because else I can't open the server windows which aren't connected.

I'll try to show you there is a bug, normally I can make a window in each cid, I suppose (because I don't have to be connected to make a @window).

If I try: /scid 29 /window -a @test I can see it, but if I try: /scid 28 /window -a @test the result is:
* No such connection id: 28

I neither opened 29 status windows and closed ID 28 (so it can't be that).

But OK, I have fixed it in my own script using $scon (now I can't activate windows on server windows which aren't connected, but OK).

You might use $activecid or $scon(N).cid

Correct, then I can return the ID's from the connected servers, but still I don't understand the 29 ID's while I opened 4 status windows Or is it randomly? XD

I think it's not "randomly" but better treat it like being random.
I suppose e.g. every new connection attempt increases the cid value (got a LOT failed reconnection attempts these days, and one recent connection had a cid value > 1000).

That could be possible, too lazy to count my reconnects. But in early versions it wasn't counting like this (I know because my treebar worked perfectly :P)

Btw, sorry.. I think I posted it in the wrong subforum, maybe it could be moved to bugs? (unless I'm wrong)

It's been reported and explained here

Haha, it explains a lot :P But it's annoying they changed the ID-counting-thing, too bad :P