[APBeta] Observation attempted but not found

Paul Rodman paul at ilanga.com
Mon Jul 6 06:54:58 PDT 2009


On Jul 6, 2009, at 4:28 AM, Dan Kuchta wrote:

>> I will add a feature request for this, but I doubt it will make V2.0,
>> since it requires many tricky changes. In fact, I think there's
>> already a feature request for something like this. I'll check... Yup:
>>
>> <http://www.astroplanner.net/reports/details/1700/1731.shtml>
>>
>> However, you make some other good points, so I will file a separate
>> request.
>>
>> What about a boolean observation user-defined field called "Not
>> found"? That will give you a checkbox. Unfortunately, it will be
>> logged as an observation, and won't be flagged in the list of
>> observations.
>>
>> Paul R.
>
> Hi Paul:
>
> Yeah, I kinda figured this might be too much for V2 at this stage of  
> the game.  But it's good to see others share the same concern.
>
> The problem I see with a user-defined field is that if this is going  
> to be done "right" in a future version, it would not be able to  
> account for the user defined field that was used in the past.
>
> What about adding a checkbox on the Observation tab underneath the  
> +, - etc. buttons to the left of the box with Magnification limits  
> etc. in it?  Even if this checkbox does nothing for now, it would at  
> least record the information in a standard location that can be used  
> by the UI when it catches up with this feature in V3 (or maybe 2.1 :-)
>
> That way, you could introduce UI features that take advantage of it  
> when time allows.  For example, adding it as a searchable field in  
> the observation database would seem fairly straightforward and might  
> be able to be done before having the rest of the UI display this  
> correctly.
>
> Or if you'd rather have us use a user-defined field at this point,  
> would there be some way to transfer that data to the real UI element  
> in the future - maybe a script or something?  It could be a long  
> time till V3 and I'd hate to have to go back through all those  
> observations to manually transfer the information.

Well, what I would probably do is add another column to the Telescope/ 
Eyepiece/.../Rating list called "Observed" with a checkbox in it  
(initially ON). Thus you'd be able to record that an object was not  
observed with such-and-such a combination, but was observed with, say,  
a shorter FL eyepiece. That would be relatively easy to implement.

What would be trickier would be to display # of observations to  
include only those that have at least one "observed" entry.

Let me ponder this.

In the worst case, you could use a user-defined "Not observed"  
checkbox and I would guarantee that this would be "updateable" in the  
future via a simple script.

Paul R.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.astroplanner.net/pipermail/apbeta-astroplanner.net/attachments/20090706/bf3bec82/attachment-0003.htm>


More information about the APBeta mailing list