Unfortunately, it is worse than that… see these screenshots from the Galaxy A7
running Nougat
http://wiki.hindu.org/uploads/20171227_104835.jpg
The entire "portal" stack remains rendered in the background, in this case, on
card "home" even though
a) it was closed
b) destroyStack/destroyWind
I hide background images and then set the background fill of the card to that
image id. Not sure if that would help.
Bob S
> On Jan 28, 2018, at 19:06 , J. Landman Gay via use-livecode
> wrote:
>
> On 1/28/18 8:25 PM, Sannyasin Brahmanathaswami via use-livecode wrote:
>> BR: But we are talk
On 1/28/18 8:25 PM, Sannyasin Brahmanathaswami via use-livecode wrote:
BR: But we are talking about entire stacks… and the offending object wants to
disappear completely across the entire screen, not be redrawn
I think the problem in SivaSiva is the background image in most cases,
the one tha
J. Landman Gay wrote:
We really do need a "redraw card" command, but for now you
can force a redraw by either hiding and then showing the offending
object, or by resetting it.
BR: But we are talking about entire stacks… and the offending object wants to
disappear completely acros
On 1/28/18 2:04 PM, Sannyasin Brahmanathaswami via use-livecode wrote:
2) worst case scenario
Entire image map of Stack B is not fully rendered.. even get some bizarre tiles
or squares with odd colors or image data from Stack A, and only one area of
Stack B is rendered like some weird inlay or
On 1/28/18 2:04 PM, Sannyasin Brahmanathaswami via use-livecode wrote:
Entire image map of Stack B is not fully rendered.. even get some bizarre tiles
or squares with odd colors or image data from Stack A, and only one area of
Stack B is rendered like some weird inlay or overlay on top of the p
Have you tried a blank background image on stack B to explicitly overwrite
the buffer for areas outside of the stack? That may help problem 1 but
probably won’t help problem 2.
On Sun, Jan 28, 2018 at 2:05 PM Sannyasin Brahmanathaswami via use-livecode
wrote:
> We are getting reports (and screen
