Frozenyam

Alright, excellent work. I'll have another crack at it.

Also... It doesn't seem to recognize my DVDs when I put them into my drive. Is there something I'm doing wrong? Maybe a codec you have that my system may not?

AutoIt Error Line 0 (File "C:\Program Files\DVD\Digital_Vision.exe") While $CursorInf(2) While $CursorInf^ ERROR Error: Subscript used with non-Array variable. Edit: I got an error running your script. It was fatal. I don't think it would have been a huge deal if the you had set the option to run scripts with an error being non-fatal.

Awesome job, it looks amazing. Is it actually in German though?

Yeah, that'll do nicely. Thanks a lot.

Just finally got around to checking out the editor. I was wondering if it will work with the latest betas? Other than that, all I have to say is that it looks awesome and that you should keep up the work.

Not a progress bar. A status bar... the little bar at the bottom of a window that shows you what going on. Like when you look at the bottom of your browser window to see if the page is still loading or whether it's done.

Beta 3.1.1.70: Anyone know if it is possible to create status bars yet? I checked for a GUI reference in the help file, and for a function reference too. I even checked if it was maybe added as a style/extended style for a window command. I didn't even see it as an option. So, I am just wonderig if the developers have added it yet, or if I still have to wait. The script I'm writing, I'm kind of waiting on the command for, as it will be of much use. Any useful answers will be of much help. Thanks in advance.

No. You'll need to ask the author for the source code.

I've looked at the feasability of making this code a function and have determined that there would just be far too many variables to reference. - The extension to register - The program to run/open/etc... the file with - The icon to be used (optional) - The persistent handler - The reference folders cited in the default extension folder. - And a few others. It would just be far too much work for me. So... if anyone wants to modify the code themselves, they can go right ahead and do so.

That GUID isn't a problem, but thanks for the concern.

Most of the other keys are to add the file extension to the to a menu. Specifically the one when you right-click the desktop and go down to "New" it will put the new file type in that meny so that you can create a new one without opening notepad or something and then saving it with that extension. You might have to wait for these additions as classes for me resume tomorrow morning and most of my days will be booked with class/work until weekends.

That's an ingenius idea! I could have it take the setting that you input and have it create a registry patch file. So when you're done executing the script all file extensions return to the way they were before you ran it. Hence it creates the keys only when you need them, and then removes them when you don't. That's the most brilliant idea I've read all day.

Yes I know it all follows a distinct pattern. I don't, however, want to give anyone just learning this language, and who has never programmed before, free reign to delete any key THEY feel they don't need. I know that the default key in the extension's folder that you're looking at contains the the folder to point to for instructions on how to deal with that extension... and yes I know that I could use that key as a pointer to delete the folder if need be, but I want to create something a little safer. I don't want to give them access to just type in a random extension and have it deleted. That's why I said I what I said.

Both create the same keys, however, I completely revamped the entire things and it got put as a new topic in the forum.