Right. The splash stack actually becomes an executable when saved as a standalone. Executables by nature cannot be modified. This is one of the reasons a splash stack approach makes a lot of sense, because now all your attacked stacks/substacks CAN be modified (given they are in a location the OS allows it and the end user has write permissions to that location.)
Bob S > On Jan 16, 2019, at 11:50 , R.H. via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Windows: Regarding the many replies to the question of allowing saving a > stack file I would like to thank everybody for the answers by Matthias, > Bob, Alex, Jacqueline, JJS ... > > The problem was that a stack file used by a compiled splash stack does not > save on some client's computers with Windows systems >= 7 and can only be > run once leaving an unsaved file that is renamed with a tilde character. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
