Forums Feature Suggestions Connection id resetting

I'd like to see the ability to reset the cids to a numerical order or something:

Example:

You're connected to servers 1, 2 and 4, you type either /scid -h or /scon -h which changes the order so 4 becomes 3. e.g. 1, 2 and 3.

(-h being re'H'ash, I would have said -r but thats already an 'option')

That seems to defeat the point of having connection IDs in the first place - that they're unique for every connection made while mIRC is open. If you want a list of consecutive numbers to refer to your connections by use $scon(N). The only issue you could have to require this that I can think of is if you're doing some calculation with the connection IDs and you've gone over the limit that mIRC's numeric identifiers can handle (that'd take somewhere around 9 quadrillion connections I believe).

What would be the point of this?

If you want to access the CIDs in order then you can use $scon(n).

Infact, the entire point of CIDs is that they represent a specific connection for as long as that connection exists and that they do not change. As such, this change would break many multi-server scripts.

It gets so tiring to read those statements about features
being added/changed/removed breaking scripts .. so what?
Scripts are supposed to conform with mIRC, not the other
way around. Also scripting is supposed to be fun, so
updating a script to conform with a new version shouldn't
be looked at as a job but a hobby, something to do for fun,
or like in my case, relaxing. Otherwise maybe the script
author should consider not doing it anymore.

I too would like the ability to reorder connection ID's.

mIRC has a history of being very backwards compatible with respect to scripts. Many identifiers that have long been deprecated, still exist only for this reason. I would say that this is one of the factors that have contributed to mIRC being such a success: being forced to rewrite all your scripts everytime a new mIRC version is released, would quickly piss off lots of people.

Back on topic, I'm afraid that you and the OP have no clue what you're asking for. The Connection ID is an opaque, session-time persistent, unique identifier. The ability to change CIDs, completely breaks their very concept. There is absolutely no reason to want a "feature" like this, besides ignorance and/or laziness.

If it can't be done, it can't be done, although I don't believe
that for a second. I can live without it, notice I said " I too
would like the ability to reorder connections IDs", not
"I insist on the ability to reorder connection IDs". I
also do not believe that a feature should, or ever will
be left out just for sake of backward compatibility.

~ Edit ~
As far as being forced to rewrite all your scripts
everytime a new mIRC version is released, the ones
to get pissed are exactly the ones that should consider
not doing it anymore. I can't think of many (if any) new
versions that forced scripters to totally rewrite any script.

Who cares about whether this feature is backwards compatible or not? It wouldn't simply be backwards incompatible anyway, it'd be currently incompatible, ie. it would completely nullify the point of having connection IDs. I've yet to see anyone give an explanation as to why they want to be able to reorder connection IDs.

#1
I didn't bring up the backward compatibilty issue,
I only responded to it so step off.

#2
It wouldn't completely nullify anything, a (an?) unique
connection id to me means, no two connections ever
having identical connection id's, I can't see any problem
with reordering/re-assigning all connection id's. It
seems to me like you guys think he/we would like the
ability to change the id of an individual connection, that is
not the case, just to be able to reorder all current
connection id's. I really don't see how this would create
compatibily problems, and if it did, the true laziness would
be to complain about it rather than remedy it.

Connection IDs aren't simply a matter of no two connections having the same ID at the same time, if this is all you need then you can use $scon(n) as previously suggested. No, the point of a connection ID is that for as long as mIRC is open each connection's ID always remains the same. Connection IDs are used in multi-server-spanning scripts to uniquely identify what parameters/options/variables/whatever are attached to which connection. If the connection IDs are then all reset/reordered then those stored parameters/options/variables/whatever are all referring to the wrong connections. Seeing as this is the point of having connection IDs I simply can't understand why people are suggesting this 'feature', and from the looks of it, neither can you.

lol no I don't have a specific reason for wanting this feature
and no it's not absolutely necessary for it to be added, but
then is it necessary for any feature to be added? Of course
not. Like I stated in my reply to Sat, if it can't be done it can't
be done, no sweat off my back. I think my main reason for
even contributing to this thread was more to respond to the
this shouldn't be done because it will break a lot of scripts bs
than actually wanting this.

Personally, I think the people who want this feature are those who don't know entirely how the whole multi-server system works. I mean the cid's are there for a good reason, they're supposed to be unique and fixed, being able to change them defeats its entire purpose, and would mess up other scripts as they couldn't rely anymore on the fixedness of them. There's nothing that can't be done for multi-server scripting with the current implementation, all it takes is to learn how, being able to change the cid's isn't going to help with that.

(PS not directed at you)

It seems there a people who do not understand the reason for this feature and that it is just perfect for the reason it exists. I dont think this discussion would ever end.

Bringing it to the Final point: It will not change because it was added to mIRC doing what it does and absolutely NOT what was suggested here as this would break the reason to have a Connection ID at all and we couldnt do things as we can do now in scripts.

This Suggestion to Reorder the IDs could also be known as "Do scripting harder or better impossible please i dont like scripts at all kill any usefull features!"

I don't want an example of why this feature is necessary, simply a practical example/description of where it would useful, because I honestly can't think of a single one.

If you want to talk about whether "but it'll break old scripts" is a valid reason for saying something shouldn't be added then I'd suggest making a new thread in the relevant forum. As far as I'm concerned this thread is about the positives/negatives of the feature suggested, nothing else.

Yes, of course it's "bs" for me to not want to rewrite a large amount of my scripts because of the complete and unwarranted destruction of a very useful mIRC feature!

Spot the sarcasm.

This idea would completely destory the entire concept of Connection IDs, as previously stated. I want features added to mIRC that make it better, not features that make it worse.

There you go again acting like I'm the one that brought it
up, I did not, I only responded to it, had it not already been
brought up, it wouldn't have been there for me to respond.
I just think it's a stupid reason for not wanting something
added/changed.

~ Edit ~
This was a response to qwerty (below, 2nd to last post).

Quote:

Thank you qwerty, that was a great example of how
this change could break many scripting methods, I use this a
lot and similarly in custom windows, hash tables, variables,
timers, lots of different things. Too bad this example wasn't
given much earlier in the thread before the so called "flame war"
broke out. Well done, I stand corrected.

""
.

/

Gah. It's like talking to a brick wall. My point is that you just said you only started posting in this thread to talk about that, not the actual feature suggestion. If that's the case you should make a new thread about it in a different forum, because this is the feature suggestions forum, and this thread is about a specific feature suggestion. It's not here so we can all have a neverending debate about mIRC's backwards compatability policy.

Quote:

you should make a new thread about it in a different forum

ahhh but see, that wasn't necessary because it was
already introduced to the conversation in this thread.

That's enough.

Could everyone please read this thread.

mIRCManiac, it seems that wherever flame wars pop up, you're involved a lot of the time. If you insist on provoking others you shant be allowed to post, and this is not the first time such a point has been made perfectly clear to you - but it will be the last.

Thanks.

Regards,

Wow, it seems like you people change your personal
definition of the term 'flame war' to fit your needs in
whichever conversation you're currently involved.
I was not calling anyone any names, I was not
ridiculing anyone, I was not using any profanity aside
from my dictionary reference, and I was fine with the
removal of that reference. I was simply making my point(s)
just like every other post in this thread, yet somehow you
manage to single me out. Tell me, how exactly was I
flaming anyone?

~ Edit ~
btw, would you please look through my previous posts
and tell me the last time I was involved in any heated
debate .. it's been so long that I can't recall, yet
you talk as though it were yesterday.