[APBeta] Moving the Observation database to another machine

Hilary Jones hdjones at pacbell.net
Thu Jul 9 10:06:47 PDT 2009


I haven't found any use for linking an observation back to the original 
plan.  In fact I've never felt much need for anything beyond _global_ 
observations.  To me an observation is an observation and has nothing to do 
with which plan was in use when the observation was made.  If I want to do 
anything along those lines, it would be to tie the observation to a session 
rather than a plan.  So bottom line, I would have no problems if the links 
went away.

Hilary


----- Original Message ----- 
From: "Jeff Young" <jey at adobe.com>
To: "AstroPlanner Beta Testers" <apbeta at lists.astroplanner.net>
Sent: Wednesday, July 08, 2009 3:58 AM
Subject: Re: [APBeta] Moving the Observation database to another machine


> Now that observations are easily edited from the global observations 
> window, the only time I ever use the reference back to the original plan 
> is for sorting -- for which it doesn't need to be a real link.  That being 
> said, I almost never do that either, so I wouldn't really care if it went 
> away entirely.
>
> While we're on the topic of editing from the global observations window, 
> it'd be nice if the edit dialog had the information box (with 
> magnification limits, focal length, etc.) as found on the observations 
> tab.
>
> -- Jeff.
>
>
>> -----Original Message-----
>> From: apbeta-bounces at lists.astroplanner.net 
>> [mailto:apbeta-bounces at lists.astroplanner.net] On Behalf Of
>> Paul Rodman
>> Sent: Wednesday, July 08, 2009 2:21 AM
>> To: AstroPlanner Beta Testers
>> Subject: Re: [APBeta] Moving the Observation database to another machine
>>
>>
>> On Jul 7, 2009, at 4:52 PM, Paul Kemp wrote:
>>
>> > I have been talking to Paul about this issue, in the last month, off
>> > group.
>> >
>> > I now do not have my Observation Database on my laptop. It got to a
>> > point where it was impossible to start the program, due to
>> > Astroplanner looking for original plans. They in fact exist in the
>> > proper directory. There is something seriously screwy with the look-
>> > up function.
>> >
>> > My take is......remove all plan path references to the observation.
>> > Just note the plan logged from as a text field with the file name.
>> > Remove the link.
>> >
>> > Any other thoughts?
>>
>> I can just not do the startup test-and-fix exercise and, if a bogus
>> plan path is found during normal operations, give the user to option
>> to fix it then (which would also fix any other references).
>>
>> I will investigate.
>>
>> Paul R.
>>
>> _______________________________________________
>> APBeta mailing list
>> APBeta at lists.astroplanner.net
>> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net
> _______________________________________________
> APBeta mailing list
> APBeta at lists.astroplanner.net
> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net 





More information about the APBeta mailing list