On 04/23/2012 11:37 AM, Mark Schonewille wrote:
Hi Richmond,
Standalones can't write to themselves and thus your standalone can't save
anything in a substack. You can create a separate stack file in a different
folder, e.g. application data on Windows, Preferences on Mac OS X and the Home
folder on Linux and save time stamp in that stack file.
Blast! I am trying to find a way so that I don't have a file "floating
about" on somebody's system that they can just flush away to
reset the 30 day limit on my DEMO.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553
We will have room for new projects after 1 June. Contact me now and be first in
line.
On 23 apr 2012, at 10:32, Richmond wrote:
Um:
--30 Day code--
if the fld "STAMP" of stack "STAMP" is empty then
set the lockScreen to true
put the seconds into into fld "STAMP" of stack "STAMP"
save stack "STAMP"
set the lockScreen to false
end if
put the seconds into DAZE30
put fld "STAMP" of stack "STAMP" into TSTAMP
if DAZE30> (TSTAMP + 2592000) then
set the vis of img "TIME IS UP CHUM" to true
end if
--End 30 Day code--
This works very well in a stack (where stack "STAMP" is a substack of my
mainstack),
will it work in a standalone?
[NOT unless I remove that double 'into' . . . :) ]
or, put another way,
will the standalone save the time-stamp data in the substack?
_______________________________________________
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
_______________________________________________
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
