Right, that makes sense, in particular with Saga's insights in mind.
> Use the commend “defaults delete de.zach.ArtSaverApp” to delete all your
> prefs. That should remove them everywhere.
>
smime.p7s
Description: S/MIME cryptographic signature
Ah, thanks a lot for the insights!
Could it happen that the new settings have not been written to disk even if the
app has quit normally?
Or, in other words, there might be key/value pairs stored in cfprefsd's
internal/runtime storage, even if i have changed the app and those key/value
pairs
I can try that , but I would have no idea what to look for.
Is there any known reasons why a toggleFullScreen call might not send the
window to full-screen?
smime.p7s
Description: S/MIME cryptographic signature
___
Cocoa-dev mailing list
> I have tested this on 1, 2 and 3 display systems over a month ago. There
> appears to be a 1/2 hour delay (or so) before it takes over and is full
> screen.
Very strange - how could that be?
> Greetings from the deepest darkest jungles of suburban Windhoek.
Happy safari!
Best regards,
I would suggest asking your user for a system report or sysdiagnose. It might
glean some details about their environment.
--
Gary
> On Aug 15, 2023, at 3:30 AM, Gabriel Zachmann via Cocoa-dev
> wrote:
>
> I have one user of my macOS app (under macOS 13.4.1)
> where the app does not want to
I have tested this on 1, 2 and 3 display systems over a month ago. There
appears to be a 1/2 hour delay (or so) before it takes over and is full screen.
Sorry, I can’t help more at the moment. Greetings from the deepest darkest
jungles of suburban Windhoek.
Alex Zavatone
Sent from my damn
I have one user of my macOS app (under macOS 13.4.1)
where the app does not want to go into full-screen mode.
It is a pretty plain app.
In the AppDelegate's method -applicationWillFinishLaunching,
I switch to full screen like this:
[self.window toggleFullScreen: nil];
It works, of course,
