opened socket in IDE prevents script changes
bdrunrev at gmail.com
Fri Jan 15 10:30:36 EST 2021
I'm seeing exactly the same range of behaviours I described earlier for
9.5.1 on Win 10 but with 9.6.1 on OS X.
It's very strange that Alex is also editing scripts with sockets
opened/closed but not losing changes made in the script editor. I also had
3 crashes on OS X within 30 minutes of working on this stack.
Alex, are you using the IDE's script editor or some external editor? If
you are using that script editor, once you've opened a socket could you add
a comment to your stack script, apply, close the script editor, then edit
the script again to see if the comment has persisted? I have to quit LC to
make any changes to a stack once I've opened a socket.
It seems to me that once a socket has been opened that the IDE is no longer
persisting changes. I'm pretty sure I didn't see this behaviour on my
previous project using sockets.
On Fri, Jan 15, 2021 at 12:21 PM Bernard Devlin <bdrunrev at gmail.com> wrote:
> Thanks Alex for your quick response.
> I'll try with 9.6.1 on Mac. The only other difference between us is that
> my sockets are interacting with a process outside of LC. But I can't see
> why that would make a difference (particularly once I've closed all
> sockets, I wouldn't expect sockets to interfere with scripts being
> On Fri, Jan 15, 2021 at 12:07 PM Alex Tweedly via use-livecode <
> use-livecode at lists.runrev.com> wrote:
>> I've not seen any such problems - though with 9.6.1 / Mac.
>> I've spent most of the last week in the IDE, with two or more stacks
>> open (one server, one client - occasionally multiple client stacks) so I
>> have multiple open sockets (both 'accept'ing and 'open'ed) almost all
>> the time, and had no problems with IDE or script editor.
>> (I know - that's no consolation, but I thought I'd mention it in case
>> 9.6.1 was an option for you and might just help:-)
More information about the use-livecode