Forums Feature Suggestions Notifies list capacity...

... is it possible to please extend the Notifies List Capacity to say, 500? (or ideally unlimited)

And perhaps provide the option to divide it into groups for easy management?

When you have contacts on several IRC networks, the contacts rapidly exceed the teeny 128 contact entries capacity, plus if your PC is shared, other users saving their contacts as well quickly exceed that 128 contact limit.

Im sure that this change is a simple change of an array capacity integer, so literally a few seconds work?

Thanks!

The IRC servers limit the notify list, and I wouldn't recommend sharing your mIRC installation with other people.
Install mIRC to a different directory for each person, e.g C:/Documents and Settings/Yourusername/mIRC, C:/Documents and Settings/Otherusername/mIRC.
I would agree that it would be easier to manage the lists if you could group them, for different servers, etc.

As mentioned, the 128 limit is due to the ircd watch list limit, which is 128 by default in most ircd configs.

I like the grouping suggestion, however rather than just any old named groups, i would like to see the ability to make watch/notify list network specific. This would essentially group them, and it would also expand the notify list limit to 128 (by default at least) for each network, instead of total.

Not sure if it does now or not, but mirc should allow you to add unlimited amount of users to its notify list (regardless of if they are assigned to a specific network, or not). It should then check for the watch limit in the 005 raw and send only that amount of watches to the network/server.

This of corse leads to another suggestion, sorting buttom (up/down) in the notify list to specify priority if needed. (so that if more entries exist than the server allows you have a little control over which will be sent) The notify window would of corse then also need to contain some sort of notification that not all were sent for that server

or, alternatively, send the entire list in sections that consist of the limit on each section until done.

Basically use the RAW 005 response in a similar manner to how some mass voice/de-voice scripts use $modespl

That would defeat the object of the WATCH system though, it'd be as primitive and inefficient as the ISON method which is exactly what it was designed to surpass. I don't think it's too unreasonable to expect mIRC to respect a server's WATCH limit, especially seeing as the lowest I've ever seen it is 128 entries, which is far more than anyone could ever honestly need to look out for (assuming the notify list is made network-specific).

I never said or even implied, that it was efficient as I know it's not. Personally I think the best idea is to have the WATCH system be network specific. If someone (for some reason) needed to WATCH for more nicks than what the server limits at, then a script could be written (and yes, I do realize the complications of writing a script like that, as I already have it).

Ummm the obvious solution is use the watchlist to it's capacity, use ison for additional nicks.

I really hate the notify list as is. Mainly, it's one ugly window. Why not use a sidebar in the server status window? But it should be on the left by default, cuz it would be awfully easy to mistake it for a channel window...

Ugh actually this gives me chills....

The problem with using ison for additional nicks, is the fact that ison only refers to a specific channel, not the network.

People that mentioned ison here were talking about the server command ISON, not the mirc /if operator.