Hi Joe, | Sure, just drag your file into your RB project. If RB doesn't | recognize it as a known file type (image, cursor, resource etc) then | it will simply include the contents of that file in your RB program | as a string. The String will have the same name as your file. | | At runtime you can use that string in a variety of ways including | writing it back out to a conventient location to use asn an external | file.
Wow, that's pretty nifty. I used to use Armadillo on the PC platform to help protect my app from up-to-no-good users that tried (and succeeded before Armadillo!) to crack it. I'm wondering if the method above would do a similar thing to help protect apps from cracking by: • writing your app as normal • when it's completed, drop it into a new empty app as a resource • call that new app your actual app and distribute it • then when users run your app, you extract the real app from within it to a temporary folder and run it • when you close the app, it deletes the temporary app and of course, the resource string could also be encrypted first etc. Just a thought. Anyone have any ideas on this? App cracking is a real issue (no pun intended) and I myself have been the victim of it in the past. All the best, Mark. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.3.2/293 - Release Date: 26/03/2006 _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
