Beta 2 Bug Reporting

ipsi

状元
Cool, changing the creator code with FileZ fixed that particular problem. Also, the problem I had on exit wasn't that it crashed, but that it stopped responding, and I had to do a soft reset. Not very fun...

I also get random crashes after adding flashcards or playing Audio. I usually have to do it several times in a row before it actually crashes...
 

ldolse

状元
My bug list:
  • English-Chinese search doesn't remember last viewed word and dictionary - C-E does though
  • The back and forward buttons don't flip across languages the way 1.0 did
  • ABC dictionary is missing the initial entries which begin with the capital letter 'A' from 1.0
  • Handwriting recognition requires you to wait momentarily after the first stroke - if you immediately enter a second stroke it won't be recorded - this is extremely frustrating. Disabling smoothing in the preferences makes no difference. This often happens on the subsequent strokes as well (every other one), but not as consistently. 1.0 didn't do this.
  • There is no way to view the character info for a 'rare' character. The character does exist in 1.0 in Unihan, so It's clear that it should be in the 2.0 Unihan DB used for character info
  • Full text search basically doesn't seem to work (i.e. no or incorrect results), when I tried to search for some chinese characters. It also forced me into the E-C dictionaries, not allowing me to attempt full text search on C-E dicts. I did see that it allowed an english text search to be done on the C-E dicts (disallowing E-C search this time), and the results made sense, though it's use was a bit flaky.
  • Toggle View/Search mode in the Dict menu - I think this is supposed to be gone now
  • The Definition highlight-tap option in Search Mode Navigation prefs only works a handful of times before failing. It will function again after a restart
 
mikelove said:
TaiwanSwedey - that's very odd, the data file has definitely been updated to say Beta 2. Any chance you might have accidentally installed the wrong application file? Not sure about that paid components message, maybe it's noticing the fact that we've only released a partial set of audio files so far.

Sorry, I just noticed I had only deleted Beta 1 from the My programs folder but still had icons for both Beta 1 and 2 left on the Start menu folder.
 
Flashcard System

mikelove said:
Wow, lot of responses here... thanks for the feedback, everyone!

The Duelist - try deleting your flashcard file (again if you already did) and you should have no trouble creating lots of flashcards in the new one. In Manage Cards, the date field is a little glitchy so go back and manually reset it to, say, all cards created after 1/1/2000 and it should show you your card. And yeah, we do need to do something about the "standard" flashcard interface along with adding the new simplified one.
Hi Mike

I Deleted The Old Flashcard File, And Have Been Able To Add Some Flashcards. :) (I Now Have 5)

The Main Source Of My Confusion With The Flashcard System, Was That On Starting A Flashcard Session,
I Was Only Presented With One Button, The 'End Session' Button.
I Have Since Seen The Familiar 'Reveal/Correct/Incorrect' Buttons.
So I have been able to run a Basic Flashcard Session. :D

Bug Report
Platform: Palm T5
Software: PlecoDict 2 Beta2

Flashcard Session
Seems To Work OK In Half-Screen Mode.
'Reveal/Correct/Incorect' Buttons Don't Appear In Fullscreen Display Mode.
Lose 'Reveal/Correct/Incorrect' Buttons Changing From Half To Fullscreen Mode.
The Loss Of These Buttons Makes The Current Flashcard Session That The User Is In Unusable.

Flashcard Session 'Display' Preferences
- Magnify Chars In Headword Doen't Work
- Reveal Fields Separately Doesn't Work

'Flashcard Buttons' Preferences
- Don't Appear To Do Anything
Mike: Could You Please Explain The Difference Between 'Default/Alt' Settings?
How Do You Get 'Alt' Buttons?

TIA
The Duelist
 
Hello Mike,

(PalmTX with 2GB SD card)

  • Changed the CreatorID using FileZ, works now like a charm. What would Palm be without FileZ? 8)
  • Increasing the search delay does help a lot, I should have thought about that myself (insert sound of slapping on the forehead)

  • Sound sometimes does not stop and I get something resembling an endless echo: for instance, go to "数码相机" and press the audio button. After playing all syllables there should be a repeating sound stemming from the last few bytes of sound.
  • In the dialog for assigning a color to a tone number I can see no way of leaving the dialog: no ok or cancel buttons, and trying to pick a color also does not make the dialog going away.
  • The radical database seems to be missing as I can see no radicals and can't select one. On the other hand this is surely politically correct. :mrgreen:
  • Some syllables are not spoken (toneless ones?). For instance, 风水: Pleco2 only speaks "feng1" and is then silent.

And just by the way: now that I had to learn that usability saiz "negated options are considered harmful" I would like to point you to the preferences dialog, section "General", option "Don't use Chinese character icons". I asked myself the first time I saw it: "what happens if I don't use the Chinese character icons? Are there then holes in the icon bar?" :shock: I would like to suggest changing the check box to a drop down box labeled "Icon theme" which contains the two options "Chinese" and "English". But then, this is just my private two cents.
 

grabolus

举人
Hi,

maybe a positive report first. Iworked with beta 2 now several hours on a treo 650 with cjkos and I had no crash.

* Often after handwriting input I get a broken screen in the normal view. There are two empty boxes on the right hand side (hiding a part of the list). When I switch to english and back to chinese, the screen is ok again, but in the area where the boxes were before the screen doesn't react any more on taps.
* I tried to define the middle button of the cursor with the command "clear", but it doesn't work.
* Could you explain the coexistence of pd1 and pd2 a bit more. The filename of the HWR and the dictionaries are the same... can they be used by pd1 and pd2 together.
* Generally: To get very good bug reports I need to know how the system should react. Some help files or documentation would give us a chance to test the system in more detail.

Good luck with the next beta....
Sascha
 
Hello Sascha,

from my experience you can use the two HWR files for both PD1 and PD2 without problems (overwriting the existing PD1 versions). Looks like an update from the company which develops the HWR engine.
 

grabolus

举人
Hi,
here are some other small bugs/things (beta2 on a Treo 650):

1. I am missing an icon to change the fontsize. (What I don't understand is that the font size numbers in the filenames are different from pd1)
2. The recent query list is always empty.
3. I don't see an effect of "append dict names".
4. I don't understand when results from several dictionaries are shown and when only from one.
5. Open Reader -> Start -> A Reset occurs.
6. I don't understand the full text search

Bye
 

FUmminger

秀才
Mike,

I tried what you suggested, but the unlock still did not stick. It seems that the unlocking consistently works the first time I open the program and fails after that.

Frederick
 

ipsi

状元
Document reader doesn't like GB2312 formatted texts. It's fine loading UTF-8 stuff (or stuff you claim is UTF-8, despite the fact that it's actually GB2312...). I get a soft reset when trying to load GB2312 stuff, but it takes a second or two, so I reckon it's definitely trying to do something.
 

sfrrr

状元
OK. Here's my feedback. For Chinese students at any level, this is the killer app. Congratulations. I am much happier with the simpler toolbars, the alternating speakers feature works beautifully, although the woman's voice sounds like a slowed man's voice. (Except for the first time I tried PD2, in which case i got a real woman's voice in there.)

However. i still can't get the settings for the toolbars to stick--that is, when I change one of the soft buttons in the toolbar, sometimes the change holds until I close PD2 and sometimes it makes no difference at all. Whatever the case, after I close and then open PD2 again, none of my changes appear.

And I've lost the automatic search function. It worked for a couple of days and then yesterday, our of the blue, it stopped working and now I'm having trouble getting any search at all. The only way to get it to search is to tap the dictionary icon and, even then, the response is sporadic.

Also, whenever I open PD2, it starts in E-C mode, rather than C-E, as I'd prefer--and the way PD1 does. I can't find a setting in or outside of Preferences that deals with this. It wouldn't really matter if PD2 did automatically detect which search language I was using, but it doesn't.

Even though I don't make much use of flashcards, I take my beta testing duties seriously, so I tried to create a new flashcard list. No go. Didn't retain a single card, didn't announce that it had added a new flashcard, didn't warn me of duplicates (probably because it wasn't saving the cards in the first place.) In the Preferences' Query page for I have ticked auto-detect search language, and it is sticking, but the feature doesn't work. Also, it takes two levels before I can start a flashcard session or manage cards. And then, of course, none of the buttons in manage flashcards works.

There is no recent search or recent word list that pops up . At least not on my Axim x51v.

I can't get the unihan dictionary to install. (I got one of those notices tha said my keyfile had been accepted by not all of the add-ons have been installed. (Sorry, I can't remember the exact wording of the error message.) I've tried moving it to the PD2 folder in Main Memory, but no go. I'll keep moving it around until it starts working.

No soft resets or any other sort.

Thanks for the great app--can't wait until all of the features work.

Sandra
 

mikelove

皇帝
Staff member
Once again, thanks for all of the great feedback. Small reminder for everyone, though: we're still not really looking for reports on minor/aesthetic issues, we're pretty much only interested in big crashing / lost data issues as described in the Beta 1 thread. All of this is very useful, but since a lot of it was likely to come out anyway in our own internal testing you don't really need to spend time reporting it yet - we'll let you know when we're at a point where we expect everything to work completely correctly. If Minor Feature X isn't working it's most likely because we either haven't finished implementing it or haven't finished debugging it yet.

ipsi - glad to hear it! And yes, the radical file is unchanged, though there's a small chance there might be a filename conflict with the old version (in which case renaming with FileZ would fix it, the software actually doesn't care at all what files are named).

ldolse - We didn't even know the C-E half remembered the last word/dict, actually; that whole area hasn't really been properly debugged yet. So that's sort of an anti-bug report :) Back and forward were just made usable the day before Beta 2 came out so there's a lot of debugging left to be done there too. Are you sure the 'A' entries are missing or is it possible they might be just be farther down in the dictionary?

We haven't noticed any delays in handwriting input in our testing - is anyone else experiencing anything like this? And which "rare" characters are you referring to? The full CJK Unified block should be covered, we don't include Extension A/B since they're not supported by our fonts or handwriting recognizer and hence there wouldn't really be any point to having the info for them. Full-text search is still very buggy, View/Search is gone but we haven't cleaned up the menus yet, and highlight-tap is actually on the way out too (replaced by a tap-hold menu as on Pocket PC) so that's why we haven't done much cleanup on that.

The Duelist - glad you've finally gotten the flashcard system semi-working. We haven't done any testing of it with display resizing yet, so that explains most of the problems you mention.. not sure about the reveal fields not working, though, it's definitely been implemented and we've even successfully tested it once or twice. Hardware buttons don't work at all yet, as mentioned in the known issues thread - alt commands, assuming we leave them in, will simply be other commands that will run if you're in a context where the default one won't, so for example you can combine reveal with correct so that pressing a button when a card is hidden in self-scored mode will reveal it but pressing that same button again will mark it correct.

haraldalbrecht - glad to hear the FileZ and search delay tips helped. We'll do some testing with this sound issue, the Palm sound code underwent heavy revisions to get the multi-syllable breakdown feature working correctly so there's a whole lot of bug potential there. The tone color dialog should exit when you select a color, so I'm not sure why it's not yet... with radicals, that file was missing in the Beta 2 archive but you can download it here (same beta username/password). Tones aren't being spoken because we didn't record toneless versions of most Mandarin syllables since they're either never actually spoken that way or sound basically identical to first-tone - we'll eventually fix this by having it just play the first-tone syllable in those cases. And good point about negative options, though in this case I'm not wild about making this an option at all; the Chinese-character icons generate a lot of complaints from people not learning characters, though, so in keeping with our philosophy of staying out of pedagogical debates it seemed like a good idea to gl along with their requests.

grabolus - not sure about that handwriting glitch, but that layout code needs some extensive debugging in general. Hardware buttons don't work yet, as discussed elsewhere, and yes, the PD1 and PD2 handwriting files are completely identical so you should be able to use either set without any problems. As for expected reactions, we're still changing enough of the design that we don't want to waste time writing documentation that will quickly be out-of-date, so this sort of very specific feedback should probably wait for a later, interface-final beta version.

Font size is configured in Preferences now, didn't seem like something we really needed to have in the toolbar anymore, recent queries are another thing we haven't implemented yet (see the Known Issues list for more of this), same goes for append dict names and multi-dict results, and reader is buggy with some file types so that probably explains that crash.

FUmminger - it definitely looks like there's something wrong with preferences being saved, sfrrr mentions the same issue as do several other people, so hopefully we'll get that fixed soon.

ipsi again - we haven't done the slightest bit of testing with the document reader on non-UTF8 yet, so it's not surprising it doesn't work - only just got that working with flashcard import.

sfrrr - thanks! Not sure what's going on with the slowed voice, but most of this other stuff sounds like it has to do with corrupted preferences, including the search not working (likely because the delay timer was reset to something very large). Auto-detect language still doesn't work very well but it's in the pipeline, like so many other things, and it should eventually do a much better job of remembering the last dict / language used too.

Duplicate checking in flashcards doesn't work at all yet, but I'm not sure why the cards wouldn't be created at all - it seems unlikely this is a database corruption issue since the SQLite code has been very very extensively used/tested outside of Pleco, but did you make sure to set Manage Cards to look for the cards you'd just created, say by making the search for cards created later than 1/1/70 or some other long-ago date? Flashcard Central was mainly intended to get rid of the unbelievably-common support question of "how do I access flashcards," the newbie-friendly toolbar layout will have a nice helpful flashcard-launching button, but I suppose we could consider adding direct links to manage/session somewhere for the benefit of expert users.
 

Sarevok

进士
mikelove said:
We haven't noticed any delays in handwriting input in our testing - is anyone else experiencing anything like this?

I also noticed this problem. Happens when I try to write quickly (a bit like grass style... within reasonable bounds of course, so that the character is still recognized correctly most of the times) with almost no pause between strokes. Then the next stroke is not drawn and I have to write it again... which almost always succeeds, as there seems to be a long enough pause between two strokes in such cases. If I try to write neatly, stroke after stroke, with some delay between them this problem almost never occurs. At first I thought that there is something wrong with my display again but it seems I am not the only one encountering this...

Never happened in PD1, I can write as quick as I want there... though I do that on a different part of the screen as I have the "bottom" option turned on, so that I don't have to switch to that special handwriting screen...
 

grabolus

举人
Font size is configured in Preferences now, didn't seem like something we really needed to have in the toolbar anymore,

I change the font size often, although I have the Treo high res screen. Sometimes the hanzi is simply too small for a beginner... With beta2 the fontsize change is effective only after a restart of pleco. Maybe other people could comment how often they needed the font size change.

Thanks
 

sfrrr

状元
Mike--About a corrupted prefs files: Is there any other way to clear it besides deleting the current prefs file and starting over from scratch? what's the name of the prefs file? At this stage, does the beta install into the registry? If so, is there any PD key that I shouldn't touch on pain of a hard reset?

I'm about to set everything back to default and try again. If it doesn't work, then I'll delete the prefs file--if I can.

Thanks,
Sandra
 

ldolse

状元
mikelove said:
Are you sure the 'A' entries are missing or is it possible they might be just be farther down in the dictionary?
I doublechecked - you're correct, they're in there, but further down. There's still some incosistencies though, as B was sorted with words starting with the capital letter 'B' at the very beginning, while 'A' is sorted so that those words show up last.
I also noticed some weirdness looking through there that there are a number of entries in ABC beginning with a slash - '/'.

mikelove said:
We haven't noticed any delays in handwriting input in our testing - is anyone else experiencing anything like this? And which "rare" characters are you referring to? The full CJK Unified block should be covered, we don't include Extension A/B since they're not supported by our fonts or handwriting recognizer and hence there wouldn't really be any point to having the info for them.
Sounds like Sarevok is seeing exactly what I'm seeing, though I'm not doing anything like grass style, just quick strokes for cases when I know the character well.

mikelove said:
And which "rare" characters are you referring to? The full CJK Unified block should be covered, we don't include Extension A/B since they're not supported by our fonts or handwriting recognizer and hence there wouldn't really be any point to having the info for them.
I'm not referring to extension A/B. What I'm referring to are rare characters that are in the full CJK block that show up in the radical output or handwriting recognizer. When I was testing out the handwriting issue a lot I entered many different strokes, which pulled up some obscure traditional character no longer in modern use in the handwriting recognizer. When I clicked on this character I discovered that it wasn't in any of the dictionaries. Because it's not in any of the dictionaries there isn't any way to get to the character info screen for that character. 1.0 was different because Unihan was just a dictionary - it shared the same lookup interface as all the others. Seems like character info needs some method to input a rare character directly without going through another dictionary entry....

-Lee
 

Ole

Member
ipsi
Document reader doesn't like GB2312 formatted texts. It's fine loading UTF-8 stuff (or stuff you claim is UTF-8, despite the fact that it's actually GB2312...). I get a soft reset when trying to load GB2312 stuff, but it takes a second or two, so I reckon it's definitely trying to do something.

Thank you: Your remarks helped me to get the reader working ...

Ole
 

roddy

秀才
I had an odd bug earlier where I noticed that the character 庭 had been replaced in one entry (it wasn't a headword, was in an example) by either 咕 or 咭. Thinking it was maybe a variant I chased it up but it seemed that the 庭 had been replaced across the board. Can't replicate it now though.

Also in full-screen landscape orientation I get three magnifying glasses across the top. I'm assuming that's not meant to happen . . . .
 
Top