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