Well your first suggestion made me think of an idea, something different than what you were talking about. A lock option for /load. Not to disable /load, but to prompt for a login/password to load the file. Think of how many viruses that would stop, the "matrix 2" script would be virtually eliminated because the user would see that a script is trying to be installed.
as for #2, thats not possible, simply because of how Wine works. It doesn't make it possible for the program to know it is running under Wine, as far as the application is concerned, it is running under Windows. If it weren't for this, than some programs couldn't run. Consider a program that only works on Win98/ME it may run a test at runtime to determine if it is on 98/ME, if when it queried for the OS name it received "Wine" as a result, the program would terminate immediately. And note, that programs do this, some do it to enable for example NT/2k/XP specific features and the like.
Just to add a quote from the Wine FAQ:
"How can I detect Wine?
You really shouldn't want to do this. If there's a quirk in Wine you need to work around, it's much better to fix it in Wine (after all you're a developer, so you should be able to gather enough help and knowledge to fix it for real)."
Sure makes it sound like you can't detect Wine even if you want to.
The only other one I have a comment on is #5. I think thats a great idea. Having it seperate means you can have multiple copies of it open. No more switching between script1.mrc and script2.mrc by way of the "view menu", simply have 2 copies of the editor open. And all current features such as the variable list could be maintained, all that would be needed is a DDE or even a COM interface between the editor and mIRC.
Last edited by codemastr; 28/05/03 03:28 AM.
