When my students turn in their assignments all their individual stacks usually
have the same name. If I try to loop through all of them there seems to be no
way to close one stack and move on to the next one (with the same name) without
getting the dialog asking if I want to save, purge or cance
I believe there is a IDE handler you can call to unload a stack -
something like "revUnloadStack" or similar, but I do not recall the
exact API name.
Hopefully, some one else on the list has the exact API details.
Alternatively, contact supp...@livecode.com and ask what the IDE API is
to unlo
This is a test of the use list.
Bob S
___
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
Bi.
There has been much discussion on the forum why, if the “destroyStack” property
is set to “true”, there still seems to be remnants of that stack that linger
when the “close stack” command is given.
Nonetheless, have you established that this property is set? If not, set it,
and let us know
Thanks for the input, digging further…
If I run the following code:
put 0 into tCount
delete tStackID
put revLoadedStacks() into tStackList
repeat while tStack is among the lines of tStackList
add 1 to tCount
delete stack tStack
wait 100 milliseconds with messages
I have sockets working in my File Server Agent, but only using non-blocking
calls, that is using "with message". Removing the "with message" bit does not
return any response from the server agent.
For instance I send a payload using
write payload to socket tSocket with message "messageReceived
Bob -
Don't use EOF. It's broken since forever ago.
I've done both of the following methods with success:
-- either --
End your data stream with a CR, and then on the receiving end "read from
socket XYZ for 1 line". This assumes that the data stream itself doesn't
contain any CRs. I normally
Are you opening all the same-named stacks at once? LC warns that this
produces unreliable results and should be avoided. The "delete stack"
command does work from a script, but if there are several open with the
same name there's no telling what the engine will do. The normal way to
handle this
