[APBeta] ASCOM disconnect

[Tim Long]

Two suggestions for closing/releasing ASCOM drivers.

1. Make sure you set the Connected property to False before releasing your reference to a driver. If you don't, and the driver happens to be multi-threaded, then things can conspire to keep the driver alive because it is effectively holding a reference to itself.
2. If the driver implements IDisposable, consider calling it's IDisposable.Dispose() method. Not many drivers implement IDisposable, but some do, and this is a good way of telling it to delete itself.

Tim Long, Principal Technology Specialist
TiGra Networks - The Small Business IT Specialists
0845 8620518 | www.tigranetworks.co.uk
 


-----Original Message-----
From: apbeta-bounces at lists.astroplanner.net [mailto:apbeta-bounces at lists.astroplanner.net] On Behalf Of Paul Rodman
Sent: 12 February 2009 3:03 PM
To: AstroPlanner Beta Testers
Subject: Re: [APBeta] ASCOM disconnect


On Feb 12, 2009, at 01:37 AM, Peter B wrote:

> I loaded up V2b20 tonight and like the improvements you've made  
> since V2b17.  I tried it with ascom EQMOD and have not found any  
> bugs yet.  The only thing I've found is the ascom window does not  
> close when I disconnect the scope.  Some time (5 minutes) later it  
> decides to close.  Not sure if this is related to ascom or AP.

Probably to my lack of understanding of ASCOM. I'll get to it  
eventually.

Paul R.

_______________________________________________
APBeta mailing list
APBeta at lists.astroplanner.net
http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net