@congoblue you said
We have a use case where we edit the OpenLP service files on the same laptop that we run the service on. When we run the service we have a projector connected by HDMI. When we edit the service files the projector isn't connected (it's installed in the venue).
OpenLP 2.9.4 detects the missing projector and automatically changes the Screen options to show the output on the laptop screen (making it difficult to get to the OpenLP window). Then when we get to the venue on Sunday we have to reset the options to display on the projector.
Previous versions of OpenLP didn't do this, it would leave the output set to projector / 2nd monitor even if it didn't exist. This was preferable behaviour for us as it avoids having to change the output options all the time. There may be an option I have missed to enable this behaviour?
I have the same misbehaviour with 2.9.4 on macOS (various versions). I agree that previous versions of OpenLP didn't behave this way. I have now avoided opening OpenLP on my 'production' machine unless I'm at church and connected to the HDMI connected TV. It's not a great option, especially in winter!
I have assumed that the problem was that OpenLP wasn't (always) recognising the connected external display(s). In a different thread, @raoul said:
"Also, set up your displays BEFORE starting OpenLP. This ensures that OpenLP knows what's going on when it starts up."
I haven't found that it makes any difference what order I do things, but, as I have a workaround of sorts, I wasn't going to bother Raoul with this one until he and the team have got v. 3.0 out and sort of stable. But now that someone else has the same/similar problem, maybe they can have a look at it. I wouldn't object if this was fixed.
Blessings,
Andrew