Full Screen Mode Bug
Posted: Wed Dec 26, 2018 7:11 pm
Hello Friends
I want to report a bug but I don't know if it is something that is reproducible across the Sibelius community.
When I am at home I work with 2 monitors. However, on the go I use multiple desktops within my laptop so I can flip between Sibelius and Transcribe. I am running a MacBook Pro 15 inch with High Sierra. Full screen has always had an issue for me. I would enter to full screen mode but be unable to exit. Now with the latest updates (both 2018.11 & 2018.12) that issue is gone but a new one has replaced it. When I put Sibelius into full screen mode I can't flip back and forth between multiple desktops. It automatically collapses and hides the Sibelius window when I make the switch between desktops. Very annoying.
The work around is easy: click and drag the Sibelius window to the full size of the monitor. However, IMO that is a sloppy back door fix. The full screen expand button should work.
Does this happen to anyone else? Is there a simple setting that I am overlooking that would cause this issue?
Thanks everyone. I appreciate the guidance.
Eric
I want to report a bug but I don't know if it is something that is reproducible across the Sibelius community.
When I am at home I work with 2 monitors. However, on the go I use multiple desktops within my laptop so I can flip between Sibelius and Transcribe. I am running a MacBook Pro 15 inch with High Sierra. Full screen has always had an issue for me. I would enter to full screen mode but be unable to exit. Now with the latest updates (both 2018.11 & 2018.12) that issue is gone but a new one has replaced it. When I put Sibelius into full screen mode I can't flip back and forth between multiple desktops. It automatically collapses and hides the Sibelius window when I make the switch between desktops. Very annoying.
The work around is easy: click and drag the Sibelius window to the full size of the monitor. However, IMO that is a sloppy back door fix. The full screen expand button should work.
Does this happen to anyone else? Is there a simple setting that I am overlooking that would cause this issue?
Thanks everyone. I appreciate the guidance.
Eric