[APBeta] Image database problems

[Paul Rodman]

On Apr 4, 2009, at 10:49 AM, John Grismore wrote:

> I'm getting this same FOV problem on my iMac with 2.0b30.  I hadn't  
> been working with V2 until this week when I downloaded 2.0b28.  Had  
> a problem with Astorb and didn't proceed, so I don't know about any  
> versions prior to b30.  I tried removing the image database and that  
> didn't help, but when I removed the resource database the problem  
> disappeared.  So now the question is, how do I "unbork" my resource  
> database so I don't have to enter all that information again?

The FOV problem is entirely (?) unrelated to the resource database, so  
you can put it back. I suspect the problem "went away" because it's  
actually timing-related and can appear and disappear at any time. The  
bug has been fixed for V2.0b31 which I will put out later today.

The "borked resource database" only appears to be a problem for Paul  
Kemp and I'm trying to figure out what is causing that.

Paul R.


>
> JohnG
>
>
>> You are still a cry in the wilderness.
>>
>> I'm pretty certain your Resources Database file is borked.
>>
>> Did it work on b27 but not after?
>>
>> Can you find "AstroPlanner Resources" and send it to me again. Make
>> sure it's the V2 one. It should be in a folder here:
>>
>> C:\Documents and Settings\Administrator\Application Data\AstroPlanner
>>
>> (That's on Win XP. "Administrator" might be your login name)
>>
>> Paul R.
>>
>> On Apr 3, 2009, at 09:44 PM, Paul Kemp wrote:
>>
>>> Paul,
>>>
>>> Is the problem I reported related to the ones you are working on
>>> since b30?
>>>
>>> Or am I still the resource problem child?
>>>
>>> Paul Kemp
>>> 13.1" f5 Reflector with Argo Navis & Paracorr
>>> Auckland, New Zealand
>>> 36? 55' 09" South, 174? 43' 30" East
>>>
>>> --- The Southern Sentinel ---
>>> www.southernsentinel.co.nz
>>>
>>> Checkout my Twitter: twitter.com/pulinski
>>>
>>>
>>> On Sat, Apr 4, 2009 at 5:39 PM, Paul Rodman <paul at ilanga.com> wrote:
>>> You're right. Ouch. I think that might be a late change I made to
>>> the threading mechanisms.
>>>
>>> Looks like 2.0b31 is on for tomorrow.
>>>
>>> Paul R.
>>>
>>>
>>> On Apr 3, 2009, at 07:33 PM, David Crum wrote:
>>>
>>> I am not getting any crashes, however, my FOV field remains a solid
>>> white, the item (galaxy in this case) is not displayed, nor any  
>>> stars.
>>> I can move the cursor around in the field and I can see that it is
>>> going over objects in the field by the display at the bottom (GSC
>>> stars, different NGC objects in same field).  I have deleted the  
>>> image
>>> database and the behavior remains.
>>>
>>> On Fri, Apr 3, 2009 at 8:58 PM, Paul Rodman <paul at ilanga.com> wrote:
>>> It would seem there are still image database problems, one of which
>>> I can
>>> reproduce here. However, I'm struggling to understand _why_ it's
>>> happening.
>>>
>>> Meantime, if you are getting odd crashes you might profit by
>>> deleting the
>>> image database and letting the app rebuild it again from the old
>>> cache:
>>>
>>> a. In AP, use Help->Where's My Stuff... to locate and Reveal the  
>>> image
>>> database.
>>> b. Quit from AP.
>>> c. Delete the database (Image database.db)
>>> d. Restart AP.
>>>
>>> I will continue scratching my head. If I resolve the issue, 2.0b31
>>> will
>>> surface sooner rather than later.
>>>
>>> Paul R.
>
> _______________________________________________
> APBeta mailing list
> APBeta at lists.astroplanner.net
> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net

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