Bill,

you could try

if(dist - min_distance > 0) { ..do what ever}

Denis

On 21/09/2010 10:53 AM, Bill J Gray wrote:
> Hi Gerhard,
>
>> If I connect to ASCOM scope driver with an other software (like a guiding
>> software) first, I can use ASCOM and all features in Guide8 without
>> problems.
>>
>> So it seems the problem only appears if the ASCOM scope driver is initially
>> installed by Guide8.
>
> Thanks for mentioning this. I tried it, and got the exact same behavior
> (bug only happens if Guide starts up the scope driver). If anybody sees
> this bug under other situations not involving ASCOM, please let me know
> (I'm not entirely convinced ASCOM is at fault).
>
> The bug is a truly weird one. It comes down to this line of code:
>
> if( dist> min_distance)
> { ...do various things }
>
> The idea is that if you just clicked on an object that was, say,
> 10.3 pixels away, then when you click on "Next", min_distance is set to
> 10.3. That way, objects closer than that distance (including the one
> on which you just clicked) won't get selected; only the next-nearest
> object should be picked. Then we reset min_distance again, so we can
> get the nearest object after that, and so on.
>
> For some reason, after you've started up ASCOM from Guide, Guide
> reaches this piece of code for the same object, still 10.3 pixels away,
> and decides that 10.3> 10.3. Not equal to... _greater_ than. So you
> get the same object, over and over.
>
> I've a temporary workaround, which is to add 1e-6 to min_distance.
> Even a computer knows that 10.3 is not greater than 10.300001. But I'd
> still like to know just how it is that 10.3 can be greater than 10.3.
> I also worry that some other things may be affected, though I've yet
> to see any.
>
> -- Bill
>
>
>
> ------------------------------------
>
> To unsubscribe from this group, send an empty email to:
> guide-user-unsubscribe@egroups.comYahoo! Groups Links
>
>
>
>