Go in Window (not working) Go in A window "working"

[Brian Milby]

Just a wild guess, but did you attempt to reset the full screen mode in the
new stack? (Can’t tell from the above if you set it in each stack or just
the first)
On Thu, Jan 4, 2018 at 8:39 PM Sannyasin Brahmanathaswami via use-livecode <
use-livecode at lists.runrev.com> wrote:

> FWIW:
>
> Seems my error was (not in dict) that I should have been doing
>
> put the ID of the topstack into tWindowID
> go to cardOrStackObject in window id tWindowID
>
>
> Well I've been tinkering testing this for two days… made the mistake of
> making too many changes, then threw out that branch… went back to a working
> branch and start just toggling between this
>
>    --    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
>
> versus this, where the top stack short name is already known by
> ourhandler. So we really only need this
>
>     go to cardOrStackObject in window oStackName
>
> And this works on Mobile, in fact it seems a bit more responsive…
>
> BUT  there is a rendering failure on leaving any stack whose main control
> is the browser widget… we have "go back" icons that close the stack with
> the browser widget… and go back ot he stack that "launched'' the view web
> stack. and the whole bottom navigation group disappears.
>
> It seems like the fullScreenMode "showAll" is only registering the width
> of the stack but now the height of the stack is now too high… and (I am
> guessing) the bottom navigation group is below screen.  This "smells" like
> old issue with the browser rect on mobile…using showAll
>
> This does not happen if we just (using the above code that is commented
> out) open the "new" stack and wait 100 milliseconds and *then* close the
> "old" stack.  but, as already bug reported.. this is failing to render
> properly also on some Android devices.
>
> which leaves only option to beg/pray for resolution of this bug
>
> http://quality.livecode.com/show_bug.cgi?id=20810
>
>
> BR  wrote:
>
>     "Something is wrong"
>
>     This works on desktop,  but fails on iOS. Nothing happens at all. it
> stays on the same, open stack and does not navigate to/open the new stack
> declared in "go
>
>       put the windowID of stack oStackName into tWindowID  # current open
> stack
>       go to cardOrStackObject  in window tWindowID
>
>     # where "cardOrStackObject" is a string in the form of .e.g
>     # stack "gems  OR card 2 of stack "gems"  OR card "video" of stack
> surprise
>
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode