I am getting the impression that any calls to network functions in your app
will cause tsNet to be included (assuming you have auto detect on). I could be
> On Mar 5, 2018, at 02:18 , Graham Samuel via use-livecode
> <email@example.com> wrote:
> [This message was identified as a phishing scam. Learn about phishing at
> This message may be a repeat. If you see two copies on the list, I apologise.
> I’ve been executing this line of script in an app made on a Mac with LC 9.0.0
> get URL “http://www.myserver.com/mytextfile
> It works fine, but I also wanted to detect what happens when the connection
> can't be established, so I made the command fail by switching off internet
> access on my machine. I got an error in ‘the result’, as expected. Or at
> least I got one when the line was executed in the IDE, and this was a tsNet
> error. As I had not initialised tsNet in my script - according to the
> dictionary, this **must** be done before tsNet functions are used - I
> concluded that the IDE had done it for me.
> Fair enough, but I then reasoned that if I wanted to see the same kind of
> explicit error messages in my standalone, I would have to include a call to
> tsNetInit in my script. However, I created a little test app which
> **doesn’t** make any tsNet calls, certainly not initialising the package, but
> I still get a tsNet style error, e.g.
>> tsneterr: (6) Could not resolve host: www.myserver.com
> So, what’s going on? Is tsNet now always included in a standalone, and if so,
> how does it get initialised?
> Puzzled, not for the first time.
> use-livecode mailing list
> Please visit this url to subscribe, unsubscribe and manage your subscription
use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription