Niggling UI glitch in 1.0.3

[caesartg]

Hi Mike

I've got one of those tiny difficult to describe UI glitches that I hope I can describe enough for you to replicate.

Machine: Lifedrive, PD version: 1.0.3

I've selected the "Left-handed HWR interface" and "Allow simultaneous list/input" perferences in the Input section and I have the HWR set to the "Bottom" setting. I also have the Palm's built-in write on screen option selected (don't know the technical term, the 'squiggly' Palm icon 2nd from the right). I also have the HWR box visible rather than minimised (the 'minimise button is visible).

If I write a character in the HWR box, everything's fine and it writes okay. However, when I click a character to enlarge it, suddenly the HWR box has lost its protection from the Palm 'squiggly' option and to be able to write easily in the box again I have to minimise and then re-maximise it again. I could turn off the 'squiggly' Palm option, but then I have to turn it back on when I enter pinyin in the input field. Seeing as I commonly intersperse looking up HWR characters with Pinyin-lookup and occasional enlarging of characters or the "Copy to input field" option, I'm always having to workaround this little problem.

Hope you can understand what I've just explained!

Cheers

Ben

 

[mikelove]

Hmm... it looks like it might be possible for the on-screen writing override to be disabled when another window like the character enlargement screen comes up. This may be beyond what we're able to take care of in a bug-fix update, but it should be fixable in 2.0 at least.

 

[caesartg]

Yo Mike

Just reposted this to show you the original bug that I had on the Lifedrive. Then, after quickly ditching the LD for a TX, it's still there and has become a constant niggling feature of my usage of Plecodict. Hope it's fixed for v2, because it does slow me down somewhat when I try to write a character in the little box and instead text appears in the text input field (which I then have to delete and turn off the write on the screen). Actually, although it's a bit strange to say it, the fixing of this little bug is one of the things I've been most looking forward to in a new release.

All the best

Ben Caesar

 

[mikelove]

We've had a couple of other reports of this, actually - thanks for the reminder but it should certainly be fixed in 2.0. (it might not be in the preview release, but if it's not fixed by the first "beta" let us know and we'll get right on it)