[ANN] Release 8.2.0 DP-2

[Sannyasin Brahmanathaswami]

Panos

any hope for this big issue of acceleratedRendering breaking  a multi-stack app framework on Android which is currently holding our app "hostage" (cannot deploy on Android)

These are all, pretty much the same issue:

http://quality.livecode.com/show_bug.cgi?id=16736
http://quality.livecode.com/show_bug.cgi?id=19576
http://quality.livecode.com/show_bug.cgi?id=20287
http://quality.livecode.com/show_bug.cgi?id=20419
http://quality.livecode.com/show_bug.cgi?id=20539  # says unconfirmed but is basically same as all the above.

Any effort to toggle Accelerated Rendering of the top stack, (usually to false) then opening a second stack (setting it to true) etc… is causing Android to fail in various different ways. most notable symptoms being Stack A's controls still appear on screen even though the topstack is Stack B (easy to query by adding an answer dialog at the very end of the running handler 

put the short name of the topstack into iShouldBeVisibile
 answer ("The Top Stack is " & iShouldBeVisibile) with "OK"

At which point the app becomes completely unresponsive to any touch events. Though if stack B has a scroller you can see the mobile scroller indicator and it will go up and down as your finger swipes on controls for Stack A which was actually closed.

This is just one of a number bizarre symptoms, possibly related like having an image control set to a file reference A, then set to a new file reference B, artifacts from the first image A still appear on the left and right if the new image B is narrower than the first etc. even though theoretically, image A is no longer in the vRam? 

Setting AcceleratedRendering to false throughout all stacks and all handlers in the entire app, a last ditch desparate attempt to get it to work despite the horrific scrolling… (jerky)  also leads to other problems… 

I just got V1.0.2 approved on the AppStore, after begin up for 2 weeks… we were keeping quiet as we gathering more input from initial users…  fixed a few minor bugs and now we are going live with a big promotion for the iOS version today. Now we brace ourselves for Android users' cries in the days ahead "When for Droid?!"  I finally gave up trying to do anything via scripting, moving on to content dev for the next version.

 ??

BR

On 10/11/17, 5:35 AM, "use-livecode on behalf of panagiotis merakos via use-livecode" <use-livecode-bounces at lists.runrev.com on behalf of use-livecode at lists.runrev.com> wrote:

    This is a list from BugZilla
    
    http://quality.livecode.com/buglist.cgi?list_id=77472&query_format=advanced&target_milestone=9.0.0-dp-10&token=1507735851-88a1cd307824f6ceeefb2788f4b32c3a&order=bug_status%20DESC%2Cchangeddate%20DESC%2Cbug_id&query_based_on=
    
    And those are some open PRs in github on the main LiveCode repo:
    
    https://github.com/livecode/livecode/milestone/154