I am trying to make my current project check for a new version. I followed the ANDOS MEDIA example using the SUPA SUPA DOWNLOAD OBJECT. Even the example seems to have problems running on my computer. Whenever it starts up I get one of those stupid windows submit problem messages.
I think it might be the object itself, but I also tried the FTP object and the same thing happened. When I removed these objects I no longer recieved the message. Any Ideas?
Are you making it check for another version through a save file or a constant program check? Either way, I just use an INI check.
When the program starts, create an INI file somewhere if there isn't already an INI file. Put in your version number somewhere in the file. If there already is a file, just check the version.
Simple as that. No need for complex extensions.
Disclaimer: Any sarcasm in my posts will not be mentioned as that would ruin the purpose. It is assumed that the reader is intelligent enough to tell the difference between what is sarcasm and what is not.
His question was "Any ideas?" and I gave my idea. If he's trying to make an online version of it, it's still not much different. But then again, I have absolutely no skill with pure Vitalize apps.
Disclaimer: Any sarcasm in my posts will not be mentioned as that would ruin the purpose. It is assumed that the reader is intelligent enough to tell the difference between what is sarcasm and what is not.
Illegal operation? Problem is, when you get one of those with an extension, it could be any single line in the extension's code causing the problem, so we can't really help without seeing the source (and even with the source it might be hard since the clickteam SDK is so iffy)
"Say you're hanging from a huge cliff at the top of mt. everest and a guy comes along and says he'll save you, and proceeds to throw religious pamphlets at you while simultaniously giving a sermon." - Dustin G
I made an example using MooSock which could download a file off the internet. I think its on the CT file archives.
The SDK is not iffy, if you had the extension source you could pinpoint the single command which crashed, view the call stack of function calls that lead to it, use MSVC++'s disassembly, etc. etc...
Yeah muz had the right awnser, just didnt notice the online part.
Just make sure that sombody cant edit the version number in there ini file, so that it will let them play online with old versions (Could cause serious weirdness) Like always keep an internal version number you cant change.
We are the music makers, we are the dreamers of dreams...
Advertisement
Post Reply
