Closed GoogleCodeExporter closed 8 years ago
BuckNut,
Thanks for the report! I can't replicate the crash here, and I'm using the most
recent version (not surprisingly :). Oh, wait, I just looked at the crash
report a
little more closely. Did you use the "restore defaults" button previously? Try
trashing your prefs
(~/Library/Preferences/com.fullyfunctional.blazingstars.plist)
and then restart BS. I was having trouble with encoding the color well values
into
the preferences, which I solved in the most recent versions (see issue 37 for
more on
this), and this looks like the error I was getting before.
Let me know if that helps!
Original comment by steven.h...@gmail.com
on 1 Feb 2010 at 9:08
Yeah that fixed it..I've been reading the updates here and I remember seeing
something about trashing the
prefs file..just forgot I suppose..oops.
Here's something really strange though. I'm now unable to open the 'Windows'
Tab if I'm running BS via the
.dmg. BS doesn't crash, per se, but the prefs window freezes. I can reopen
the prefs window via the menulet
and things seem to work fine, but every time I click the Windows tab it locks
up on me. It still quits just fine,
and I can't seem to find anything strange in the console (this could easily be
another issue but I thought I'd be
efficient about things and keep it here :p ).
Strangely, though, if I'm running BS via XCode things work swimmingly :/ I'm
guessing the .dmg just wasn't
updated after you altered the 'Windows' tab code?
Original comment by BuckNu...@gmail.com
on 1 Feb 2010 at 9:27
BuckNut,
Actually, the Windows Pref issue was solved after the .dmg version was
released; I
don't update the .dmg every time I fix an issue, just when I do an official
release.
That will be coming soon (hopefully tonight, 0.9.9b22), and then you can do an
update through BS to get the latest version which will hopefully iron all this
out.
Original comment by steven.h...@gmail.com
on 1 Feb 2010 at 9:30
I assumed as much..no rush :)
Original comment by BuckNu...@gmail.com
on 1 Feb 2010 at 9:33
Okay, 0.9.8b (22) is out and this issue should be resolved.
Original comment by steven.h...@gmail.com
on 2 Feb 2010 at 5:22
Original issue reported on code.google.com by
BuckNu...@gmail.com
on 31 Jan 2010 at 10:47