Post by Andrew » 21.10.2005 01:56:17
The images were JPGs, although I have now tried it with BMPs with the same result.
There is one BMP in the Dexpot directory and it is a copy of the image that is retained on that one desktop that works properly... it has been named "Hintergrund Andrew6.bmp" which I am guessing means Background for Andrew's number 6 desktop.
Just by the by, it's a bit of a no-no to be writing runtime data/files to the application directory... if this is happening by design then you really should be looking at using the Documents and Settings\<user name>\Application Data\<app name> directory. Writing to any directory below Program Files assumes the user has admin privilege, which is contrary to Microsoft's best practice for runtime security. Anyway, changing the permissions on this directory to grant "Modify" privilege to my user did not help either.
The images were JPGs, although I have now tried it with BMPs with the same result.
There is one BMP in the Dexpot directory and it is a copy of the image that is retained on that one desktop that works properly... it has been named "Hintergrund Andrew6.bmp" which I am guessing means Background for Andrew's number 6 desktop.
Just by the by, it's a bit of a no-no to be writing runtime data/files to the application directory... if this is happening by design then you really should be looking at using the Documents and Settings\<user name>\Application Data\<app name> directory. Writing to any directory below Program Files assumes the user has admin privilege, which is contrary to Microsoft's best practice for runtime security. Anyway, changing the permissions on this directory to grant "Modify" privilege to my user did not help either.