Upon opening fullscreen apps new theme isn't fully applied.

Allan Nyholm Nielsen

October 12, 2013 09:59

So,

This time it's a bug regarding opening fullscreen apps with Flavours. Let's say you've previously opened an app like Mail in fullscreen after previously just being windowed using a theme like Bexos or whatever theme is and then after this quit the app while it's in fullscreen mode and then decided to open Mail once more - this time it opening in fullscreen -- not a big deal since it's what the normal behaviour is. 

That's the explanation - now the bug. The area surrounding the buttons does not get themed after this. The background in an area of a few pixels changes to the default theme in OS X. Not just Mail has this bug but Safari as well. I haven't tried other apps but I could imagine it turns out just as bad in other apps as well. Apps like Spotify which use a custom UI does not have this issue. Not thinking Contacts app has the issue either. I would have taken a screenshot but I hope the explanation will help you along in testing it yourselves?

Thank you otherwise for Flavours. 

1

• 

  Nuno

  October 14, 2013 08:31

  Dear Allan,

  Thank you so much for providing a very helpful and detailed feedback! This really helps us!

  We have in fact been able to reproduce this issue, and it is already fixed on our internal build, which will be available on the upcoming 1.1.0 Beta 3, to be released soon. I really appreciate your time and efforts to describe the issue so well!

  Again, thank you, and best regards!

  Nuno

  0
• 

  Allan Nyholm Nielsen

  October 14, 2013 15:14

  You're welcome - although now that I look closely on the beta release notes I can see that you've already fixed it in a beta release. Again, that's what I'm reading from the release notes. Could be a separate bug or you are being nice to me ;) I should have looked at the beta forum first.

  I'll try the beta soon - I'm no stranger to betas so this should go smooth.

  0
• 

  Nuno

  October 15, 2013 09:30

  Hi Allan

  Ops, my mistake! I though that fixed was pending yet, but yes (you're right), it was made available on the 1.1.0 Beta 2 release. We should be releasing Beta 3 later this week which will include additional bugfixes and under-the-hood improvements.

  Thank you once again for your feedback!

  Nuno

  0

Please sign in to leave a comment.