Forums Bug Reports Connection ID.. broken?

I've been using "scid 1 blah", "scid 2 blah", etc for doing various startup commands, and now I see the $cid's are all over the place.

Is this is a bug, or am I not trying hard enough? I can't seem to figure out how to get the $CID of the second and third open server windows, but I thought thats exactly what $cid was for..

Connection IDs are unique identifiers for the connection, they are not supposed to be in a particular order.

What you're after is possible with $scon() though:

//echo -a First CID: $scon(1).cid | echo -a Second CID: $scon(2).cid

I think they are. (Same with window ids.)

My currently layout is:

They're not broken *sigh*



/scon is used for doing what the OP thought /scid was for. /scon takes a connection NUMBER, /scid takes a connection ID.

That clears things up completely. I've actually learned a few things about the Connection ID's from this thread that may help clear some other confusion I have in some script.

Thanks!

How're they not broken?

Look.

Because the connection ID was only ever supposed to be used to identify a connection. It was never stated that they must be in order. Even though the behaviour has changed from 6.21, that does not mean it has broken, because the connection ID was never supposed to indicate a connection number.

What's so hard to understand? Each connection is given a unique identifier so that you can identify that connection. This identifier is known as the connection ID, or CID. It does not have to increment with each connection, it just has to be unique. The same applies for window IDs. Even if they DO increment with each one, they do not have to; they just have to identify a window and be unique.

I don't get what you're trying to point out. That they're not in sequence? They're not meant to be. They're IDs, as in identifiers. They don't have to have any kind order or be sequential, the only defining characteristic is that they're unique for each instance of mIRC so that if you refer to a window by it's ID you will never get any other window.

My confusion was that they WERE in order.

I didn't realize I was misusing them. Seeing the differences in scon and scid, I can see how this is a very powerful distinction. I can also see others that are going to have the same problem with the change, even if it is a good move.

A note in the versions.txt would be nice.

It may not even be intentional, but possibly a side effect of another change. The point is that they don't have to be in any order as long as each id is unique. I fail to see why anyone would consider it broken. Different? Yes. Broken? Absolutely not.

I think what Grover is saying that many people mis-used the CID with the incorrect asumption that they were sequential.

What these people are going to see is that their scripts broke because of the change in behaviour, and consider it a bug.