MC vs Rev docs
I think I'm getting the hang of this. One reason I had wanted to work in the Rev IDE was because it appeared to have more listings in the Index docs. So I had thought that all those extra listings that were not in the MC docs, existed in the engine, but were not documented in MC. If I'm understanding this, then I am half right. The extra items exist, but as Rev handlers in the Rev IDE. It means that those things can be done within MC if you want to write the handlers or swipe the handlers from the Rev IDE. In other words, the MC Index docs are complete. They are not missing anything as I had originally thought (excepting some of the documentation to explain how the menu items work in Rev, such as the detailed info re the standalone builder... I already know how to do this in MC so I don't need the Rev docs unless I'm working in Rev...) So this reasoning for working with the Rev IDE just went blooey. I think I'll work in MC today :-) A side note... I noticed on the Rev list that folks are talking about the dontUseQT. My existing project sets that. The only platform that I've created a standalone for is Macintel. And it works there (as the folks said on the other list). I don't intend to put out a new Windows version at this time. Ain't broke... :-D But when I do, I sure hope this isn't a stumbling block! I had wanted to force MC to use the internal built in visual effects, as my own custom ones weren't working in my Windows test. So I let Mac have the ones I created, and Windows could use MC's built in ones. But it wasn't using them, so I set dontUseQT to force Windows to ignore QT and use MC's built in effects. Shari -- Gypsy King Software Mac and Windows shareware games http://www.gypsyware.com ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: MC vs Rev docs
Hi Shari, ... A side note... I noticed on the Rev list that folks are talking about the dontUseQT. My existing project sets that. The only platform that I've created a standalone for is Macintel. And it works there (as the folks said on the other list). I don't intend to put out a new Windows version at this time. Ain't broke... :-D But when I do, I sure hope this isn't a stumbling block! I had wanted to force MC to use the internal built in visual effects, as my own custom ones weren't working in my Windows test. So I let Mac have the ones I created, and Windows could use MC's built in ones. But it wasn't using them, so I set dontUseQT to force Windows to ignore QT and use MC's built in effects. you sure want to: ... set the dontuseQTEffects to true ## sic! ... instead of dontuseQT! :-) Shari -- Gypsy King Software Mac and Windows shareware games http://www.gypsyware.com Regards Klaus Major [EMAIL PROTECTED] http://www.major-k.de ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: MC vs Rev docs
Shari wrote: In other words, the MC Index docs are complete. They are not missing anything as I had originally thought (excepting some of the documentation to explain how the menu items work in Rev, such as the detailed info re the standalone builder... I already know how to do this in MC so I don't need the Rev docs unless I'm working in Rev...) That's partially true. The MC Language Reference contains all tokens supported by the engine as of engine v2.5. Since then another hundred or so tokens have been added. For the Rev v2.6 series a few of us got together and made an importer for the Rev Dictionary for use in MC -- you can get it in the Files section of MC's Home -- see mcTranscriptDict.mc.zip at: http://tech.groups.yahoo.com/group/MC_IDE/files/Extras/ We can't distribute RunRev's dictionary files for copyright reasons, but since every licensed MC user is also a licensed Rev user everyone already has a copy of the dictionary data on their hard drive anyway. So that utility is a shell for displaying the data, and includes its own importer (see the Help button) to import the thousands of tiny XML files that Rev uses. The import takes only a few seconds, and when it's done you have one tidy window to view all of the latest tokens. It's been working great for the last couple years, but with Rev v2.7 the format of the XML files has changed so we need to update the importer for the latest version. I've been so busy with client stuff and my own IDE that I haven't had time to update that importer. It would be ideal if someone in this community would be willing to act as owner of that stack, willing to update the importer and clean up the UI. Any takers? If not I'll get to it sooner or later, but I can't guarantee it'll be sooner. :) Also on my plate is DarksIDE, a one-click solution for downloading, installing, and setting up the MC IDE. This would obviate the need for FlipsIDE (also in the Files section at MC's home), which lets you conveniently flip between IDEs. The problem with FlipsIDE is that while it's convenient, it seems silly to wait for Rev to load just to run FlipsIDE to purge Rev to load MC. DarksIDE addresses this by making a completely separate installation for MC, in a way that is even more convenient. DarksIDE could also use an owner. It's not difficult to make, just tedious and time-consuming, and I have a lot of products on my plate right now cutting into my volunteer work. If someone wants to bring DarksIDE to completion I can forward notes and the beginnings of the UI I've concocted for it. Just drop me a note. So this reasoning for working with the Rev IDE just went blooey. I think I'll work in MC today :-) I'd say Have a great day, but it sounds like you're all set for that. :) -- Richard Gaskin Managing Editor, revJournal ___ Rev tips, tutorials and more: http://www.revJournal.com ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Script editor buttons
I miss the buttons at the bottom of the script editor window that allowed me to Save Script and Close Script with the click of one button. From what I can tell, now it is two moves. Apply, then Close, in a menu. No more buttons at the bottom. I've noticed it in both IDEs. Am I missing something simple? Shari -- Gypsy King Software Mac and Windows shareware games http://www.gypsyware.com ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: MC vs Rev docs
you sure want to: ... set the dontuseQTEffects to true ## sic! ... instead of dontuseQT! :-) Yes Klaus. I edited for brevity :-) Probably not the best idea in a forum that can be searched by people with questions :-) Shari -- Gypsy King Software Mac and Windows shareware games http://www.gypsyware.com ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: Script editor buttons
Hi Shari, I miss the buttons at the bottom of the script editor window that allowed me to Save Script and Close Script with the click of one button. From what I can tell, now it is two moves. Apply, then Close, in a menu. No more buttons at the bottom. I've noticed it in both IDEs. Am I missing something simple? you can still use the ENTER key as a shortcut for Apply and close in both IDEs Shari -- Gypsy King Software Mac and Windows shareware games http://www.gypsyware.com Regards Klaus Major [EMAIL PROTECTED] http://www.major-k.de ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: Script editor buttons
Klaus Major wrote: you can still use the ENTER key as a shortcut for Apply and close in both IDEs That's true in MC, but I thought that Rev's script editor required you to hit Enter twice in succession, no? I miss those buttons myself, so I've put them into my own script editor (available for MC users in devolution). -- Richard Gaskin Managing Editor, revJournal ___ Rev tips, tutorials and more: http://www.revJournal.com ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
script colorization
Did we settle on a final version of the script colorization algorithm? I didn't touch the one in MC because it seemed the alternatives discussed here were still in progress at the time, but if we can pick the final one it might be nice to fold it in. -- Richard Gaskin Managing Editor, revJournal ___ Rev tips, tutorials and more: http://www.revJournal.com ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: script colorization
Hi Richard, Did we settle on a final version of the script colorization algorithm? Dunno, I never use script colorization. I didn't touch the one in MC because it seemed the alternatives discussed here were still in progress at the time, but if we can pick the final one it might be nice to fold it in. -- Richard Gaskin Managing Editor, revJournal Best Klaus Major [EMAIL PROTECTED] http://www.major-k.de ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: script colorization
Dunno, I never use script colorization. I didn't touch the one in MC because it seemed the alternatives discussed here were still in progress at the time, but if we can pick the final one it might be nice to fold it in. -- Richard Gaskin Managing Editor, revJournal Best Klaus Major I don't colorize either. Shari -- Gypsy King Software Mac and Windows shareware games http://www.gypsyware.com ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: Script editor buttons
you can still use the ENTER key as a shortcut for Apply and close in both IDEs Nifty! Thanks! Shari -- Gypsy King Software Mac and Windows shareware games http://www.gypsyware.com ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
