mIRC Home    About    Download    Register    News    Help

Print Thread
Page 2 of 2 1 2
#61770 26/11/03 08:56 PM
Joined: Dec 2002
Posts: 2,962
S
Hoopy frood
Offline
Hoopy frood
S
Joined: Dec 2002
Posts: 2,962
I can't think of a single thing that I had to change in any of my script files when changing from 6.0x to 6.1x. Not a single thing. I'd honestly like to know just what you were using that means every dialog and line of code in your script must be rewritten, the only thing I can think of is that you use /setlayer about 10,000 times in your script because that's pretty much all that was really changed from the existing 6.03 commands and identifiers. As Naru has already said, if people don't register that's their own fault, you make it sound unreasonable that Khaled should expect payment for his work and that you should do everything you can to help them break the law by maintaining your script for 6.03 alone.

We've already been through this several times before but... very little of the mIRC GUI has changed, about 3 or 4 toolbar icons and some tiny changes in the Options dialog. Yes, I can see why that would be a minor inconvenience for people who use their own toolbar images, but it would take maybe a couple of hours to make a few new 16x16 icons. Beyond that, if you find the changes in mIRC's GUI to be that mind-blowingly difficult to come to terms with I can only imagine what will happen when the next version of Windows comes out with crayola-matic GUI.


Spelling mistakes, grammatical errors, and stupid comments are intentional.
#61771 27/11/03 12:12 AM
Joined: Jun 2003
Posts: 195
N
Vogon poet
Offline
Vogon poet
N
Joined: Jun 2003
Posts: 195
another thing about the UI. Altho the option dialog changed I dont see where thats such a big deal. Most scripts ive seen have thier own auto join favorites setup dialog thingies anyway. I almost never use it i just type /server and /join.

what happens when 7.something is released and we now have all the nifty dialog controls such as listviews and toolbars or for is added etc.. will you complain about making a 6.03 version with them as well? How about when were up to build 22.1 should khaled maintain a new 6.03 for every build he puts out?

I think the better solution would be to make a request to put back the options dialog the way it was if that is indeed what troubles you so much. I wouldnt halt progress based on a version reply or some dcc exploit. DCC imo is a waste of space. If you have a legitimate purpose for swapping files theres literaly a plethera of methods to choose from. DCC is most handy when you want to shell out illegal files to just anyone who can type /ctcp blah some lame trigger here. If its the exploit that troubles you dont use dcc it can be ignored. If its the size of the scripts that bother you script your own.

I can see a reason for _altering_ the version reply as ive said some channels dissalow 6.03 because of the exploit maybe allowing the version ctcp event to _append_ something wouldnt be such a bad idea but I as well as many others feel that removing it entirely would be ethically challenged to say the least.


Have Fun smile
#61772 27/11/03 08:02 PM
Joined: Feb 2003
Posts: 3,432
S
Hoopy frood
Offline
Hoopy frood
S
Joined: Feb 2003
Posts: 3,432
Quote:

A year to fix it? You could write an entire full featured script, delete it,do it again 6 times in a year. Ive seen large scale applications go from a twinkle to a beta in than time.

I didnt say it would take me a year to fix it.. but my example was that it took Khaled a yer to fix these bug fixes and other changes to mirc, and if i look at it i think it took a bit long time.. so if i would rewrite everything that arent compatible in my script, then i had to work allo, and i dont know how much i have to reewrite, but if i would do that, then i had to beta test every feture in my script.. and then fix the ones that dont work, i cant say that i would know every bit of code in my head, and that means that i cant say "ahh, i have to fix this and that".. i have to look over every single line of code and test it with the latest version of mirc, i also have to rewrite everything that dont work with the new version, and as you have seen in these forums it have been reported many bugs in the new exe file that didnt exist in the old ones, and i also have seen many reports about people using a script, then asking whi this or that dont work with the latest mirc.
PS: i rewrote my script and was done with it 3 days befor the new mirc was relesed.. and i dont have time to start all over again.. and i belive that many script's will be using 6.03 for a while longer.. but time will tell..


if ($me != tired) { return } | else { echo -a Get a pot of coffee now $+($me,.) }
#61773 27/11/03 08:34 PM
Joined: Dec 2002
Posts: 2,962
S
Hoopy frood
Offline
Hoopy frood
S
Joined: Dec 2002
Posts: 2,962
Very little, if any, of the scripting language as it was in 6.03 has changed to the point that it breaks in 6.12. $submenu was broken in a previous 6.1x release and then fixed again in 6.12. Unless you use DLLs your script will probably run fine without any changes whatsoever. And even if you do use DLLs there's probably a new version for them out by now so your actual script probably won't need changing anyway.

Your reasons for not upgrading don't make sense - yes you'll have to test your script again, but you have to do that for every new version - it's not like 6.12 is some magical version which breaks scripts whereas no other update has ever done so. Do you think that anytime someone releases a script of addon they should demand that mIRC never change from that moment because it might break their script?


Spelling mistakes, grammatical errors, and stupid comments are intentional.
#61774 27/11/03 09:18 PM
Joined: Feb 2003
Posts: 3,432
S
Hoopy frood
Offline
Hoopy frood
S
Joined: Feb 2003
Posts: 3,432
I use 8 DLL's so far.. and i wouldent be supriced if i add a fev more wink


if ($me != tired) { return } | else { echo -a Get a pot of coffee now $+($me,.) }
#61775 27/11/03 09:44 PM
Joined: Apr 2003
Posts: 85
K
Babel fish
Offline
Babel fish
K
Joined: Apr 2003
Posts: 85
"and i dont want any new mirc user to see that anoying screen popup every time they start mirc and that they should register, you have 1 month free "test period""

The only way a user would see this pop-up is if they have yet to purchase mIRC. That is between Khaled and that user and it has absolutely nothing to do with you or your script.

I also have been using my script for almost as long as mIRC has been around .. and everything still works, with the exception of the few things that have been dropped. ie $parm and $1*


--

katsklaw
Rather experienced Admin
Rather experienced mIRC Scripter
Amateur C Coder
#61776 27/11/03 09:55 PM
Joined: Feb 2003
Posts: 3,432
S
Hoopy frood
Offline
Hoopy frood
S
Joined: Feb 2003
Posts: 3,432
If you are a new mirc user, then that screen will make you drop mirc, and that wouldent be so good, as i said, that popup screen makes people mad, they have to close it every time they start mirc.. and if you have 1 month to test somthing, then you shouldent have to see that stuff popup every time u restart the porgram, i havent seen any programs with the same fetures that dont have a "disable" on it, and when your 30 days is up, then you get the popup without the option to disable it.. and i must say the old way was much bether.. you didnt have to see it every day.. and i dont think less people registered mirc then.. now it makes people scared that if they dont pay, then mirc wont work after 30 day, and yes. i know that have been explained here on this site, but people dont read old posts, they dont bother open the readme file or somthing like it, they want to install then run the program, same with mirc and all the script out there, they wont spend 1h trying to understand the help.. and i can say i do the same if i can.. if i need to, then i read the help.. but often i just skip it smile


if ($me != tired) { return } | else { echo -a Get a pot of coffee now $+($me,.) }
#61777 27/11/03 09:59 PM
Joined: Apr 2003
Posts: 85
K
Babel fish
Offline
Babel fish
K
Joined: Apr 2003
Posts: 85
Then they should pay for what they use ... NOT paying violates the user agreement .. again, not your problem.


--

katsklaw
Rather experienced Admin
Rather experienced mIRC Scripter
Amateur C Coder
#61778 27/11/03 11:43 PM
Joined: Jan 2003
Posts: 1,063
D
Hoopy frood
Offline
Hoopy frood
D
Joined: Jan 2003
Posts: 1,063
I know ALOT of shareware programs that uses a splash screen with every startup of the program during the trial period...

some of them don't even have the ability to click on OK, but you just have to wait for them to disappear for the program to start...

why bother with it?

just click it away and be done with it


If it ain't broken, don't fix it!
Page 2 of 2 1 2

Link Copied to Clipboard