Artifacts on screen from closed stacks on Android

[Sannyasin Brahmanathaswami]

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/destroyWindow (what's the difference?) are set to true

c) Stack "surprise" opens to card 3 which has a background texture with an image overlayed… only the image object from what is now the "topstack"  is rendered. The rest of the card is not.

similar case here where stack "gems" was closed and stack "Surprise" is opened but only the image object on the card renders while the entirely of the card of the close stack remains on screen in the background.

http://wiki.hindu.org/uploads/20171227_095851.jpg


 

On 1/29/18, 5:54 AM, "use-livecode on behalf of Bob Sneidar via use-livecode" <use-livecode-bounces at lists.runrev.com on behalf of use-livecode at lists.runrev.com> wrote:

    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 <use-livecode at lists.runrev.com> wrote:
    >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 that extends beyond the card width. So I'd try hiding that image on closestack and showing it on preopenstack.