Post by VirtuaMan » 29.11.2017 09:57:31
I have a vbs script as follows:
Set objShell = CreateObject("WScript.Shell")
objShell.SendKeys "%{F11}"
and I call it KeyAlt-F11.vbs.
In Dexpot > Settings > Controls > Miscellaneous > Restore icons from profile I have chosen the key combination Alt and F11. The vbs script does the same as hitting these two keys.
Then in each and every Dexpot window I in a corner have an icon that runs KeyAlt-F11.vbs when double clicked. If the icons are not properly ordered when I open one of the Dexpot windows, I just double-click that icon. Then they normally order up as they should.
But if they still do not, it is because the backup has become messed up. I have two backups: Backup 1 and Backup 2. If still messed up, I load the other one and then it is almost always OK. Then I store it to replace the backup that has become disordered.
So here is a question: Why does it sometimes happen that a backup is disordered after starting Win-dows? That should not happen! It should be as it was stored in the previous Windows session. If only I knew where Dexpot stores the locations of the icons, I could probably have a master backup and at the start of Windows copy its content to the backup folder for Dexpot in …App Data > Roaming > Dexpot > profile. - But maybe I can just copy the ordered backup in the latter folder to a safe place and recopy (overwriting) at start? I will explore that idea… maybe that is where the locations are stored – but how can they then sometimes change when restarting Windows? And it seems that, when they do, it is usually in the backup that is set as a chosen profile.
It is obvious that Windows XP and Windows 7 (and higher) handle the desktop icons differently, and it seems that the Dexpot developers don’t know how Windows 7 (etc.) does it. If they did, they would probably have adapted Dexpot accordingly in a Windows-7-version…
As another little trick I use the program Desktop OK (in a portable version) and let it run in autostart. Then the Dexpot window 1 is loaded at startup, as it is stored by Desktop OK from the last session. Dexpot usually starts a bit later and is not yet running in this moment. When it starts, it just “over-writes” window 1 and then loads all the other Dexpot windows also. So there will not be a “primary mess of icons” immediately after starting Windows – until Dexpot is also running.
I have a vbs script as follows:
Set objShell = CreateObject("WScript.Shell")
objShell.SendKeys "%{F11}"
and I call it KeyAlt-F11.vbs.
In Dexpot > Settings > Controls > Miscellaneous > Restore icons from profile I have chosen the key combination Alt and F11. The vbs script does the same as hitting these two keys.
Then in each and every Dexpot window I in a corner have an icon that runs KeyAlt-F11.vbs when double clicked. If the icons are not properly ordered when I open one of the Dexpot windows, I just double-click that icon. Then they normally order up as they should.
But if they still do not, it is because the backup has become messed up. I have two backups: Backup 1 and Backup 2. If still messed up, I load the other one and then it is almost always OK. Then I store it to replace the backup that has become disordered.
So here is a question: Why does it sometimes happen that a backup is disordered after starting Win-dows? That should not happen! It should be as it was stored in the previous Windows session. If only I knew where Dexpot stores the locations of the icons, I could probably have a master backup and at the start of Windows copy its content to the backup folder for Dexpot in …App Data > Roaming > Dexpot > profile. - But maybe I can just copy the ordered backup in the latter folder to a safe place and recopy (overwriting) at start? I will explore that idea… maybe that is where the locations are stored – but how can they then sometimes change when restarting Windows? And it seems that, when they do, it is usually in the backup that is set as a chosen profile.
It is obvious that Windows XP and Windows 7 (and higher) handle the desktop icons differently, and it seems that the Dexpot developers don’t know how Windows 7 (etc.) does it. If they did, they would probably have adapted Dexpot accordingly in a Windows-7-version…
As another little trick I use the program Desktop OK (in a portable version) and let it run in autostart. Then the Dexpot window 1 is loaded at startup, as it is stored by Desktop OK from the last session. Dexpot usually starts a bit later and is not yet running in this moment. When it starts, it just “over-writes” window 1 and then loads all the other Dexpot windows also. So there will not be a “primary mess of icons” immediately after starting Windows – until Dexpot is also running.