I have a home network that contains a mixture of devices, some of which that receive a...
Background Manager has progressed out of its Beta stage with today’s release of version 1.0!
New features have been added, which allows you to select from a number of Transition Effects – or none at all – for the background images. This applies only to full-screen background images that change at a specified interval. The effects, in addition to the original Crossfade, include Slide and Cover. The Slide effect “pushes” the old image out of the way, whereas the Cover effect will slide a new image on top of the old one. This can be set to happen from any of the four positions on the screen. It is also possible to set the Transition Speed now, which before was fixed to 600 milliseconds – it can now be set from 100ms (0.1 second) to 7500ms (7.5 seconds).
Background Manager now uses browser cookies instead of a PHP session to store which image was displayed to a visitor, when set to change a background at each browser session. This is to better accommodate the EU/UK laws regarding cookies. The cookie is a ‘non-essential’ part of the visitor’s browsing experience, and for this reason EU/UK websites need to ask a visitor permission prior to have the cookie set after 26 May 2011 (or 26 May 2012 for the UK). The cookie that Background Manager sets is “myatu_bgm_bg_id_X” where X is a number.
Thanks to the input of users, I have been able to fix a few bugs. One was that all background images were scaled down to a maximum width of 1024 pixels, which has now been corrected. There’s no need to re-add your images, it will automatically use the original size of any images you already have in your Image Sets.
Google Chrome experienced a race condition at times, where the background image would “disappear” if it was already cached by the browser. A small delay was added to avoid this. On the topic of browsers, Firefox had the potential of crashing or behave erratic because there were too many events attached to the background image as Background Manager “forgot” to remove old ones as it added a new one. This was only the case with full-screen images that would change at a specified interval.