We can just send a man to mars. Same deal. :-)
Bob S
On Oct 6, 2020, at 6:08 PM, Richard Gaskin via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
So "just" changing from 32k to 64k isn't as easy as putting the word "just" in
front of it might make it seem. :)
ia use-livecode
Sent: Tuesday, October 06, 2020 2:50 PM
To: use-livecode at lists.runrev.com
Cc: Richard Gaskin
Subject: Re: Canvas Limited to 32767
Glad it's not the funky mobile field workaround. That's such a horrible
experience for developers that even the act of documenting it should have
been a
Services
rdim...@evergreeninfo.net
-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Richard Gaskin via use-livecode
Sent: Tuesday, October 06, 2020 2:50 PM
To: use-livecode@lists.runrev.com
Cc: Richard Gaskin
Subject: Re: Canvas Limited to 32767
To: use-livecode@lists.runrev.com
Cc: Paul Dupuis
Subject: Re: Canvas Limited to 32767
You would think with 32K px at 72px/inch being like 450 inches that the 32K
limit would not be an issue, but I have run into it as well
I have written a custom graph (like a bar graph for example sake
Glad it's not the funky mobile field workaround. That's such a horrible
experience for developers that even the act of documenting it should
have been a red flag to go back and refine the field buffering for the
few cases where that put-it-in-a-group recommendation is actually needed.
In
.com
Cc: Richard Gaskin
Subject: Re: Canvas Limited to 32767
Ralph DiMola wrote:
> I just ran head first into this. Could someone explain why other than >
moving from an int16 to an int32 this is such a challenge? This should >
have been addressed during the refactoring of the engine.
I
ard Gaskin
Subject: Re: Canvas Limited to 32767
Ralph DiMola wrote:
> I just ran head first into this. Could someone explain why other than >
moving from an int16 to an int32 this is such a challenge? This should >
have been addressed during the refactoring of the engine.
Is this f
Ralph DiMola wrote:
> I just ran head first into this. Could someone explain why other than
> moving from an int16 to an int32 this is such a challenge? This should
> have been addressed during the refactoring of the engine.
Is this for the weird recommended mobile workaround of putting a text
