On 04/05/2016 15:01, dunb...@aol.com wrote:
There are not even enough letters in the alphabet to reach "10" (base 42).
I suppose you could use a subset of the base64 alphabet (treat uppercase
and lowercase letters as different values).
Peter
--
Dr Peter
On 5/4/2016 10:01 AM, dunb...@aol.com wrote:
> There are not even enough letters in the alphabet to reach "10" (base 42).
You are not considering Unicode in LC7 and 8 :-)
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this
There are not even enough letters in the alphabet to reach "10" (base 42).
-Original Message-
From: Mark Wieder
To: How to use LiveCode
Sent: Tue, May 3, 2016 9:56 pm
Subject: Re: Doing Maths in Hex
On 05/03/2016 11:53 AM,
> On May 4, 2016, at 8:48 AM, Kevin Miller wrote:
>
>> It also bears repeating that I have told Kevin, and others, that I think
>> there is not enough bang for the buck for the Business edition, so we
>> don't
>> buy it.
>
> That will be changing very fast now that 8 is
On 04/05/2016, 13:38, "use-livecode on behalf of Mike Kerner"
wrote:
>It also bears repeating that I have told Kevin, and others, that I think
>there is not enough bang for the buck for the Business edition, so we
On 04/05/2016 13:44, Mike Kerner wrote:
Anybody download the latest XC update, this morning? If so, can we use it
with the latest LC 6, 7, or 8?
Yes, it should work.
Please let us know if you run into any problems.
Peter
--
Dr Peter Brett
Anybody download the latest XC update, this morning? If so, can we use it
with the latest LC 6, 7, or 8?
--
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
and did a little
Exactly, Kevin, Monte,
The "priority bug fixes" is nothing more than a way for all of us to say
"me, first", and that is totally sensible and reasonable. How important is
that bug that you reported, vs. all the other bugs that are in the DB? Do
you really think that LC is going to hold some bug
Some time back on this email list there were discussions about tool(s)
to write a stack (mainstack, substacks, controls, images, and all their
standard and custom properties) out into a text file that could then be
run through another tool to recreate the stack exactly. I think I recall
that the
We can either prioritize bug fixes for the good of the user base as a
whole, or we can prioritize a bug that affects your project today. The
former we do automatically, the latter has a cost for us and a benefit for
you, thus the service. We¹ve had great feedback from our commercial
customers who
It's all getting too complicated...
On 4 May 2016 at 10:39, RM wrote:
> To this I would just like to point out that in my "other" email I have been
> offered the chance to PAY Livecode to fix THEIR bugs:
>
> https://livecode.com/services/priority-bug-fixes/
>
> That
To this I would just like to point out that in my "other" email I have been
offered the chance to PAY Livecode to fix THEIR bugs:
https://livecode.com/services/priority-bug-fixes/
That seems a bit odd.
Richmond.
On 4.05.2016 09:53, Terence Heaford wrote:
It seems to me as a “community” user
Thanks Richard! More questions (ideally of course you'd simply point me to the
guide I should have read to have answered these for myself)...
On 03/05/2016 23:24, Richard Gaskin wrote:
Ben Rubinstein wrote:
...is there anyway an explanation of the differences and
^anywhere, obviously
It seems to me as a “community” user that there is no community.
There only appears to be those that want to pay, those that can’t afford to pay
and those that don’t want to pay for ideological reasons.
I, personally do not feel part of a community.
When I read the discussions (not just this
Monte
> On 4 May 2016, at 13:20, Monte Goulding wrote:
>
>
>> On 4 May 2016, at 3:12 PM, Peter W A Wood wrote:
>>
>> I think that you have missed out one way to contribute that would be very
>> valuable to both the community and LiveCode. That is
101 - 115 of 115 matches
Mail list logo