This is long, so most of you will probably want to skip it.
On 9/1/19 6:48 AM, Mark Waddingham via use-livecode wrote:
Hmmm - you say 'on your Pixel' - have you observed the behavior on other
devices, or indeed other Pixels? (It might be worth creating a Pixel
emulator which will be in factory
On 2019-09-01 01:16, J. Landman Gay via use-livecode wrote:
Yes, I meant "launch url in widget" which says it opens a url in the
widget, but that is what "set the URL of widget x" does too. I don't
see any difference.
As Sean said the difference is the widget, rather than anything else.
The
Originally such things could be used to "redirect" urls.
But in the current browser widget this is not used and in fact there
is no difference between the two:
[ The LCB code is
public handler OnLaunchUrl(in pUrl as String)
setUrl(pUrl)
end handler ]
But I have meanwhile found a solution you
Yes, I meant "launch url in widget" which says it opens a url in the
widget, but that is what "set the URL of widget x" does too. I don't see
any difference.
I'm having a terrible time with both acceleratedRendering and the browser
widget in LC 9.5. I can't fix acceleratedRendering but I
Launch url is for opening an appropriate app for the url (text file, LiveCode
stack, phone number etc) as associated by your OS. A phone number might open
your phone app on a mobile device. A text doc might open MS Word.
Launch in widget is intended to open a webpage in the browser. Depending
> JLG wrote:
> What is the difference between "launch URL" and "set the URL" in a
> browser widget?
You probably mean load url which caches non-blocking,
contrary to set url.
There is also load url in widget which also sends you a message,
contrary to set url.
Launch url leaves LC and launches
What is the difference between "launch URL" and "set the URL" in a
browser widget?
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
___
use-livecode mailing list
