Built with Xojo2017r2.1, 32 bit.
Is that a known issue, has it been reported to Apple (if so, under which radar ID)?
You might fighting an uphill battle. Not sure Apple is going to care about fixing a 32-bit bug and I’m not sure Xojo is really going to fix something in Xojo 2017 R2.1. I would say test again with the current Xojo release and alpha and see if it’s still happening for 32-bit.
Bob, they fixed most of the other visual bugs in the recent betas, so what makes you think they would not care about a crashing bug?
Also, I cannot release a bugfix update any more for FAF (which crashes due to this bug) in the MAS as I cannot simply build a 64 bit version with Xojo (am working on a new version in ObjC now). So, this is not something I can fix by hoping Xojo will address - which I find more unlikely than Apple addressing this, anyway, seeing how little Xojo did respond to other Mojave issues in the past weeks.
[quote=401903:@Thomas Tempelmann]Built with Xojo2017r2.1, 32 bit.
Is that a known issue, has it been reported to Apple (if so, under which radar ID)?[/quote]
Have you tried a newer version of Xojo?
Is there perhaps something I might be able to help with here? What’s the problem?
[quote=401903:@Thomas Tempelmann][h]SelectFolder crashing on Mojave (b8)[/h]
Built with Xojo2017r2.1, 32 bit.
Is that a known issue, has it been reported to Apple (if so, under which radar ID)?[/quote]
Could you be more specific? I just tried 2018r2, 2017r3 and 2017r2.1 with this code and it certainly doesn’t “crash”, whether I select something or not.
call SelectFolder()Greg, I can’t yet tell what’s causing this.
One of my apps, Prefs Editor, made with 2018r1, in 64 bit, does not crash, but both FAF and iClip, both made with 2017r2.1, do crash.
Here’s the bug report I sent to Apple: http://www.openradar.me/radar?id=5549639256244224
Apple needs to fix this, as they won’t let me submit a fix with a newer Xojo version unless I submit is as a 64 bit app, which is easier said than done, so even if the crash would not occur with a more recent Xojo version, it won’t help me (but if the reason for the crash is known, I’d be happy to let Apple know so that they can hopefully fix this more easily).
Oh, now this is curious: I was just using BBEdit 10.5.13 on Mojave, and when I got the file selector dialog there to save a new file, and pressed shift-cmd-D to show the Desktop in the dialog, it ran into the same type of crash.
So, this is an issue not happening only with Xojo. I guess it’s about using an older (Carbon based?) file dialog.
Well it helps to know that it was pressing cmd-shift-D that caused the issue…
The Carbon file dialogs have had problems for the past couple of years. If that is the cause i’m surprised you haven’t been bitten long before now.
@Greg O’Lone No, shift-cmd-D was just the first way I crashed BBEdit. Cancelling (Esc key) did it for me just as well when I tried again.
@Kevin Gale But if it’s such that an old and known bug, as you suggest, shouldn’t Xojo 2017r2 have dealt with it already?
Also, to clarify: Both my crashing apps (FAF, iClip) are built for Cocoa, not Carbon, of course. I just said that I suspect that an older File dialog function was used that’s not used by modern Xcode-built apps any more but that were still in use by Xojo 2017r2. No idea if that’s really the case, though, as I have no idea what’s being used.
The bug is not reproducible here with FAF 1.9.3.
@Beatrix Willius Damn - I had customers contact me about that, so it’s not just me.
Would anyone else with Mojave please download FAF from http://apps.tempel.org/FindAnyFile/, launch it, type cmd-shift-O to open a file, then cancel the dialog? Does it crash for you?
@Beatrix Willius, @Greg O’Lone Please try this: In your System Preferences, under General, enable the option to Always show the Scroll Bars.
Now try again - I found that only if that option is set, it’ll crash.
[quote=402041:@Thomas Tempelmann]@Greg O’Lone No, shift-cmd-D was just the first way I crashed BBEdit. Cancelling (Esc key) did it for me just as well when I tried again.
@Kevin Gale But if it’s such that an old and known bug, as you suggest, shouldn’t Xojo 2017r2 have dealt with it already?
Also, to clarify: Both my crashing apps (FAF, iClip) are built for Cocoa, not Carbon, of course. I just said that I suspect that an older File dialog function was used that’s not used by modern Xcode-built apps any more but that were still in use by Xojo 2017r2. No idea if that’s really the case, though, as I have no idea what’s being used.[/quote]
The problems we had were in an RB app. Our investigation at the time indicated that it was an issue that Apple had introduced. I would have thought the Xojo Cocoa dialogs would be using something like NSOpenPanel and if so, a different problem altogether.
I wonder if it’s because Apple doesn’t like modal dialogs anymore?
It might be worth noting that I have a couple of customers who report that one of my apps freezes sometimes when they click “Save” in a Save dialog. What happens is the file list vanishes, but the rest of the dialog is still present and won’t accept any input, being a sheet dialog, that’s it, the window is now jammed.
I actually had it happen on my work machine once, but I was unable to figure out why and the second time, it didn’t happen.
What makes you think that we’re not?
I appears that Apple fixed this crash in Mojave b9.