Re: [Bf-committers] Should we change the splash image when the version number changes?

2019-10-12 Thread Gaia Clary
Maybe it is as simple as displaying the splash screen in greyscale... What about something like this: if version_cycle == "Alpha":   display_the_splash_in_grey_scale(saturation=0.1) #Almost black&white see: http://pasteall.org/pic/show.php?id=a18beb5d36f5dfd320f091278489a294 That would be autom

Re: [Bf-committers] Should we change the splash image when the version number changes?

2019-10-11 Thread Brecht Van Lommel
We could consider adding a new splash at the start of the release cycle, instead of at the end. It makes some sense for a specific Blender version to always have the same splash. On Fri, Oct 11, 2019 at 5:29 PM Dalai Felinto wrote: > Hi Antonio, > > What you propose is not really solving the pro

Re: [Bf-committers] Should we change the splash image when the version number changes?

2019-10-11 Thread Dalai Felinto
Hi Antonio, What you propose is not really solving the problem. To have a new splashscreen from 2.81 and still use the 2.80 splashscreen for 2.82 (master) would be even more strange in my opinion. In a way what we have now is no different than having a stable Blender with a splash, and master wit

[Bf-committers] Should we change the splash image when the version number changes?

2019-10-11 Thread antonioya blend
Hi all, Until now, when we had a version, the splash was changed at the end when the release was made. With the new way of working, the version is changed at the beginning and appears in the splash, and we follow the development in the master branch. The release of the previous one has its own