Forums Feature Suggestions .mrc file extension

Since .mrc seems to the most commonly used file extension in the scripting community, I think more support should be added for it in mIRC.

1. mIRC could register the filetype to open in remote when double clicked in explorer.
2. It could be the default filetype in mIRC (mIRC will load Script.mrc by default rather than Script.ini if there are no loaded scripts.)

I concur!, this also helps us scripters alot with releasing scripts.

you could liekly code this into the file type settings yourself. .MRC opens in notepad for me, thats the way i want it.

Thats not the point, the point is it opens for everyone in mIRC so that running scripts can be alot more easy for people new to mIRC.

It could be added as an option checked by default in the installer. "[x] Register .mrc filetype to open scripts"

I do like this idea, but wouldn't that mean that all .mrc files would automatically be loaded if it opened in remotes? I don't always want that when I open a .mrc file...could be dangerous. I have it open with notepad and have the extension use a mirc icon ... just because I can

Just repeating yourself doesnt mean much personally, (so now ill do it as well), why have the option when u can do it your self, and few users use scripts, so assigning a filetype is a bit of over kill, having it preselected as ON is way over kill. Mirc leaves little to no foot print on the PC, is designed to be portable between locations with in the pc, so how is mirc to assign a filetype to itself, is each mirc instance to TAKE the file type from the previous? if so u well never know what instance of mirc might run when u click on a .MRC file, and if not maybe the old instance no longer exists , as its really the new one moved to a different folder.

I don't think users moving a program from the default installation location is a good reason not to add a feature. That's pretty much a big nono anyway.

The reason I would like this feature?

1) Portability. Scripts will be easier to distribute and will need less documentation on how the run them.
2) Not everyone knows how to edit file assosciations in windows explorer and it's normally a pain if they do.
3) We'll have a nice mIRC icon assosciated with the .mrc filetype (again, I know you can set that in explorer.)

what do u mean the deafult mirc installation location, I just put the mirc.exe file into a folder and run it.

I mean the directory you told the installer to install mIRC to when you first downloaded and ran it.

point is, not everyone does that...

been ages since I last installed mIRC but I have changed OS installations since then.

you don't have to install mIRC to be able to run it, you can just as well copy the old dir to a new place.

you could add an option in mIRC to preserve file regs which it checks on boot to correct this problem though.

but like people said. if you have more then 1 mIRC on your computer they will be stealing eachothers file regs, and even more then 1 instance would be annoying.

@ cybercruiser:
you could always check with notepad anyways if you are not sure about the content. and the init warning would still apply (or an extra warning: are you sure you want to load this script or something)

Most programs come with installers nowadays and if you install a program improperly (by not running the installer) any problems you run into are your own fault. That is not even a reason to not include this suggestion imo.



How often do you change directories anyway? Do you sit at the pc dragging mIRC to various places across your disk? My point is that on the rare occasion you have a strong urge/need to move mIRC you could simply reinstall it. My mIRC has sat in c:\program files\mIRC\ for nearly 4 years now, despite switching pcs.



Good idea. It could say something like:

".mrc files are currently not assosciated with mIRC, would you like to register them?
[yes] [no]
[x] Do not ask me this again"



Does that surprise you? You could say the same about notepad, cmd, or countless other programs.

Anyway, why would they steal each others file registrations? You just make sure the installer option is unticked on one of the installations. This suggestion would work in a very similar way to the catcher options (making irc:// links open in mIRC.)

What extension would one use for Aliases and Popups (and Users/Variables, for that matter)?

Aliases and popups would be .mrc (since they are still scripts), users and variables would be .ini.

Would then remotes mrc files need to be number n(n)= like the other ini files are now?
Or is it better maybe to leave these other files as they are now and add *.mrc as a file type to say, open in notepad.

No. Only ini files have the N= part in them. mrc files would work the same way as they or any other plaintext file do now except it would be a registered file in windows and it would be the default file extension in mIRC.

I like the idea but usually when I am opening a .mrc file I'm opening to edit it, and it is very easy to simply open it thru notepad to edit. .-.

Yeah but theres more people that use scripts then there are people that want to look at the code, a View code button could easily be added in the initialisation dialog which asks if you want to load the script.

Hmm, not sure how well this would work really...

How would it know which instance of mirc to open the file in if there is more than one instance running?
Similarly how would it know which installation (or possibly non-isntalled (file copied)) to open the file in?
If it were possible to determine the exact installation of mirc to use, should it launch mirc performing any on start/auto connect options or should there be some sort of seperation between mirc and the scripts editor?

I agree mrc should be the default filetype extention used within the script editor rather than ini, but launching/opening a mrc file with mirc seems like it would be a messy implementation at best.

I agree, the .MRC extention is for a file to run in mirc, not to be run alone, i mean how much practicle use would it be to have mrec launch mirc and run the mrc file, assuming all the problems you clearly stated were resolved, then should also the new MRC now be loaded all the time for future executions of mirc or should it unload once the mirc session is over.