Time-Stamping Demo programs #2

[Richmond]

On 04/23/2012 12:30 PM, Mark Schonewille wrote:
> Hi,
>
> Yes, it will.
>
> I would use a time limitation using a separate file together with a functional limitation, e.g. the inability to save documents. Actually, I rarely use time limitations for my own products, because I believe that every time a user starts up your software is a potential sale. I regularly get requests such as "please send me my license for Strõm Flow Chart Software quickly because I want to save my work" :-)

That is certainly a thought. Thanks.

>
> --
> 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 11:21, Richmond wrote:
>
>> 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.
>> And, I suppose storing a time-stamp in a custom property will, similarly, "evaporate" when a standalone is quitted?
>>
>
> _______________________________________________
> 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