Re: Websockets Problem on LiveCode

2018-12-28 Thread Tom Glod via use-livecode
> > Hey Todd, did you get this figured out? > > ___ 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: Websockets Problem on LiveCode

2018-12-27 Thread hh via use-livecode
> Todd wrote: > I assume that it is a memory leaking error. Has anyone had this problem of > calling LiveCode function from a JavaScript function in the browser?? This > is a HUGE problem for us as the app cannot be shipped. Libbrowser eats on desktop up to 5 MByte of memory per second. Bug

Re: Websockets Problem on LiveCode

2018-12-26 Thread Charles Warwick via use-livecode
Hi Todd, Did you try the sample LC stack that I sent you with the socket external? It allows you to send basic websocket messages to a server. If you did try it, what happened? The beta version should work on Windows, Mac and iOS (Android version is easy to add if needed). Regards,

Websockets Problem on LiveCode

2018-12-26 Thread Todd Fabacher via use-livecode
This is a 911 call for HELP from anyone. We are using a Socket IO server. We tried using the web browser to send websockets messages...no problems. but when we listen and receive the websocket message, that is where the problem is created. If we don't call LiveCode from the web browser, we don't