On 2015-12-18 18:38, sa...@hrz.uni-kassel.de wrote:
There we have two different views on this problem from two members of
the Livecode team, and I am inclined to judge that Mark is fully right
here.
No, there are not two different views - mine was not a view, it was a
statement of fact which
On Mon, 14 Dec 2015 11:35:50 Mark Waddingham wrote
in response to Peter Brett:
On 2015-12-14 11:21, Peter TB Brett wrote:
Hi Wilhelm,
I find this newly installed monitoring process controlling the
validity
of older, but already fully installed versions an outright
Wilhelm Sanke wrote:
> I surely cannot afford the present Business license, but could live
> with a new Indy-license starting August 2016, provided the Indy
> license allows me to install Livecode - and different versions of it
> - more than one time on one or more computers.
Looks like section
Hi Wilhelm,
On 13/12/2015 18:15, sa...@hrz.uni-kassel.de wrote:
Intending to test performance developments between different LC versions
(on the Windows partition of the Mac Mini) - like I reported them
several times on the Livecode lists this year - I ran into a new
problem: Versions that had
Peter,
You wrote:
> I'm afraid that that's not correct -- when your current commercial
> license expires in August 2016, you will not be able to use any
> commercial version of LiveCode or use them to create standalones
> unless you renew your license.
This may be correct for 6.x and later,
On 2015-12-14 11:21, Peter TB Brett wrote:
Hi Wilhelm,
I find this newly installed monitoring process controlling the
validity
of older, but already fully installed versions an outright
unnnecessary
nuisance. Is this part of the new licensing policies that restrict the
use of LC-Indy