Ben 2008-06-11 17:12
I'm using ultramon with VB6 to control a 2nd monitor. When our VB application is closed UltraMonIndDisp.exe remains running (I can see it in task manager) for around 30 seconds after. If the application is restarted before UltraMonIndDisp.exe has closed we get some strange behaviour.

The references to ultramon are declared as follows...Global umWnd As New UltraMonWindowGlobal umSys As New UltraMonSystemGlobal umInd As New UltraMonIndDispGlobal umUtil As New UltraMonUtilityGlobal umMon As ULTRAMONLib.IUltraMonMonitor

and these are all set to "Nothing" when the application closes.

Any ideas how I can tidy up references properly, or is this behaviour to be expected?

Thanks

Ben 2008-06-11 17:15
Follow Up: Sorry I forgot to mention i am using Ultramon version 2.6.23.0

Christian Studer 2008-06-12 09:48
This seems to be standard behavior for out-of-process COM servers like UltraMonIndDisp, I'm not aware of a way to change this.

What kind of problems do you experience when you restart your application with UltraMonIndDisp still running?

Ben 2008-06-15 22:58
The problem we experience when UltraMonIndDisp is still running is that DetachedApps.LaunchAndAdd fails to launch the app on the 2nd monitor. It appears on the main monitor instead.

Christian Studer 2008-06-16 11:18
I have now done some testing, my guess would be that the following happens: