<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><blockquote type="cite">I will add a feature request for this, but I doubt it will make V2.0, <br>since it requires many tricky changes. In fact, I think there's <br>already a feature request for something like this. I'll check... Yup:<br><br><<a href="http://www.astroplanner.net/reports/details/1700/1731.shtml">http://www.astroplanner.net/reports/details/1700/1731.shtml</a>><br><br>However, you make some other good points, so I will file a separate <br>request.<br><br>What about a boolean observation user-defined field called "Not <br>found"? That will give you a checkbox. Unfortunately, it will be <br>logged as an observation, and won't be flagged in the list of <br>observations.<br><br>Paul R.</blockquote><div><br></div><div>Hi Paul:</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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 :-)</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>-Dan</div></body></html>