I think I want to have Mark's baby.
On Wed, May 3, 2017 at 2:38 PM, J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 5/3/17 6:00 AM, Mark Waddingham via use-livecode wrote:
>
>> On 2017-04-30 23:52, J. Landman Gay via use-livecode wrote:
>>
>>> I have been wanting to
On 5/3/17 6:00 AM, Mark Waddingham via use-livecode wrote:
On 2017-04-30 23:52, J. Landman Gay via use-livecode wrote:
I have been wanting to know that for years. I have the general idea
but I want to know exactly what each command or property does. How
does layerMode interact with rendering
On 2017-05-03 14:07, hh via use-livecode wrote:
Thanks for that, this was very enlightening (should be, once
again, attached to the Dictionary).
If I understand correctly, it explains why testing for speed
has reliable results only on _physical_ mobile devices.
And, while in physical desktop
Thanks for that, this was very enlightening (should be, once
again, attached to the Dictionary).
If I understand correctly, it explains why testing for speed
has reliable results only on _physical_ mobile devices.
And, while in physical desktop environments a stack/ an app may
run correctly,
On 2017-04-30 23:52, J. Landman Gay via use-livecode wrote:
I have been wanting to know that for years. I have the general idea
but I want to know exactly what each command or property does. How
does layerMode interact with rendering and when should I set it? (I
used it incorrectly and submitted
Layering was definitely broken, that's for sure. But in this case we're
referring to the layermode of a draggable object. I haven't worked much
with his latest version yet, when I was doing it I was using fields instead
of images. But since the images are created on the fly from within LC I
My mistake was resetting the layermode after a drop. It does have to be set
after object creation but that should be the only time it's messed with.
Dragging was too jerky without acceleratedRendering, so I think that has to
remain.
--
Jacqueline Landman Gay |
Did you already try the following?
Layer mode:
Use 8.1.4. Before that and in 9-dp6 exact layering is broken.
The combination:
set the acceleratedRendering to false
set the paintcompression to RLE
set the alwaysbuffer of to true
___
use-livecode
Never mind
Jacque
you already have this in our script
[snip] set the borderwidth of the last image to "4"
set the topcolor of the last image to tRGB
set the layermode of the last image to "dynamic" -- jg: required for
smooth movment on slower devices
end repeat
and we
Jacque
thanks for the detailed query, or rather the detailed outline of the Shadows of
the Unknown World of Rendering.
appropo the puzzle app/module we have in our new app, which is pretty much
failing on Android completely.
@ the rest of you:
we get a quote from a dbase,
take snapshots of
On 4/29/17 9:56 PM, Sannyasin Brahmanathaswami via use-livecode wrote:
My question is: where is the documentation for AcceleratedRendering
-- exactly what does it do? (don't worry, if the explanation is very
technical.. .let me see it!)
-- when does it help
-- what contexts may there be where
Our new modular app was crashing badly and also rendering bizarre screens on
Android, HQ determined that if Accelerated rendering was on when you close one
stack and opened a second one, it was the problem. But Acceleratedrendering is
needed for performance, so it seems to work fine,if, instead
12 matches
Mail list logo
