[APBeta] v2.0b19
Paul Rodman
paul at ilanga.com
Thu Feb 5 17:11:51 PST 2009
On Feb 5, 2009, at 04:12 PM, Anthony Tripodi wrote:
> Thanks for answering so quickly, Gentlemen.
>
> Here's what I did:
>
> I used the link that Paul sent, the one that announces a new build.
> It was 18. I clicked on the OS X version, and downloaded the new app
> to my desktop. When it opened to the finder window that shows the AP
> app and the little blue folder, I dragged the AP app to the blue
> folder. "Do you want to replace earlier version?" Yes.
>
> I close everything out. I then launch AP. Normally, everything goes
> well. But this time, I got the crash. I did not investigate what
> happened until after I sent the bug report. So, since things were
> not working, I started to manipulate files; nothing dangerous, I
> just wanted to investigate the behavior of the crash by poking
> around in the blind. It may be interesting to note that when the app
> crashed, the window behind the crash window was the setup wizard.
>
> Then, Paul sent the newer b19. Since I was having so much trouble, I
> trashed b18 before installing b19, but I kept all of the data in the
> application support folder. B19 installed ok, but would not read my
> preferences or resources. Catalogs and saved plans were OK. I had to
> re-enter all of my preferences and resources. I saved a new "Test"
> plan to see where AP would save it to. It saved it to my users
> folder; not in any existing AP folder, mind you, but appended it to
> the bottom of the list. When I used AP "help, where's my stuff" to
> find it, AP crashed. I trashed the "test" folder and created a new
> "test" using the plan creation wizard, and use the "save as"
> command. This time, AP saved it into a folder in "documents".
>
> All is working properly now. I have closed AP and opened it several
> times, all with the same pleasing response. Magic.
What can happen (on Mac OS X) is that if an app crashes, it can leave
files in a state where they can't be read. This can usually be
resolved by running the same app once or twice more, or by logging out
and in again, restarting, etc.
This might be the case here.
> The FOV magnitude problem still exists. I don't know if you tried to
> fix it yet, but if you did the problem has returned.
Nope. I assume you mean:
<http://www.astroplanner.net/reports/details/1700/1715.shtml>
in which case it's still open.
Paul R.
> V1 no longer exists on my machine. I trashed it just before I
> installed V2. All the stuff in the AP folder was from V2, perhaps
> corrupted by 18.
>
> Thanks again.
>
> Tony
>
> Paul Rodman wrote:
>>
>> On Feb 5, 2009, at 01:10 PM, Anthony Tripodi wrote:
>>
>>> Hello, Paul.
>>>
>>> V2b19 opens ok now. But...
>>>
>>> It has installed as if it was brand new. It will not recognize any
>>> resources or preferences. What's worse, I still have all
>>> preference and resource data in application support, but when b19
>>> installed itself, it installed not in the Astroplanner folder in
>>> Applications, the program installed itself and replaced the
>>> Astroplanner folder, thus replacing all the previous data. All
>>> lost. No matter to me, but others may have a problem.
>>
>> (Note: Anthony is a Mac user)
>>
>> You dragged the AstroPlanner app to your Applications folder,
>> right? Even if you already had a folder in there called
>> "AstroPlanner", it should get overwritten, since the application is
>> called AstroPlanner.app (although the extension is probably hidden
>> on your system).
>>
>> What was in the AstroPlanner folder? V1?
>>
>> AstroPlanner V2 keeps all its stuff in ~/Library/Application
>> Support/AstroPlanner/, not in the Applications folder.
>>
>>> I still have the data in the support folder. I copied that to a
>>> new Astroplanner folder that I created, placed the AP program in
>>> that folder, rebooted the computer, and restarted AP. No help.
>>
>> No. AstroPlanner V2 _always_ uses the above folder. It ignores
>> where it's running from.
>>
>>> I still have to re-enter all data as if the program was new.
>>
>> You can use the V1-to-V2 Converter app on your V1 files.
>>
>>> So, I tried both ways: I allowed AP to install itself over the
>>> existing previous version, and I tried to move the data files
>>> about manually. All with no positive result.
>>
>> I have not seen this behaviour myself (yet). I don't have much of a
>> clue what's going on (assuming I understand the problem).
>>
>> 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