[lisak]

Ooooh, heavy report! - my comments are below

-When I pop in the SD card I need to hit a button (any button, seemingly) before the program will actually pop up. Otherwise, it will just sit on the same screen.

I know - this always happens for a while, then suddenly the problem mysteriously disappears and program is starting normaly. Somehow I'm in doubt whether the code itself has to do anything with it - actualy, the dictionary screen should pop out before a program code itself is executed. I'll try to do some tests to find out where exactly it hangs up.

I also have to hit a button (any button again) after searching to get the definition to pop up.

Hmm, I haven't encountered this one yet.

it seems like it might be a good idea to move all of the program's functioning to the internal memory, with the autorun script on the card serving only to point to the script that's on the Reader and launch it.

I know about the battery drain (I learned it the hard way - today I left my reader open with Dictionary running during the night and in the morning the unit was completely dead w/ some weird residuums at the screen - it scared the hell out of myself), but I am not sure if the sole fact that application is running from the card is causing this.

Anyway, I can shift autorun.js to internal memory, but autorun.xml has to stay where it is (I can use symbolic link to redirect it elsewhere, but card would be accessed anyway). I am still trying to find out how to start application without using autorun functionality, but it's only realizable through a hack, which is rather risky with 505 and somewhat difficult.

Finally, is there a way to make the "exit" button not also send that input to the regular Reader firmware?

I am afraid that the answer is "no", because I believe that "exit" from the book actualy happens even before dictionary is launched (when you insert the card, current viewer is interrupted, "main" application pops into foreground and then content of autorun.xml is evaluated). And I suppose that if we ever get the dictionary running without autorun.*, you won't be able to start the dictionary while reading at all.

...several of the problems (both of the "have to hit any button to get it to work" things and also the "menu button" one directly above) seem completely fixed when I start the program over again. I am working on trying to reproduce these again, but it does seem to have to do with it running differently after the first time...okay, so...

See? Told you so. Don't be afraid, these glitches will return. But if you do find out what combination makes this one pop out, let me know.

in fact, I'm thinking that this whole situation would be best fixed by disabling both the next/previous word buttons until after a search,

Good idea. I still consider saving the last searched term (maybe last nine of them and access them via buttons...?), but I am not sure if anybody would find it ever useful (think 80/20 rule). This idea of yours might be a good quickfix.

Oh, and of course I just had to think of one more thing: I already said that the new version needs to be the one that's linked to in the first post (old one doesn't work at all on the 505, and I didn't check to see if Clemenseken changed this yet so forgive me if that already happened)

This is up to Clemenseken... I'd recommend to put a link to http://code.google.com/p/dictiolaunch/ there, where the latest version resides (alas, for 505 only...) and where also documentation will should be stored. :