On the bright side, it isn't as confusing as the one that tells you the
script has been changed in an external editor, even if it wasn't, and then
you don't know whether to keep what you're looking at or take a chance and
reload. You can lose work by choosing the wrong button.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On October 6, 2021 4:32:25 PM Mark Wieder via use-livecode
<use-livecode@lists.runrev.com> wrote:
On 10/6/21 1:22 PM, Eraklis Pittas via use-livecode wrote:
I just put up with it and kill LC - I don't think we will ever have a
definitive answer or fix (prove me wrong please!) . As I say they
don't seem to eat their own Dog Food otherwise this would have been sorted
years ago.
That's what I do as well. Kill, then go do something else for a bit.
Reading the code that invokes this dialog (the reloadstack handler in
revbackscriptlibrary.livecodescript) isn't much help. It's only the IDE
that can't handle this, not the engine.
This would all be moot if the IDE used the long id of the stack instead
of just the short name of the stack, but that would require work.
BTW - the original bug report on this is now 18 years old.
https://quality.livecode.com/show_bug.cgi?id=1061
--
Mark Wieder
ahsoftw...@gmail.com
_______________________________________________
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
_______________________________________________
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
