I am too lazy to see if this has been posted before.
Here's my suggestions for changes:
1.Clear mood to blank after each post (or have the option to)
2.Go back to default journal after each post (love those personal posts to unrelated communities, heh)
So yeah.
Here's my suggestions for changes:
1.Clear mood to blank after each post (or have the option to)
2.Go back to default journal after each post (love those personal posts to unrelated communities, heh)
So yeah.
Profile
ijournal- iJournal: Official LiveJournal Client for Mac OS X
- iJournal Home
Comments
I give that a serious seconding.
And a second for the mood change.
Great program, though, makes my life much easier.
The only real issues with the 1.60 testing release are with friend group modification. That still needs work. Normal posting should work, though, so you may be able to use that.
http://www.student.cs.uwaterloo.ca/~jmdisher/ijournal.dmg
Check it out if you are interested and tell me if there are any glaring bugs. (The friend group modification stuff is quite broken and I know about that but there may be some other rough edges which I am unaware of).
It seems to be an issue with some old settings, I think, which part of the program is picking up and using as if it were still the old design (that is, assuming that it could use a string where an array is currently expected).
I am not totally sure how to proceed with this issue. I did have an idea to make a special build which would give me specific crash lines which I could send to you. I may have time to do that later on today, actually. It just requires me writing a little app to pollute the code with tons of debugging data. I was going to try to do it conservatively but it will be easier to be liberal about and it may even work better. I will see what I can do.
http://www.student.cs.uwaterloo.ca/~jmdisher/ij.dmg
NOTE: using this build of iJournal will dump TONS of output into the console log files! This isn't a problem if it isn't used often but using the build regularly could start to use a lot of drive space to store the traces in the logs so don't use it regularly. In fact, if you are comfortable with running Cocoa apps from the command line, that is preferred since you will be able to redirect the trace data so that it never stays in the console. (what this build does is write a line of output to the console every time a function is called - so this is a large amount of output).
That said, try running this and then quitting as soon as you realize that the problem has been duplicated. If you run it from the command line, send me the file containing the full trace (if you need more contact data, get in touch) or, if you are running it normally, post the last 100 (more or less) lines of the Console.app dump in response to this.
Thank you very much for helping me out with this problem.
and thanks, i'm glad to help.
So, if you are in the same directory as the iJournal application, you could type something like:
./iJournal.app/Contents/MacOS/iJournal 2> output.log
first error occurs at 2004-07-04 20:50:22.356; it can't make the connection for the newVersion action. technically, this shouldn't really matter.
next problem at 20:50:22.739, following which is that "selector not recognized" error (note: it's under -[iJournalController _extractArchive:], which isn't the thing that normally shows up in the console)
at 20:50:30.955 is our predecessor to the real problem. i'm no programmer, but i have a feeling that because the extract failed (see previous line), now it's failing to insert the values it was supposed to extract.
later, I tried doing Login As... and the result was 20:52:17.637 iJournal[13995] *** +[NSArray arrayWithObject:]: attempt to insert nil . i clicked on the little arrow to view the drop-down menu for usernames, and there was nothing there! absolutely nothing. not only do I have 2 usernames, even if i had just one it should show up.
at the end, I think that this build is having problems with the Keychain. it seems that it can't retrieve the usernames and passwords, and thus is unable to log in, because it has no data to send.
hehe....now how close am I to being right (w/no programming experience)??
There are some issues with the 1.60 use of the key chain since I am trying to come up with some solid rules about exactly what needs to be put there whereas the earlier implementations would just stick the data there. There is likely some problem there.
Thanks for the log, I will take a look at it.