[bug] Lock screen background changer

Can only change lockscreen background once

With the latest non-beta version, I found out that I can only change the lock screen background image once.

Steps to reproduce.

1. Start Decor8, and go to Lock Screen section.

2. I then use the 'Select File' function, select an image for the new lock screen background.

3. I then click the 'Apply Selected Background to my lock screen' button to make the selected image my lock screen button.

4. The lock screen background image will be successfully changed, but the 'Apply Selected Background to my lock screen' button will stay greyed out.

5. I then use the 'Select File' function again, to select a new image for the lock screen, but I cannot apply the new image as my new lock screen background image because the 'Apply Selected Background to my lock screen' button is greyed out.

I have to restart the Decor8 program just to change the lock screen background image again.

 

2,551 views 3 replies
Reply #1 Top

I have the same bug which I reported in another thread along with others. Hopefully, the developers are aware of it but there was no response posted in that thread last time I looked.

This bug is extra annoying because not only can I not change the Lock screen image with Decor8 since it keeps resetting back to that cartoonesque one with the tower next to water but I cannot even change to one of the default ones using the Charm bar settings either. I did accidentally stumble across a hidden folder created by Decor8 though which contained around 10 copies of the images, some duplicates, when I'd been trying to set them. The weird thing is that this issue was not there in the beta release, it seemed to have surfaced in the final v1.0 build for me.

Note: I tried running Decor8 as the Administrator but it makes no difference to this bug.

Reply #2 Top

I am also having the same problem, just reported it to support.  I see that could be a waste of time from your NO responses thus far.  UGH

Reply #3 Top

This issue seems to finally be fixed in v1.01 although it was a long time coming. I reported this issue over two months ago so I'm surprised it took so long to address.