sfrrr - yeah, those were the days; really the issue before was Pocket PC was that we were expecting it to do some things for us that Palm OS didn't; with Palm we've taken it upon ourselves pretty much since day 1 to develop our own versions of operating system features that Palm either doesn't do or doesn't do very well, so now that we've adopted the same approach with Pocket PC in 2.0 (rather than our earlier strategy of doing the best we could with what Microsoft gave us), the core, fundamental stuff that we can't replace like memory management / filesystem / etc have proven to be much nicer than their Palm equivalents. We'll probably be taking that approach from day 1 on iPhone and other new platforms - just because Apple doesn't offer copy-and-paste or text highlighting doesn't mean we can't.
Still working on a better system for storing history but hopefully we'll have that in place soon. (probably should just dig up how we did it in 1.0 - we basically threw out all of that code on PPC for the new version and we may have discarded a few clever ideas in between all of the haphazardly-implemented workarounds and such) With IA, if you can't get it working the normal way you could always try the look-up-text-in-clipboard option instead - just one or two extra pen strokes really, and with a whole sentence or paragraph that it can look up for you in the reader it might actually be faster that way.
Fleminator - glad it's sort-of up and running. With the missing cards, are you sure some of those weren't duplicates? When files get corrupted in SQLite it's usually more obvious, 10,000 entries down to 900 or something like that (or a table wiped out like profiles or category assignments). The cards should show up by default in the same order that they were in in 1.0 (which is actually just the order in which they were created in 2.0, but that's how the import file is sorted) - if you compare the two lists, do you see occasional missing cards or is it just a big chunk somewhere that's disappeared? Anyway an experimental better-Palm-database-system release should be out in two or three days so you can try again with that.
gato - glad it seems solid so far. Imports generally slow down the more cards you add, since it takes slightly longer to update the indexes the longer they get - the Centro might also use newer / higher-speed flash memory than some of the older models like the TX. Cards exported from 1.0 are tagged with dictionary IDs so they'll import to the same dictionaries in 2.0 - the best way to move them over to Guifan would be to use the remap command in Manage Cards' More Options screen after you import them. The reason for the two Dicts lists is that the Import one is a permanent mapping (i.e., this is the dictionary which this card is linked to) while the Dicts option in Advanced tries to dynamically remap cards to a different dictionary for a particular session, so if for example you want to try reviewing with Guifan but not move everything over to there permanently yet you can do it that way.
The plus and minus icons don't scroll between flashcards, they add and remove them to the category selected in the popup menu next to them. (should both move the highlight down) Not sure if we'll get around to adding hardware button support to that screen for 2.0. The plus icon is actually just to create new cards, to edit a card you tap the i (= card info) button and then tap the Edit Card button at the bottom of that screen. The first screen may actually be getting more crowded in the next version since we're probably adding an "Organize Flashcards" screen that looks more like the 1.0 manage one (a lot of people are unhappy with the new interface) - I think as long as there's still an extra-large button to start a new session it's probably OK, I suppose a few options like Import/Export could be folded into a separate screen but then people would have to wade through two confusingly-crowded screens to get to those options instead of just one
Profile affects Manage Cards too, since that screen uses whatever scorefile is selected in it, and also affects Import since scores in import lists that don't specify a specific scorefile name (like the ones generated by the 1.0 converter) go to whatever scorefile is associated with the current profile, so they're a bit more than just a set of test settings.
There's an option in the Button Actions section of Preferences to use the up/down arrow buttons to scroll through pages instead of lines - we're debating whether to make that the default behavior. The definition shows up either way, that option just puts it in a separate window instead of on the main one, so I'm not sure how we can really make it clearer - something more action-oriented, like "Pop-up definition in separate window," suggests that the definition won't show up at all if it's not checked, which seems more confusing. The reader's actually supposed to remember the last position already but doesn't due to a bug.
kkuguru - thanks for identifying the specific action that causes the input field to lose the keyboard focus, sfrrr mentioned it happening occasionally before but we didn't know what exactly caused it - should be easy to fix now that we know where it's hiding. With that multi-choice issue, were the words all of an unusual length, say 5 or 6 syllables? How may cards were in the session? How many cards in total are in your flashcard file? With KuanDai, if you check the box to allow example sentences in flashcards in Preferences that should get those entries to display normally - we haven't gotten all of our data files coded up correctly for that feature yet (and may end up disabling it and punting it to a future release). Multi-wildcard searches go a lot faster with single-character wildcards than multi-character ones, but it's true they're not that fast in general - tough thing to speed up since the standard methods for wildcard-indexing text don't really work well with Chinese.
Harm - yeah, we weren't sure what to do about that aspect of multiple-choice; it seemed like if someone had already gotten the card partially wrong (and was therefore going to get it scored incorrectly) there was no point in asking them about the second part of the question when it wouldn't affect their score. Anyone else have any feelings on this one way or another? With the missing choices, it could be an issue of the lengths of words getting calculated incorrectly - that would certainly explain the user dictionary connection anyway. Are these unusually long entries, say sentence-length ones? If you go into the Advanced/Settings screen in Manage Flashcards and search for cards with length = 0, do any come up?
