On 20/03/2016 04:14, J. Landman Gay wrote:
Not exactly. I tried a similar file path when I was testing a widget but
it wouldn't load at all, nothing happened. I just now realized that the
file path has spaces in it. If I remove those (or encode them) it does
load, so the widget works after all. Then I pasted the file path (with
hashtag) into the inspector and that worked too. I didn't see the
problem you described, the widget keeps its original size. Looks like I
do have an option, thanks for that.
The bug report that explains my issues with revBrowser is here:
http://quality.livecode.com/show_bug.cgi?id=17179
Hi Jacqueline,
For reliability I do recommend using an RFC 1738 URL with a browser,
rather than a "LiveCode-style" file URL.
For example, "file:///Users/peterbrett/My%20File%20Name.doc" rather than
"file:/Users/peterbrett/My File Name.doc"
Do the problems with the #-component in revBrowser go away if you use an
RFC 1738 file URL?
Peter
--
Dr Peter Brett <[email protected]>
LiveCode Open Source Team
LiveCode 2016 Conference https://livecode.com/edinburgh-2016/
_______________________________________________
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
