koffiejunkie
Executive Member
This is driving me to drink more than I already do. One laptop. One external screen to the right of the laptop. Desktop extending to the right onto the second screen.
Open a file in QuicktimeX, drag it to the second screen, hit play, hit full screen.
Now, what used to happen, is it went full screen. I have something running on the external screen, while poking around on my main screen.
Instead, when I hit full screen, it goes full screen on the laptop screen, and whatever was on the external screen, kinda slides in behind QuicktimeX, leaving me with a blank external screen.
I vaguely remember I had to write a default setting but I tried two so far which QuicktimeX seems to ignore:
defaults write com.apple.QuickTimePlayerX MGFullScreenExitOnAppSwitch 0
defaults write com.apple.QuickTimePlayerX FullscreenPreferenceCaptureAllDisplays 0
It seems to ignore both. Now, I copied good old Quicktime Pro from my old drive, and that seems to behave right. I looked at all the resources I could find on settings for QuicktimeX, but nothing reads like it might affect this (and it seems to ignore everything anyway).
Has anyone managed to get it to behave?
Thanks
Open a file in QuicktimeX, drag it to the second screen, hit play, hit full screen.
Now, what used to happen, is it went full screen. I have something running on the external screen, while poking around on my main screen.
Instead, when I hit full screen, it goes full screen on the laptop screen, and whatever was on the external screen, kinda slides in behind QuicktimeX, leaving me with a blank external screen.
I vaguely remember I had to write a default setting but I tried two so far which QuicktimeX seems to ignore:
defaults write com.apple.QuickTimePlayerX MGFullScreenExitOnAppSwitch 0
defaults write com.apple.QuickTimePlayerX FullscreenPreferenceCaptureAllDisplays 0
It seems to ignore both. Now, I copied good old Quicktime Pro from my old drive, and that seems to behave right. I looked at all the resources I could find on settings for QuicktimeX, but nothing reads like it might affect this (and it seems to ignore everything anyway).
Has anyone managed to get it to behave?
Thanks