2.0.3 Bug Report Thread

[mikelove]

Might have been a mixup with category IDs, perhaps some deleted / moved categories were still stored in your profile settings somewhere; I'll double-check to see if there's any execution path that would prevent the category list from being rebuilt / rechecked when starting a new session.

[mfcb]

and yesterday i tried to split hsk3 in smaller sub-categories, and i got nervous when the device went nearly unresponsive after i pressed "done", without a busy cursor... i remembered last time i also had that feeling, so i just waited and after some time the category was split...

but for my nerves it really would be better, if some visible response is there, that its working on something...

[mikelove]

A status update for category splits would be nice, though those callback updates can be kind of tricky to implement - hopefully we can manage something anyway.

[mfcb]

not necessary to make a "live" response, just a popup with "please wait" or like that would do... not even the "done" button got selected (did not turn black), it just stopped to respond to anything...

[HW60]

Is it possible to use the user dict in compounds?

[mikelove]

mfcb - that should be doable at least.

HW60 - User dicts should be accessible in compounds even now, but they're very slow - they should become much faster / more usable in the next update, though, with its vastly improved (though slower-to-insert-entries) user dictionary indexing system.

[HW60]

But the only way to choose a dictionary in compounds is to hit the dictionary button, and if the USR dictionary does not appear after circling through the dictionaries: what to do then?

[mikelove]

Hmm... go into "Manage Dicts," select your user dictionary and check the "Use in reader" box - does that help?

[HW60]

No - I checked all 4 boxes for the user dict before.

[mikelove]

Hmm... might be a bug then. Has anyone else managed to include user dictionary results in compounds successfully before?

[daniel123]

Some time ago I reported a small bug: when opening IA while the keyboard is already opened it overlaps the IA window. The keyboard also cannot closed while the IA windows is opened.

This just happends if using IA via taskbar icon. If instead using IA via start menu I can open or close the keyboard without any problem.

So the problem just affects the IA when using taskbar icon. Unfortunately this is the only possible way to use it in WM 6.5.

[Scoox]

System: Palm Zire 72s, Palm OS v5.2.8, Pleco 2.03

Summary: Executing the 'Copy to input' command when no text is selected crashes the system.

Reproducing the bug: This bug can be reproduced in various ways, but all of them feature an attempt to 'Copy to input' with no text selected.

1. In the preferences, set stylus tap-hold action to 'Menu'.
2. The Pleco screen has two parts, the list and the definition. The list may or may not be hidden, this does not matter.
3. Look up a word that has a short definition, so that the definition part of the screen has some empty space with no text.
4. Tap-hold in an empty area of the definition, i.e. not tapping on any text so that nothing is selected. After a short delay, the menu comes up (Copy, Copy to Input, Magnify, Char Info, Popup Defn).
5. Tap on any one of the menu options except Copy to Input. For example, tap on Copy.
6. The menu disappears.
7. Tap and hold again in the empty area of the definition.
8. [BUG 1] The menu does not come up this time (the menu would have come up if text had been previously selected)
9. Tap and hold once again in the empty area of the definition. The menu comes up this time.
10. OK, that's one bug. Now comes the big one. Tap-hold in an empty area of the definition (same as step 3 above). The menu pops up.
11. [BUG 2] Tap on Copy to Input. The system crashes with the following error message: Fatal Alert: MemoryMgr.c, Line:3722, Nil Ptr Looks like an uninitialized pointer to me.

You can also set the stylus tap-hold action to directly copy to input (thus bypassing the pop-up menu stage), and the system will crash too.

[mikelove]

daniel123 - we'll take another look at this, but it may prove difficult to fix - IA already exists in kind of a nebulous gray area windowing-system-wise and I'm not sure if we can get it to consistently overlay the keyboard, though perhaps we can at least get it to relocate itself so it only occupies the non-keyboard part of the screen.

Scoox - thanks, this should be easy to fix.

[mfcb]

Hopefully Microsoft will fix I) in the upcoming Windows Mobile 6.5.3 release. (which I imagine will show up in ROM updates for a lot of devices)

II/III we've got a preliminary fix for now, doesn't even seem to sap performance much so we'll try it out in the first beta of 2.0.(8?) - thanks for the reminder on that.

We'll see if we can get IV) done for that first beta as well.

hi, i'm back using my touch pro, replaced the touchscreen and it worked again (although a few moments i thought i might be unable to assemble it again). currently i am using a WinMo 6.5.5 beta release and the list view problems with selecting items are gone, cant say anything about 6.5.3.

dont want to put any pressure on you, mike, but how late in january are we ? any new timeline? recently i check the forum 3 times a day, hehe

[mikelove]

Another week or two for the beta WM update, I'd say - distracted a bit by an unexpected-but-positive personal matter.