1. Identity support should be implemented in mIRC. This will allow different users of one computer to create a username and password to access, change settings, and customize the mIRC GUI to their liking. Identity support sounds like a great option. I'd use it just to connect to servers with different info or to have a "backup" login or something. ie. I don't have other users who use mIRC on this computer, but this option would make it easy for me to have other options available to me besides the same ole same old login info every time.
3. This one has been suggested before and I just want to mention it once more. An identifier that will return $true if you're connected to the internet, and $false if you're not. There could be problems with detection for someone on a LAN, but it could always just simply try to ping mirc.com/209.240.130.48 and if it goes through, it assumes that it's connected to the internet. (I know this is sort of a round the bout way of doing it, but hey, if it works, it works, and if it doesn't work exactly correct in a million years when mirc.com/209.240.130.48 isn't around, then who cares?)
5. The mIRC Script Editor should be external rather than internal. Keep in mind that not every mIRC user scripts. If a user wants to script, then a seperate editor should be available to download from the mIRC website. This would reduce the size of the mIRC executable for those who don't script. I doubt it takes up much space, as it's pretty simple, but if it were a separate .exe file or something, it could perhaps have multiple spawns of itself.
I'd rather just have it so mIRC allows you to open up multiple editors within itself, let's you minimize them within mIRC (or to the taskbar if you have the editor set to it), and has a LOT more options for the editor! (ex: event driven macros to do stuff like auto-complete $whatever - even for custom aliases that I created myself to make scripting easier - the event driven macros could be coded into the same page you're editing, with the -l switch or without it to make them only work on that certain script you're editing, or work globally for any script you're editing)
-- edit (continuation of the event driven macro idea)
on *:TAB:{
; this is for when someone types "$whatever" then tab
echo this is the entire line that the cursor is on: $1-
echo this is how many characters over it is: $chrs
echo this is how many words over it is: $words
echo this is the word directly behind the cursor presently (whether there is a space or not): $word
; placecursor would put the cursor to the right place after the text has been changed (it goes from left to right from the beginning of the word, negative numbers would work)
placecursor $calc($chrs + 10)
; the 'return' simply replaces the word behind the cursor
return $ $+ whatever(filename,input,output)
}
Option two (it could have the $1-, $chrs, and $words identifiers as well, but for simplicity I left them out):
on *:type:whatever:{ placecursor 9 | return whatever(filename,input,output) }
When someone types '$whatever', This would auto-matically turn the 'whatever' to 'whatever(filename,input,output)' then place the cursor here: whatever(
filename,input,output)
