Page 7 of 13

Re: What I'm adding, and what I'm planning next...

Posted: Wed Jan 17, 2024 6:04 pm
by tperry2x
richmond62 wrote: Wed Jan 17, 2024 5:56 pm What chance MacOS 10.6 and MacOS 10.7?
I'm afraid not, as LCC 9.6.3 needs MacOS 10.9 as a minimum.
Unless you wanted to change the engine, but that's a huge task because all of those supporting stacks are different.

Re: What I'm adding, and what I'm planning next...

Posted: Wed Jan 17, 2024 9:46 pm
by overclockedmind
Yeah, in Monterey, when I was doing the testing with other things in it I just about thought: did I just run into a virus making prorgram? Cuz damn is this window top-level, systemwide! SYSTEM--wide?

Disclaimer: I thought it was "just me," and well... not so much. I think we just replicated a report up in here, amitrite? :lol:

Re: What I'm adding, and what I'm planning next...

Posted: Wed Jan 17, 2024 11:10 pm
by tperry2x
Sorry, but do you mean you are getting weird window behaviour in MacOS Monterey? - which window is it - could you upload a screenshot please.

Re: What I'm adding, and what I'm planning next...

Posted: Wed Jan 17, 2024 11:33 pm
by overclockedmind
Yes... once I figure all that out (remember, the last macOS I used is seriously 10.8 or something close) :oops:

Re: What I'm adding, and what I'm planning next...

Posted: Thu Jan 18, 2024 12:39 am
by overclockedmind
I tried to find the post Richard and I were speaking of this in; I couldn't..

This is it. I'm in the Applications folder, in the Finder... so how's Untitled 1 there like that? I did set it to float above everything, but shouldn't we not do this within the confines of every program? Or is this expected?

Re: What I'm adding, and what I'm planning next...

Posted: Thu Jan 18, 2024 2:09 am
by overclockedmind
What I am asking is, shouldn't "float above everything" be top window only in the context of the IDE, or when running something for test, or in a resultant executable? All I did was check that box and switch to the Finder, and there's Untitled 1 right on top of the Finder and anything I switch to.

Re: What I'm adding, and what I'm planning next...

Posted: Thu Jan 18, 2024 4:28 am
by overclockedmind
helpcrash.png
helpcrash.png (227.62 KiB) Viewed 4119 times
Might as well also mention the other thing that just happened:

All that happened was me clicking the Help menu after fresh start of the program.
"Continue" works sometimes, sometimes not. I have the info it presented saved, to
a plain-text file the board doesn't want as an attachment.

Maybe good ol' code? Let's try, I guess: (YAY)

Code: Select all

Exception Name: NSInternalInconsistencyException
Description: Invalid parameter not satisfying: index >= 0
User Info: {
    NSAssertFile = "NSMenu.m";
    NSAssertLine = 1024;
}

0   CoreFoundation                      0x00007ff8021876e3 __exceptionPreprocess + 242
1   libobjc.A.dylib                     0x00007ff801ee78bb objc_exception_throw + 48
2   Foundation                          0x00007ff803034cd3 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 267
3   AppKit                              0x00007ff804b39424 -[NSMenu itemAtIndex:] + 151
4   LiveCode-Community                  0x000000010d0d6e61 MCJSObjectGetID + 139745
5   LiveCode-Community                  0x000000010d0d6f8b MCJSObjectGetID + 140043
6   AppKit                              0x00007ff804dd9f40 -[NSMenu _populateFromDelegateWithEventRef:] + 290
7   AppKit                              0x00007ff804d008d1 -[NSMenu _populateWithEventRef:] + 84
8   AppKit                              0x00007ff804e263ef -[NSCarbonMenuImpl _carbonPopulateEvent:handlerCallRef:] + 365
9   AppKit                              0x00007ff804e261e2 NSSLMMenuEventHandler + 1074
10  HIToolbox                           0x00007ff80ad9634d _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 1365
11  HIToolbox                           0x00007ff80ad9579c _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec + 333
12  HIToolbox                           0x00007ff80ad9563d SendEventToEventTargetWithOptions + 45
13  HIToolbox                           0x00007ff80ade5546 _Z16SendMenuPopulateP8MenuDataP20OpaqueEventTargetRefjdjP14OpaqueEventRefhPh + 301
14  HIToolbox                           0x00007ff80ae170fa _ZL15SendMenuOpeningP14MenuSelectDataP8MenuDatadjjP14__CFDictionaryhPh + 332
15  HIToolbox                           0x00007ff80af3d1b1 _ZL11DrawTheMenuP14MenuSelectDataP8MenuDataPP9__CFArrayhPh + 305
16  HIToolbox                           0x00007ff80ae2de55 _ZL11MenuChangedP14MenuSelectDatahh + 248
17  HIToolbox                           0x00007ff80af402b8 _ZL15TrackMenuCommonR14MenuSelectDataPhP13SelectionDataP10MenuResultS5_ + 1094
18  HIToolbox                           0x00007ff80ae2db64 _ZL14MenuSelectCoreP8MenuData5PointdjPP13OpaqueMenuRefPt + 397
19  HIToolbox                           0x00007ff80ae2d93e _HandleMenuSelection2 + 456
20  AppKit                              0x00007ff804ce76d9 _NSHandleCarbonMenuEvent + 215
21  AppKit                              0x00007ff804ce7546 _DPSEventHandledByCarbon + 54
22  AppKit                              0x00007ff804b47de0 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3368
23  LiveCode-Community                  0x000000010d0d1fa3 MCJSObjectGetID + 119587
24  LiveCode-Community                  0x000000010d0c3a18 MCJSObjectGetID + 60824
25  LiveCode-Community                  0x000000010d0beca2 MCJSObjectGetID + 40994
26  LiveCode-Community                  0x000000010d0bf36e MCJSObjectGetID + 42734
27  LiveCode-Community                  0x000000010d0d12c5 MCJSObjectGetID + 116293
28  Foundation                          0x00007ff802f8aae2 __NSFireDelayedPerform + 440
29  CoreFoundation                      0x00007ff802124e99 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
30  CoreFoundation                      0x00007ff802124988 __CFRunLoopDoTimer + 923
31  CoreFoundation                      0x00007ff8021244f8 __CFRunLoopDoTimers + 307
32  CoreFoundation                      0x00007ff80210ac06 __CFRunLoopRun + 2010
33  CoreFoundation                      0x00007ff802109d6c CFRunLoopRunSpecific + 562
34  HIToolbox                           0x00007ff80adbc5e6 RunCurrentEventLoopInMode + 292
35  HIToolbox                           0x00007ff80adbc213 ReceiveNextEventCommon + 283
36  HIToolbox                           0x00007ff80adbc0e5 _BlockUntilNextEventMatchingListInModeWithFilter + 70
37  AppKit                              0x00007ff804b48f6d _DPSNextEvent + 927
38  AppKit                              0x00007ff804b4762a -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1394
39  AppKit                              0x00007ff804b39cd9 -[NSApplication run] + 586
40  LiveCode-Community                  0x000000010d0d42eb MCJSObjectGetID + 128619
41  dyld                                0x00000001149d152e start + 462

Re: What I'm adding, and what I'm planning next...

Posted: Thu Jan 18, 2024 6:41 am
by tperry2x
Looking at the debug, it all seems to be caused by something in the menubar that MacOS doesn't like.

If I get a chance, I'll see if I can find NSMenu.m in the engine c++ code, and look at line 1024
something about index not having a value greater than 0?

I think anything past 'big sur' on MacOS we can list as potentially incompatible, as I was running on about before:
viewtopic.php?p=5685#p5685

Re: What I'm adding, and what I'm planning next...

Posted: Thu Jan 18, 2024 8:15 am
by tperry2x
This is going to sound odd, but in your screenshot above, I notice you have the backdrop turned on.
What if you turn off the 'backdrop' in the view menu?
Does every window of the IDE continue to steal focus still?
focus-mac.gif
focus-mac.gif (144.29 KiB) Viewed 4084 times
It doesn't make any difference as far as I can tell - at least from my testing on 10.9 up to 10.15 Catalina.
I don't have a Monterey mac to test on.

You can see how I'm still able to put the 'System preferences' window in front of the untitled stack window, no matter if the backdrop is on or off.

I just wonder if it's doing something weird on MacOS 12 Monterery for you, perhaps because it doesn't like the backdrop (?) - just a guess at this stage.

Second issue:
sounds a strange question - but the version you are getting that error on, isn't that 0.98 or lower?
The reason I ask is: (to be cheeky and re-use your screenshot you sent)
helpcrash.png
helpcrash.png (109.4 KiB) Viewed 4097 times
I sorted this tool icon out in 0.99 on the mac, so I guess you are running an earlier 0.98 - If so, that has an older copy of revMenubar with conflicting shortcuts.

In version 0.98, I found this conflicted with "revshortcutslibrary.livecodescript"
Or rather, to be more accurate: "revshortcutslibrary.livecodescript" contained statements that were conflicting with the revmenubar.livecodescript stack - they were both trying to set their own values at the same time and fighting for control.

This makes sense, as I was messing about with the 'file' > 'save as' shortcuts in 0.98, and didn't know about this nasty surprise left for me in the revshortcutslibrary.
So, by changing the 'save as' shortcut in the file menu, I would have unknowingly triggered this error and produced a conflict.

This also explains why LCC 9.6.3 and OXT Lite 0.97 and lower didn't produce this error.

This could be exactly why you are getting that NSMenu error, if it turns out you are running an older version - (0.98 specifically)

I have a vague theory that 0.98 was locking up Richmond's mac because of this same issue too.

I had a look at the menu C++ code today, and it appears that the menus on the Mac are drawn with a cocoa API. (Surely that had been phased out). The Mac part of the menu code also contains statements like 'it does this for some unknown reason'.
The Windows and Linux parts of this menu code don't use any cocoa API - that's a Mac thing only), and because they are coded differently, they seem a lot more forgiving of conflicting shortcuts.

Anyway, that's my theory at the moment.
Theories are all well and good, but they need proving.

Either way, I fixed all those conflicts in 0.99 and above, so if you can confirm which version of the IDE this is please that would be great. I'm pretty sure it's something before v0.99.

Re: What I'm adding, and what I'm planning next...

Posted: Thu Jan 18, 2024 11:16 pm
by overclockedmind
tperry2x wrote: Thu Jan 18, 2024 8:15 am This is going to sound odd, but in your screenshot above, I notice you have the backdrop turned on.
What if you turn off the 'backdrop' in the view menu?
Does every window of the IDE continue to steal focus still?

focus-mac.gif

It doesn't make any difference as far as I can tell - at least from my testing on 10.9 up to 10.15 Catalina.
I don't have a Monterey mac to test on.

You can see how I'm still able to put the 'System preferences' window in front of the untitled stack window, no matter if the backdrop is on or off.

I just wonder if it's doing something weird on MacOS 12 Monterery for you, perhaps because it doesn't like the backdrop (?) - just a guess at this stage.

Second issue:
sounds a strange question - but the version you are getting that error on, isn't that 0.98 or lower?
The reason I ask is: (to be cheeky and re-use your screenshot you sent)
helpcrash.png

In version 0.98, I found this conflicted with "revshortcutslibrary.livecodescript"
Or rather, to be more accurate: "revshortcutslibrary.livecodescript" contained statements that were conflicting with the revmenubar.livecodescript stack - they were both trying to set their own values at the same time and fighting for control.

This makes sense, as I was messing about with the 'file' > 'save as' shortcuts in 0.98, and didn't know about this nasty surprise left for me in the revshortcutslibrary.
So, by changing the 'save as' shortcut in the file menu, I would have unknowingly triggered this error and produced a conflict.

This also explains why LCC 9.6.3 and OXT Lite 0.97 and lower didn't produce this error.

This could be exactly why you are getting that NSMenu error, if it turns out you are running an older version - (0.98 specifically)

I have a vague theory that 0.98 was locking up Richmond's mac because of this same issue too.

I had a look at the menu C++ code today, and it appears that the menus on the Mac are drawn with a cocoa API. (Surely that had been phased out). The Mac part of the menu code also contains statements like 'it does this for some unknown reason'.
The Windows and Linux parts of this menu code don't use any cocoa API - that's a Mac thing only), and because they are coded differently, they seem a lot more forgiving of conflicting shortcuts.

Anyway, that's my theory at the moment.
Theories are all well and good, but they need proving.

Either way, I fixed all those conflicts in 0.99 and above, so if you can confirm which version of the IDE this is please that would be great. I'm pretty sure it's something before v0.99.
Be cheeky and use any screenshot of mine that you like. Just watch if you would that you try and cut out anything personally identifying and the like. I'm off to try this backdrop business, and verify the version, but I'm almost entirely sure it's 0.98. Allow me to confirm.
I sorted this tool icon out in 0.99 on the mac, so I guess you are running an earlier 0.98 - If so, that has an older copy of revMenubar with conflicting shortcuts.

Re: What I'm adding, and what I'm planning next...

Posted: Thu Jan 18, 2024 11:18 pm
by overclockedmind
Confirmed that I am in 0.98 - so I'm causing my own issues? :lol:
I must have missed "here's 0.99" in this sea of... stuff.

Re: What I'm adding, and what I'm planning next...

Posted: Thu Jan 18, 2024 11:26 pm
by overclockedmind
BACKDROP OFF

Dunno that it matters now given the version, but here, backdrop's off.
backdropoff.png
backdropoff.png (131.45 KiB) Viewed 3989 times

Re: What I'm adding, and what I'm planning next...

Posted: Fri Jan 19, 2024 1:41 am
by overclockedmind
Backdrop off, no stack loaded period, with no stack open that has a Float Above Everything window within it.

I guess it is tied to whether any stack/project you're trying to build with the "Float Above Everything" thing... assuming it matters. Might not.

Uh, 0.99?

Re: What I'm adding, and what I'm planning next...

Posted: Fri Jan 19, 2024 6:04 am
by tperry2x
overclockedmind wrote: Fri Jan 19, 2024 1:41 am Uh, 0.99?
That looks like 0.98 in your latest screenshot too:
098-too.png
098-too.png (168.37 KiB) Viewed 3964 times

Re: What I'm adding, and what I'm planning next...

Posted: Fri Jan 19, 2024 6:08 am
by overclockedmind
tperry2x wrote: Fri Jan 19, 2024 6:04 am
overclockedmind wrote: Fri Jan 19, 2024 1:41 am Uh, 0.99?
That looks like 0.98 in your latest screenshot too:
098-too.png
That'd be me, meekly asking for you to link me (and I'll be bookmarking it, thanks.)

Re: What I'm adding, and what I'm planning next...

Posted: Fri Jan 19, 2024 6:11 am
by tperry2x
overclockedmind wrote: Fri Jan 19, 2024 6:08 am ...link me (and I'll be bookmarking it, thanks.)
No probs:
Releases page: (always has a list of what I've changed)
viewtopic.php?f=16&p=4646#p4646

Direct Dropbox link:
https://www.dropbox.com/scl/fo/75kfz9ho ... 5xdm5&dl=0

Re: What I'm adding, and what I'm planning next...

Posted: Fri Jan 19, 2024 6:40 am
by overclockedmind
Screen Shot 2024-01-19 at 12.37.46 AM.png
Screen Shot 2024-01-19 at 12.37.46 AM.png (397.68 KiB) Viewed 3952 times
The quick brown fox... well yeah hopefully that's enough filler text for this thing.

Re: What I'm adding, and what I'm planning next...

Posted: Fri Jan 19, 2024 8:09 am
by richmond62
enough filler text
Is it possible to have some action on both the need for "fifty thousand" characters and the messing around involved getting images into posts?

Re: What I'm adding, and what I'm planning next...

Posted: Fri Jan 19, 2024 8:54 am
by tperry2x
To add to the above, I'd like to have an option to delete known spam advertising accounts, such as LysandraMabel

Re: What I'm adding, and what I'm planning next...

Posted: Fri Jan 19, 2024 11:13 am
by richmond62
It has been suggested that some us might be elevated to Admin.