Hoo, lot of feedback today - thanks all.
ipsi - no chance for "bookmark selected line" in Beta 7, though we may be dropping the modification date check (along with switching to just filenames) since it does seem like some systems change the modification date when you move the file - as long as the file's the same size it's unlikely the bookmarks would be invalid. Of course the ideal would be some sort of system that went by paragraphs / section names or somesuch rather than byte positions, but that's not feasible on any PDA yet. We'll hammer away with memory-eating background tasks and see what we can find, though it may be that there just isn't enough memory on a typical Palm for Pleco to coexist comfortably with more than a couple of background applications.
weight - we've gotten a few reports of problems with the converter utility like this, but we haven't yet been able to reproduce them here; at some point we may just give up and at least initially tell people that if they encounter a crash they can send us the file and we'll export it for them, though hopefully we'll figure this out before 2.0's released. The reset on exit looks like a bug too... does it make any difference if you export to an SD card instead of to internal memory? The whole thing's really perplexing since most of the code in that converter utility is taken directly from the 1.0 exporter (which doesn't seem to give people the same problems). If putting the file on an SD card instead of internal memory doesn't help, send us your flashcard files and we'll export them for you (and see if we can reproduce the problem on a TX here using your files).
Fleminator - I'm seeing #1 too now - definitely a recent development, must have been from one of the changes we made to improve tap/tap-sel accuracy. #2 is probably happening because of the new system we use to cache profile/scorefile names (so they're not as maddeningly slow as they were in Beta 5) - does the list still populate slowly or is it faster now than it was in Beta 5? #3a yes, deleting a scorefile will never affect any profiles linked to it - we probably should put the name of the thing you're about to delete in the confirmation box, actually, just to make situations like that a bit less nerve-wracking. #3b are you using frequency-adjusted or repetition-spaced lately? On #4 a quick Google search brings up 8.4 million results for "flashcards" and 8.3 million for "flash cards", so if it's a spelling mistake it's an awfully popular one.
#5 we've actually been working on all weekend - it's still not perfect, but the mistakes tend to be concentrated in a few areas (and a lot of them were actually created by bugs in the encoder program rather than in the original audio files) and we think we've found most of them now; if people keep reporting lots of problems once we've released the revised set of files we might try to organize some sort of audio-specific testing thing here on the forums. (everyone gets a thousand words or so in the form of a flashcard list, maybe, if we can convince people to do it)
#6 we'd love to do but even if the UI part of it is easy it's tricky to implement on the back end (much harder than in New Session due to the different way the queries are structured) so that might have to wait for 2.1. #7 we thought we'd fixed, we'll take another look but that's definitely in the category of things-that-can-wait-for-2.0.1 at this point. #8 here's something that might work: search for all flashcards with dictionary == your user dict, export them to XML (with user dict definitions included - use the Export button in More Options to export a list of search results), delete the cards, delete your user dictionary file, then import that exported file back into Pleco with definitions being stored in the user dictionary - that should bring back just the flashcard-linked user dict entries and no others.
#9 it sounds like it couldn't access the flashcard file from wherever it was accessing it before. Go into FileZ, Preferences, and make sure the "Show Hidden Volumes" option is checked, then tap the Close button and View and Edit Files again and you should see your hidden internal volume listed as the second item - if you open that up, is there another flashcards file in there? If so, send me that file and we can check to see if it was corrupted (which would be very bad) or accidentally still marked as "in use" (not so bad). If there's no other file in there, it might have been accessing it from the SD card before too - go into Preferences, Search Paths - what storage location is selected in the list at the bottom of the screen? PlecoMover as ipsi suggests would let you easily move around the files, but if the file's getting corrupted if it's in internal memory and the palm resets that's definitely something we'd need to investigate.
#10 I'm seeing here too, guess our fix for that problem only worked with All. #11 I'm not sure about - with truly colossal numbers of flashcard categories (say 200 or more, which we've definitely seen in some people's files) even on the Advanced screen you probably wouldn't want to see them all. We're still tracking down a few glitches like #12, there are a couple on Pocket PC too. #13 the data comes from the
UniHan database and ranks cards from 1-5 (1 being highest-frequency, 5 being lowest) - I believe they originally generated it based on USENET postings. At some point we really need to get some more nuanced frequency data in there so we can use that to do things like sort search results...
ldolse - it shouldn't be hanging the whole PDA, that's true, I just wanted to eliminate the possibility that it was a bug involving corrupted data - my best theory now is that it's some sort of a software conflict. What firmware / ROM version are you running on your Touch Dual? We only have a regular Touch here but maybe we can reproduce it on that - and if I haven't asked you this lately, what third-party software (if any) do you have running in the background / as a system extension at the same time as Pleco?
Thanks for the reminder on the stroke order issue. With the large entry copy, how did you manage to copy out more than one page of text? Using the hardware scroll buttons? The reader issue sounds like we just need to check for an open reader window / not open another one if it's there, something we probably should have been doing several betas ago. We'll check on this ZTA4 bug, I think we've already got it installed on something else anyway. I'm not sure if integrating a popup definition screen into the user dictionary editor would make sense, but maybe at least some sort of simple character-to-Pinyin converter (with popup lists in the case of multiple pinyin variants).
Full-text indeed doesn't work with single-character searches - there'd be too many results for too many characters, though maybe something we could look at for a post-Palm release. Good point on the pound sign, not really any reason to leave it in in those cases since full-text always autodetects the search language anyway. You can actually delete it just by tapping on the full-text toggle button again, though I agree it probably should work on a highlight-and-clear too.
The dictionary switch bug in Edit Card has been noted elsewhere - the 'sou' icon exists because at the moment that screen doesn't auto-update when you change the search term and hence there needs to be some way you can try a different search in the same dictionary. Reveal fields separately was mentioned somewhere before, I think, though we have it marked as not-reproducible so we'd better take another crack at it. Skip Duplicates can't determine whether or not something is a duplicate until you select it from that list, since it's possible for example to have a single character with several different Pinyin transliteraitons (in which case it wouldn't be a duplicate if you picked a different one from the one in the existing card) - do those different entries have the exact same headword/pinyin or do they vary in some way?
Manage Cards already can sort alphabetically by Pinyin, just choose "pron" "ascending" in the "Sort By" section of the Settings screen. Making Guifan less prominent I'm not sure about - if an entry isn't in ABC then it isn't in Oxford either in which case it's either going to be in Guifan or nowhere (unless you're using Adso in which case you'd already want to customize that list to put it somewhere higher than fourth) and it's better to have an entry from a Chinese-Chinese dictionary than from none at all. Imports already can be canceled, just tap on the "Stop" button (which Start changes to after you tap on it). With the word wrapping issue, by any chance does a scrollbar appear in the definition after you've revealed it? Assuming there's a space between the ] and the x it should break on that space regardless, so the best reason I can think of why it wouln't would be if it didn't have enough space to fit that last bracket on the first line, which could certainly happen if a scrollbar appears once the entry is revealed (causing the text area to shrink).
Good point on exiting sessions. A "fix later" checkbox seems a bit too specific - seems like it would be easier to just create a "Fix Later" category, put it at the top of your flashcard list, and then toggle it by tapping-holding on the category button. It may be a problem a lot of people have but I hate to add yet another confusing checkbox when just creating a category isn't really any more cumbersome. Double-clicking / pressing the center button to bring up Card Info are both good ideas but definitely in the "maybe" pile for 2.0. Popup definition already should work once the card is revealed - just select and then tap-hold on the word you want to look up to pop up a menu that includes that and several other options.
I'm not seeing much of a problem with English font sizes in the entry list - any chance the characters might just look small because you're used to seeing them magnified? Good point on the history list. Adding "send to reader" to the context menu I'm a bit unsure about, because it seems like that would be for sending the currently-highlighted text to the reader than the whole entry (which I guess would be useful in its own way but less so than sending the whole entry and hampered somewhat by how difficult it is to highlight multiple pages of text).
There are actually two different kinds of superscripts in Guifan, the regular non-circled ones are for multiple entries with the same headword (and indeed probably should show up with TC as well as SC headwords) while the circled ones only appear in single-character entries and are for pointing out which definitions a particular character variant applies to (for those pesky one-simplified-but-several-traditional-character words).
ipsi again - good point on moving Send to Reader, probably makes sense to move Play Audio too - as I recall there used to be a lot more options under Dict and those ones were put under Edit originally due to lack of space for them elsewhere.
ldolse again - yeah, we went halfway on Unihan-as-a-dict and should probably just finish the job and make it a full-fledged dictionary along with the others; as long as it's not accessible by just tapping on the cycle dict button it shouldn't confuse anyone too much. (and just using it as a fallback is already going to get us a bunch of "what's this darn UNI icon" e-mails)
Fleminator again - yeah, PlecoMover is really as much for our benefit as anything - makes it a lot easier to walk users through moving around / backing up databases. PlecoMover only sees databases in the root level (/) of an SD card, so make sure your flashcard file is there and not in a subdirectory. Good point about up/down scroll, it should at the very least be available along with the other options on the flashcard button settings screen.
weight again - looks like we created another zhuyin bug in the course of fixing that earlier one you mentioned - dots were supposed to be appearing after neutral tones instead of first tones. And don't worry about being pushy, I have almost no experience with Zhuyin myself so if someone doesn't point out these problems they're probably going to go unfixed. We'll take a look at this edit card issue. Remove Card should be assignable as a hardware button, not sure why it's not showing up in preferences...
stephanhodges - the reader searches for files in the same directories as the rest of pleco, so you'd configure that in the Search Paths section of Preferences. We'll check on this left/right issue on our Tapwave unit here. What do you mean by "the 4th word"? Good point on Adso, particularly since some people may want to put Guifan in the reader as a fallback it makes sense to not switch dictionaries unless they ask it to. (though I'm sure making this change will result in calls from others to either change it back or provide a way to have a different dictionary search order for the reader than for the main dictionary, like there already is for flashcard imports - all in 2.1, folks)
grabolous - glad to hear it's more stable. Did the soft reset happen when you were configuring the flashcard buttons in Preferences or in the Display tab of the Advanced Settings screen?
dom - that's weird... have you had any problems with this memory card before? Any chance the files might not have copied completely, say if the memory card accidentally came loose? How many other files are there in /Palm/Launcher? Any files from a previous beta? MakePlecoDict won't be out until after 2.0, can't justify holding up the main product to finish it, but you can actually create pretty good-sized user dictionaries using the flashcard importer now - unlike the old created-on-device dictionaries these are sorted and generally quite stable / reliable. (and do indeed use SQLite) MakePlecoDict is going to use essentially the same format, actually.
sfrrr - resetting the preferences per ldolse's suggestion should help, yes. The OK button issue sounds like the return of the old button-turning-into-an-X issue from 1.0, hopefully we can find / fix it once again.
kkuguru - are you sure you mean "jiahua"? I'm not seeing any entries for "jiahuan" in anything except Adso, and then only as part of longer words.
sych - no need to do this for Beta 6, actually, the formats remain the same.
.