Fair enough. I had no idea that you were no longer working on developing the program. I'm sure I'm probably reiterating what your users already said to you when you originally made this announcement, when I say that your program and AutoHotKey are two of the most important, comprehensive macro/automation systems available for Windows and that this news is very disappointing. This is literally the only problem I've had with the program in something like six years. (I tell a lie, I have a floating topmost bar that completely breaks Google Photos Screensaver by stopping it from running a split second after it starts, but that definitely isn't any sort of dealbreaker IMO).
At any rate, it's a shame that the icons feature will remain broken and that we need to use a separate program on x64. More people will be using x64 in the future as programs and operating systems start requiring a little more than 3Gb of RAM to operate comfortably in - I'm guessing (hoping) x86 will go the way of the dinosaur in a couple of years (shrug). I'm pleased to announce that I discovered that the program I now use, DesktopOK, actually DOES have command line parameters to save and load icons so I'm back in business. http://windows7themes.net/save-and-restore-desktop-icon-layout-in-windows-7.html Using a menu option in PP I can save and load icon positions exactly the same as I used to before. Problem solved. Thanks and regards, Dhry --- In [email protected], "brucexs" <bruc...@...> wrote: > > Also should have mentioned the fact that PPro is 32 bit app and explorer 64 > bit, leading to more complications in implementing this capability (and in > fact this may be the main reason it does not work now). > > > > --- In [email protected], "brucexs" <brucexs@> wrote: > > > > > > compatibility is introduced. Everything else appears to work - menus, > > rolling up windows.. I don't get why the simple location/positioning of > > icons on a desktop is a fail point. > > > > Because it is not using supported Windows APIs, as do the other things you > > mention. For XP and previous, you have to reverse engineer internal > > Windows data structures running in Explorer and use special tricks to > > manipulate them. I imagine the same is true Vista and later, where the > > internal data structures may have changed and/or the new security model may > > mean new tricks have to be used to reach into Explorer. > > > > I am afraid I stopped officially supporting PowerPro some time ago. I fix > > easy bugs now and then, but this one would require significant work. In > > addition, I don't have access to Windows 7. > > > > So I am afraid I don't have any plans to try to fix this. > > >
