Time-Stamping Demo programs via substacks?

[Pierre Sahores]

Richmond,

The best way to go is to call the DAZE30 function from your standalone and compare it with a TSTAMP reference stored on the cloud so your customers won't find any local file to delete to get a way to bypass your 30 days try-period key.

HTH,

Le 23 avr. 2012 à 10:31, Richmond a écrit :

> 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?
> 
> or, put another way,
> 
> will the standalone save the time-stamp data in the substack?
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

--
Pierre Sahores
mobile : 06 03 95 77 70
www.sahores-conseil.com