opened socket in IDE prevents script changes
alex at tweedly.net
Fri Jan 15 07:05:59 EST 2021
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:-)
On 15/01/2021 11:37, Bernard Devlin via use-livecode wrote:
> This is a strange phenomenon.I wonder if anyone else has seen this.
> Livecode 9.5.1 Windows 10.
> If a socket is opened then changes to scripts in the IDE are not
> applied/saved. There's no error message. It *appears* from the IDE that
> the changes are applied (i.e. the changes are visible in the script editor,
> the "apply" button indicates the script is no longer dirty).
> *Even if the socket is then closed and changes made this problem occurs.*
> There are also many crashes of the IDE in working on scripts involving
> sockets. It's because of these crashes that I realised changes are not
> Once a socket has been opened/closed then in the IDE the stack cannot be
> closed/reopened without closing/reopening the entire IDE. Saving the stack
> from the message box also results in the (not really applied) changes being
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode