I recently (finally) updated macOS on my laptop from Sonoma (14.x) to Tahoe
(26.x). Most things are fine, but I've found a couple of anomalies (this is
all with LiveCode 10.0.2).
Before I report these (realistically only the first one), has anyone else seen
the same effects? Is there any evidence that these aren't specifically Tahoe
issues?
1) This is the important one.
A tool I use regularly (in the IDE) which pulls data from a MySQL (actually
MariaDB) database on our local network to output some summary info. Since
upgrading to Tahoe, when I press the button it throws an error when it tries
to connect:
Can't connect to MySQL server on '<hostname>' (65)
When I press the button again, it connects fine. After that I can repeatedly
run the scripts that open this connection... for a while. Then it will happen
again, even if I haven't quit and restarted LiveCode in the interim. The
symptoms would be consistent with LC having to load something (e.g. a driver)
into memory, and either timing out the first time, or doing this in the wrong
order; and then at some later stage that may have been released and need to be
loaded in again. But I'm just guessing here. (I typically have the IDE open
for weeks at a time, and just switch to it to use one of various tools.)
This behaviour is consistent, and definitely related to Tahoe (or it might
have been in Sequoia as well, I skipped past that).
2) In the script editor, I've recently been repeatedly messing with a
particular command in a script in a relatively long process; so I set the
entry point to it. It seems that this is sometimes resetting - even when I
check (under Debug > Entry point...) that it is referencing the correct
command, when I click the play button in the script editor the first command
in the script is executed instead. I have to open the Entry point dialog
again, select something else, then re-select the command I want, and that
solves it.
I can't reproduce this reliably but it's happened several times in the last
week or so. I also can't be sure that it's Tahoe related, because I don't use
that feature very often; but I've certainly not noticed this issue before.
3) Trivial but strange. In the IDE, I have an 'extra toolbar', a palette stack
which docks itself next to the revMenubar and holds a bunch of useful
controls. On revResumeStack and desktopChanged messages, it repositions itself
(and adjusts the size of the revMenubar) - this is needed because I often plug
and unplug external monitors. Since I updated to Tahoe, when my laptop wakes
from sleep (even if no change is made to external monitor) the palette goes
mad, flashing back and forth into place; sometimes it settles down after about
30 seconds of this, sometimes only once I switch to LiveCode. I believe that
this was an interaction between the revResumeStack and desktopChanged
messages; at any rate, once I introduced a semaphore between them so that the
repositioning/resizing code would only run once regardless of which of these
messages fired first and how often, the problem went away. Probably I should
have coded it that way in the first place - but the first place was probably
15-20 years ago, when I was a cruder user of Revolution it was then; and it's
only since moving to Tahoe that this issue has arisen. Obviously it's pretty
obscure; but there is _something_ different happening in Tahoe, that may
affect other LiveCode users.
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
