LiveCode Forums.

I added a comment to an existing bug report I found. Maybe that will help.

https://quality.livecode.com/show_bug.cgi?id=17261

Sure looks like the right report to tack it on to

Started around 6.6.5, I wonder if you try a earlier version, say 6.5, if the issue goes away? Hmm.

Do you see a difference between Win7 and Win10? The issue superficially seems like it may be related to the tiling differences in the Windows compositor between the two version. Not that there's anything you can do about that, it would still require an update to the LC engine for Windows. But may provide useful guidance for the bug report if a difference can be seen between those two Windows versions.

Richard wrote:

Do you see a difference between Win7 and Win10?

I am on a Mac. And though I never fully understood if the "flattening", or truncation, was what actually was seen (the demo stack did not show it on Mac), there is distinct jerkiness on the Mac. This, er, renders "animation" poorly overall in LC.

This is one of the few instances where "jerkiness" can be ascribed to Macs.

Craig

Its been a few months since I posted this original question. I haven't seen any updates or developments on the bug report so I'm guessing this is not a priority or there's no workable solution? I can't believe I'm the only one in the world that sees this as a major flaw in LC? Is there no way to fix this ? I've scoured the forums looking for any solution to fix this clipping/distortion that is experienced when moving objects, but have been completely unsuccessful.

I might be hallucinating, but I have a strong (if possibly phantom) memory of seeing a suggestion/workaround to make the graphic/image have a transparent space around it (ie the image stays the same visible size, but the pixel dimensions of the overall picture are increased. Thereby any truncation should crop the invisible background, and leave your visual display intact.

I might be hallucinating

I wouldn't like to comment on that, but it is perfectly possible to prepare images with
a graphics program such as GIMP so that each one is surrounded by a "moat" set at,
let's say, 1% transparency:
- -

Or even 100% transparency. It's just a non-visible area that doesn't matter about being chewed up when the graphic is in motion.

Ok, but how would that be accomplished with a graphic object/drawing object vs. an image object? Basically, like on the sample stack, its just a round graphic object.

The advantage of using 1% transparency (possibly I mean 99% transparency and 1% opacity . . . it is
all a bit subjective), is that should one want to use intersect that may prove useful.

but how would that be accomplished with a graphic object/drawing object vs. an image object

presumably you mean something like an imported SVG image?

I, honestly cannot see why there should be any undue problem there.