No Russian keyboard --> UMPCs less popular than they could be --> Less developers interested in them --> No Russian keyboard. I can wait until the second coming like that.

I'd code something myself, but I don't do Windows.

Doesn't that give you more reason to learn windows programming ? Armed with google, I can't see how you can fail. ZWKB was my first windows app too. Where there's a will ...

No, it gives me more reason to study driver development for Linux so I can switch this machine over.

Version 7.10.21 released.

www.freshnet8.com

Transparency
Command line option Transparent=nn% has been renamed to Transparency=nn%.

Typematic Transparency
A new transparency command line option TypematicTransparency=nn% has been added to allow setting of a special transparency level for when the keyboard is in typematic mode.  The typematic transparency can be set from 0% to 99% and the keyboard will atomatically switch to this level when typematic action begins, provided the typematic transparency level is higher than the current normal keyboard transparency.
The purpose of the typematic transparency level is to allow setting of higher than normal transprency so that the automatically moving cursor can be more precisely tracked with greater visibility.

Stay On Top
The StayOnTop command line option has been eliminated. The built-in passive stay on top capability of the keyboard has been fixed, and it will keep the keyboard on top of other windows/popups in the most efficient way possible.  The Vista TIP remains an issue. It appears to be a special popup that no standard windows, of which ZWKB is one, can rise above it.

Enter Key
The Enter key on the numeric keypad of physical keyboards has been implemented on ZWKB to occupy the Return key spot when the Fn is turned on. Some applications may differentiate the Return and Enter keys. For most applications, these 2 keys serve the same purpose.

Fixes And Refinements
The Foreground=nn command line option has been fixed to allow a colour code higher than 31, and in the range from 0 to 63. Other minor internal fixes and refinements have also been made to improve various aspects of the keyboard.

very impressive indeed DevDoo6!

I tested it on my tabletPC but really would love a 'linux' version for my nokia n800 Internet Tablet.

With lots of other mobile devices running 'linux' in the near future [Intel's 'moblin' etc] would you consider implementing a hildon/ubuntu mobile version?
[perhaps with the help of some linux developers if needed]

I posted about your 'Zero Weight Keyboard' in the following thread in the Internet Tablet Talk Forums:

Transparent thumb keyboard poll

I finally got around to using this KB.  It works like a charm!!

ichmoimeyo:

very impressive indeed DevDoo6!

I tested it on my tabletPC but really would love a 'linux' version for my nokia n800 Internet Tablet.

With lots of other mobile devices running 'linux' in the near future [Intel's 'moblin' etc] would you consider implementing a hildon/ubuntu mobile version?
[perhaps with the help of some linux developers if needed]

I posted about your 'Zero Weight Keyboard' in the following thread in the Internet Tablet Talk Forums:

Transparent thumb keyboard poll

Thanks for your interest in ZWKB. Having looked at the Nokia devices, there doesn't seem to be a need for additional keyboards since they already come with on-screen or physical keyboards. Porting ZWKB on to smaller screens would just turn it into a stylus-pecking keyboard that would not be better than what Nokia has provided. The goal of ZWKB is to offer the bare minimum for 'touch' typing. This will not translate well on small screens. So, for now, if you want something like ZWKB, you will have to put your coding hat on and do it yourself. I have not decided on what to do with ZWKB yet. It will remain a closed but free commercial software for the moment.

socpsy:

I finally got around to using this KB.  It works like a charm!!

Me too very impressed, thanks to the creater

DevDoo6:

Thanks for your interest in ZWKB. Having looked at the Nokia devices, there doesn't seem to be a need for additional keyboards since they already come with on-screen or physical keyboards. Porting ZWKB on to smaller screens would just turn it into a stylus-pecking keyboard that would not be better than what Nokia has provided. The goal of ZWKB is to offer the bare minimum for 'touch' typing. This will not translate well on small screens. So, for now, if you want something like ZWKB, you will have to put your coding hat on and do it yourself. I have not decided on what to do with ZWKB yet. It will remain a closed but free commercial software for the moment.

The problem with the full-screen nokia thumb keyboard is that there is no transparency and one cannot see whether the other person is typing in an IM conversation for example; also my n800 does not have a physical keyboard.
Thanks for your response DevDoo6.

ichmoimeyo:

The problem with the full-screen nokia thumb keyboard is that there is no transparency and one cannot see whether the other person is typing in an IM conversation for example; also my n800 does not have a physical keyboard.
Thanks for your response DevDoo6.

Perhaps Nokia realised the limitations and for that reason built a hardware keyboard for the next model n810. I imagine they would expect the n800 users to upgrade to overcome the limitations of their model. If the device is sufficiently useful, maybe it's worth the replacement price ? Because the n800 is an out-going model, the chance of Nokia improving its useability is deminished. For the same reason, developers would be reluctant to commit efforts.

DevDoo6,

Just had to post and say thanks for this application.  I can't believe how much functionality it provides on my Q1 Ultra.  As I said on another forum, I consider it an absolute requirement for anyone that owns a Q1 Ultra.  At this point, the pyhsical keyboard is used solely for shortcuts (in which it excels) while ZWKB is used for everything else.

Many thanks!

Thank you all for your positive feedbacks. Although I will not respond to each individually, all your comments are much appreciated. If you like ZWKB, you are welcome to tell other UMPC/TabletPC users about it. I am certain many more people will find it useful.

Devdoo6,
I just started using it this weekend and it turns out that of all the on-screen keyboards I've used, it's probably the best.  As others have mentioned before, having to tweak command line options to configure it is a little bit of a pain, but I can handle it.

A problem that I encountered is that zwkb doesn't resize if the screen resolution changes.  I logged into my UMPC after a reboot via a remote desktop session which is configured at 1024x768.  Zwkb started at this size.  Next, I logged in via the touchscreen which, by default on my box is 800x480.  Zwkb was open, covering the entire screeen, but the lower row of keys and the right row of keys was off the edges.  So I could not press Hide, nor could I press Fn in order to get the Exi option.  I had to limp my way around the system holding the right mouse button down to get the task manager up and kill zwkb before I could do anything else.

So could it monitor for resolution changes and adapt?  Also, why does is zwkb showing the keyboard after I log in when switching between remote desktop and local console sessions?

Thanks.

ree:

So could it monitor for resolution changes and adapt?  Also, why does is zwkb showing the keyboard after I log in when switching between remote desktop and local console sessions?

Thanks for the problem report. The resolution thing is an ongoing issue because there are countless ways in which the desktop resolution can suddenly change. At the moment ZWKB only checks the available resolution whenever it is activated, ie, unhidden.

I will take a look at how the keyboard interacts with remote desktop and see what's going on. Generally, problems that I can reproduce can be fixed.

Okay, thanks.  Perhaps, could you devise a hide function that can be activated if the right and bottom keys get hidden?  An obvious one would be to put the Hide button where Esc is, but I'm sure most of us like the Esc key where it is.  What about adding a gesture that will hide it :)