[spooky69]

That all sounds good to me. To answer your question (and my own, now that I think about it) I was using the 0.85 version of the program with the original dictionary text file I posted on here a few pages back (I deleted the whole directory when re-installing the 0.85 version and I only had the old version at hand). I suspect that if I went back and used your wb.txt file again, the problem would go away. [Just tried, and it did fix the problem]

A couple of other hang-ups/suggestions/musings:
-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 don't remember if the first version of your re-write did this, but I know that Clemenseken's didn't. It does still load automatically when I start up the Reader, which is actually another little something that I'd like to see gone, though I understand why it happens.

-Yikes, just noticed this one: I also have to hit a button (any button again) after searching to get the definition to pop up. This was actually going to be another error to report, because it seemed like some of the results were showing up much slower than they should have (like "ant" and such). For now, I can just hit enter twice in a row and it will pop up after it finishes the search. On the upside, I can see now that this search is actually much, much faster than I thought it was when I posted my first impression.

-Speaking of start-ups, is there any way to get the actual script that's running onto the Reader itself? You may remember a post where I found that leaving the program open drains the battery very fast (about halfway down in 2-3 hours on my 505, I think it was), probably because the program is cycling while it waits for input. I haven't tested for any battery drain on the newer versions, but if it's possible (and doesn't impair the start-up time), 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.

-Finally, is there a way to make the "exit" button not also send that input to the regular Reader firmware? In all of the versions, hitting "menu" to exit program has also made the corresponding screen pop up when I'm back in the "main area". Since this is almost always going to be while I'm in a book, it has the potential to cause problems. Last night, it took me back out to the table of contents I was using on my reader, and sometimes you can't get back from that screen to where you were in the book without having to re-navigate back to that spot.

-Okay, wow, here's a whole big 'nother thing: 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...

There are a lot of variables here since I've been re-installing and changing dictionary files around, and I can't reproduce these errors again yet (restarting and doing a device shutdown didn't do it; reinstalling might but I'm about done messing around for today), but I think the fix has something to do with doing my first search after installing the new dictionary file and then restarting the program, since the errors happened consistently until I did that, at which point they stoppd. If this becomes a problem, I can be a little more thorough in trying to track down the caustation of the problems I had since I pretty much remember all of the steps that led up to it. Thing is, I'm pretty sure all of the errors that disappeared were happening last night when I was using 0.85 and the old dictionary file...I'll maybe report back later after doing a full deletion and re-install with 0.85 and the current wb.txt.

So, how's that for a really long, confusing list of interconnected troubles? I did just realize one more that's very easy to fix: hitting the "left" button on the directional pad when you don't have a search term (like I keep doing since I was used to old button configuration [the new one works much better for me by the way; thanks again]) makes it "freeze" up for about 10-15 seconds as it looks for a previous term behind nothing. You should just disable the "previous word" function until they've done a search (and it doesn't do the same "freeze" if you try to go to the previous word from the first line, so that's okay). You might still want to leave in the ability to use the "next word" button without having done a search, though, since that has some slight usefulness if somebody had a short list of somethingerother and wanted to scroll through it. In fact, you might just want to make the "previous word" button go to the last line of text file depending on how long the delay is...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, since if somebody's pressing those right off the bat, it's going to be a mistake 99% of the time and any delay while that line is dregged up out of the text file is going to be frustrating for the user who isn't trying to look up "a" or "zythum". Was that a long enough explanation of my thoughts on the next/previous buttons and their role in the dictionary program before a search has been done? Maybe this is a problem best left to a future "user settings" feature.

And one other thing: after using the dictionary a few times, I really think that automatically clearing the input line when a new letter is entered after a search is probably the best default option. Leave up the definition in case the new input was an accident, but I've already had several instances where I spend a few moments typing out a new term and look over and find I'm about ready to search for dogrock or saxaphoneniggard.

So, there's a bunch of stuff. I'll try to pin down what was causing those problems that went away, but that will have to wait until I'm less frazzled from typing about this program so much!

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), but I'd also suggest that the next version's archive include a text file with installation instructions and a short user manual, since otherwise people might have to track that information down in the thread. OUT