Re: Go in Window (not working) Go in A window "working"
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@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@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Go in Window (not working) Go in A window "working"
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@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Go in Window (not working) Go in A window "working"
"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 Since I had made other changes since my last commit… I did commented out my new lines and used the old method and ran the stand alone again and it works -- put the windowID of stack oStackName into tWindowID # current open stack 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 --go to cardOrStackObject in window tWindowID # where we open the other, new stack first and *then* close the old one. On 1/2/18, 10:31 PM, "use-livecode on behalf of Mark Waddingham via use-livecode" wrote: On 2018-01-03 05:55, Sannyasin Brahmanathaswami via use-livecode wrote: >Hmmm >how simple. >go stack in window tID >needs to be added to the dictionary… as an example… >I did read the entry text description of the Window param, but missed >it, still.. >lets see if this helps on Android. You don't need to indirect through the 'windowId'. You can do: go stack "NewStack" in window "OldStack" i.e. 'window' can either be a stack name, or 'the windowId' of an existing stack. Warmest Regards, Mark. P.S. If you could file a bug about the dictionary deficiency, that would be great! -- Mark ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Go in Window (not working) Go in A window "working"
On 2018-01-03 05:55, Sannyasin Brahmanathaswami via use-livecode wrote: Hmmm how simple. go stack in window tID needs to be added to the dictionary… as an example… I did read the entry text description of the Window param, but missed it, still.. lets see if this helps on Android. You don't need to indirect through the 'windowId'. You can do: go stack "NewStack" in window "OldStack" i.e. 'window' can either be a stack name, or 'the windowId' of an existing stack. Warmest Regards, Mark. P.S. If you could file a bug about the dictionary deficiency, that would be great! -- Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ LiveCode: Everyone can create apps ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Go in Window (not working) Go in A window "working"
Hmmm how simple. go stack in window tID needs to be added to the dictionary… as an example… I did read the entry text description of the Window param, but missed it, still.. lets see if this helps on Android. BR ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Go in Window (not working) Go in A window "working"
On 1/1/18 9:48 PM, Sannyasin Brahmanathaswami via use-livecode wrote: but this fails in a backscript put ("stack " & quote & gems & quote) into tDestination; go to tDestination in window It needs a specific reference, not just the word "window": put the windowID of this stack into tID go stack in window tID -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Go in Window (not working) Go in A window "working"
On 01/01/2018 07:48 PM, Sannyasin Brahmanathaswami via use-livecode wrote: Mark recommends using "go in window" on Mobile, saying this closes stack A while going to open stack B This works on desktop put ("stack " & quote & gems & quote) into tDestination go tDestination # but stack A remains open. but this fails in a backscript put ("stack " & quote & gems & quote) into tDestination; go to tDestination in window Script error, though the dictionary seems to indicate this is correct syntax. Well, the dictionary leaves a bit to the imagination. It also says Name: window Description: The name or windowID property of any open stack. If a window is specified, the stack opens in that window, replacing the stack that was previously displayed in that window. So I believe what you want (untested) is something more like go to tDestination in or go to tDestination in -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Go in Window (not working) Go in A window "working"
Mark recommends using "go in window" on Mobile, saying this closes stack A while going to open stack B This works on desktop put ("stack " & quote & gems & quote) into tDestination go tDestination # but stack A remains open. but this fails in a backscript put ("stack " & quote & gems & quote) into tDestination; go to tDestination in window Script error, though the dictionary seems to indicate this is correct syntax. so that I test in the msg box…and also passing by ref which we need to do. the problem is not using "a" put ("stack " & quote & gems & quote) into tDestination; go tDestination in window # fails put ("stack " & quote & gems & quote) into tDestination; go tDestination in a window # works But stack A is still open…(on desktop) thinking it was because this was being called from a library, text only script (which has no window) I created a button the top of the main stack on mouseup go to stack "gems" in window end mouseup # also fails on mouseup go to stack "gems" in a window # this worked…but stack A remains open on desktop end mouseup but doesn't this entry indicate "a" is optional? go [invisible] [to] card [of stack] [{as mode |in [a] new window|in window}] and in any case. the firs stack stays open so the goal of only keeping one stack in memory is "defeated" either way.. so … back to 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 Any clues to using Go in window to close stack 1 and open stack 2? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode