Artifacts on screen from closed stacks on Android

[Sannyasin Brahmanathaswami]

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 across the entire screen, not be redrawn

This works on desktop, but there's a serious performance it..

   lock screen
   hide stack oStackName
   go to cardOrStackObject in window oStackName
   close stack oStackName
   show the topstack
   unlock screen

vs this which is relatively fast ( but leaves artifacts on android)

   go  cardOrStackObject  # e.g   go "gems" (or this string)  go card 3 of "gems"   
   wait 100 milliseconds with messages  
   close stack oStackName   
   wait 100 milliseconds with messages  

This is also very fast on desktop

   go to cardOrStackObject in window oStackName
           # would this possibly eliminate artifacts?
           # downside is user might see a "scary Picasso" briefly 
   hide stack oStackName  # hopeful the amazing abstract will go away?
   close stack oStackName

If it does not crash my pixel (because there are no waits) I'll do a beta test for Aravind to test on his Galaxy..

BR