I did not really understand if Kee want to be able to poke inside a standalone script or if he is not trying to.
Case A: Kee wants to pick his code from a standalone which was not protected with password: If the standalone is built with a engine before 4.0 then you can pick the scripts back using an HEX editor. If it is built with the newer engines, then I don't know. Case B: Kee wants to make sure people don't see his source code: Use modern engine and protect stacks with password. On Wed, Mar 17, 2010 at 10:33 AM, Richmond Mathewson < richmondmathew...@gmail.com> wrote: > On 17/03/2010 15:31, stephen barncard wrote: > >> Use the splash screen method and don't password protect the stacks. the >> first stack gets compiled into the app package with the standalone engine. >> The other stacks are editable. >> >> The making of splash screen apps has been covered previously. >> > > Umm . . . jolly helpful advice for the future; the problem, if I read > things right, is that Kee > neither did that or made a backup of the original stack. > > > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > -- http://www.andregarzia.com All We Do Is Code. _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution