The browser widget reports as being at 0,0, but clearly it isn’t (at least the visible contents is a long way from the top of the card). You work around that by having a script set the location too, then after that you have another browser position problem. If LiveCode was fixed so that the browser looks like it’s in the position that it claims to be, that might fix other position issues.
> On Jun 27, 2016, at 4:44 PM, Sannyasin Brahmanathaswami <[email protected]> > wrote: > > @ colin: Not sure I understand the action you suggest > > Are you saying, because the browser widget's location is set in the inspector > to 0,0,736,414 and loclocation is set to true.. that we should try not trying > to re-located it again by script? > > From: use-livecode <[email protected]> on behalf of Colin > Holgate <[email protected]> > > I don’t know if you tried it, but if you show the position of the browser > when you get to the card, it’s already 0,0. Until that symptom is fixed it > may confuse the other symptoms. > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
