You can search the LiveCode Quality Center yourself at
https://quality.livecode.com/
Either search for those in the AWAITING_MERGE state or just browse the
bugs and find them
As I said, my recall (which could be incorrect) was that LiveCode. LTC,
had in place an automated build and testing process. No software build
is "easy" and "effortless". So to do one final LiveCode Classic build
with all the AWAITING_MERGE code folded in is still a level of work that
would presumably take some time away from LiveCode Create, but it does
seem to me to be a waste to let the code already written (the "PR" if
you look at one of the "AWAITING_MERGE" bugs) go to waste.
More specifically, I am not sure which "this" you haven't see or what
bits your asking if they are "common knowledge". I assume everyone on
this list is aware of the Quality Center (BUGZILLA) bug and enhancement
reporting system. If you have followed any bugs or reported any, I would
also assume you are aware of the various bug "Statuses" like AWAITING_MERGE.
The LC automated build and testing, I suspect (if my memory is correct)
is less well known as I think it was only spoken to in some of Kevin
Miller's updates in years past (can't remember whether it was in a video
update or text update).
-- Paul
On 8/18/2026 10:20 AM, Craig Newman via use-livecode wrote:
I have never seen this. It is common knowledge? I an on a Ma
Craig
On Aug 18, 2026, at 9:56 AM, Paul Dupuis via use-livecode
<[email protected]> wrote:
I find it interesting that this bug is listed as "AWAITING _MERGE", as well as
a number of other bugs in that same state.
If I recall, that means the code to fix it has been written and just need to be
built and possibly tested.
As I also seem to recall LiveCode spent a lot of time developing automated
testing routines, and an automated build process, I DO have to wonder why they
do not just release ONE more maintenance release of LiveCode Classic with any
and all AWAITING _MERGE fixes rolled in.
It seems like a waste of human resources for someone to have spent the time
fixing the code and not roll it into one last build and release.
-- Paul
On 8/18/2026 1:02 AM, Roger Guay via use-livecode wrote:
Thank you, Paul!
On Aug 17, 2026, at 7:05 AM, Paul Dupuis via use-livecode
<[email protected]> wrote:
There are 1 or more bugs related to cursors and lock cursor I submitted ages
ago that I don;t think have been fixed in classic Livecode.
Here's the one I think applies:
https://quality.livecode.com/show_bug.cgi?id=22211
On 8/16/2026 10:46 PM, Roger Guay via use-livecode wrote:
Hi Folks,
Can anyone tell me why the cursor does not change when I switch from the browse
to pointer tools and vice versa? It’s always the browse tool, regardless of
what I select, even though the function is switched as expected. LC 10.0.5, Mac
OS Tahoe
Thank You
Roger
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
