Post by Andrew » 10.10.2005 06:00:12
Seems to be solved - I removed the application from the "All desktops" startup tab, then the "Copy to all desktops" rule works when the app is started.
Interestingly, if I start the app from within Dexpot (say from Desktop 1), the rule does execute but the app goes ballistic when it starts, littering lots of windows that the user should never see over every desktop; then closing the app results in runtime errors (object reference not set). However, if I start the app before Dexpot and then let Dexpot copy to all desktops via its rule it seems fine... I'm guessing there must be some difference in permissions when Windows starts the app compared to when Dexpot starts it.
I am running WinXP SP2 and Dexpot 1.3. The app is Vision Manager (by Performance Solutions) - it's a UI for PABX voice mail/phone management. My Windows user account does have local admin privilege (I know, I know - I'm getting around to fixing that up!) so it may be bad design within Vision Manager relying on admin rights at runtime. I will retest this once I have removed admin rights from my account.
Seems to be solved - I removed the application from the "All desktops" startup tab, then the "Copy to all desktops" rule works when the app is started.
Interestingly, if I start the app from within Dexpot (say from Desktop 1), the rule does execute but the app goes ballistic when it starts, littering lots of windows that the user should never see over every desktop; then closing the app results in runtime errors (object reference not set). However, if I start the app [i]before [/i]Dexpot and then let Dexpot copy to all desktops via its rule it seems fine... I'm guessing there must be some difference in permissions when Windows starts the app compared to when Dexpot starts it.
I am running WinXP SP2 and Dexpot 1.3. The app is Vision Manager (by Performance Solutions) - it's a UI for PABX voice mail/phone management. My Windows user account does have local admin privilege (I know, I know - I'm getting around to fixing that up!) so it may be bad design within Vision Manager relying on admin rights at runtime. I will retest this once I have removed admin rights from my account.