Get it at www.freshnet8.com. It is regularly updated with new features.

Version 7.7.31 is now available.

This release adds a permanently visible Tap Box for stylus users who had no way of bringing up the keyboard previously. The Tap Box is small enough to be unobtrusive but big enough to be tappable by an accurate finger. A corresponding -NoTapBox command line option is provided for users who donnot require the Tap Box. The Tap Box can be dragged out of the way to anywhere on the desktop.

All keyboard activation methods are switched on by default. These can be switched off respectively using command line options:

-NoTapBox

-NoBumpBox

-NoPhysKb

The Q1u specific -Q1Ultra option is now obsolete.

That isn't at all bad! Thanks.

Holding a Q1U in two hands and using your thumbs to type works pretty well, but is a bit of a stretch on some of the keys.

If I rest the Q1U on my lap and type with a few fingers then I can get a really good speed.

I do think it needs a way to set the options without command lines or at least lose the sound by default!

And if you really want people to use it then you need an 800x480 version. The Q1U is the only UMPC without a keyboard (I don't count it's silly keyboard) and a 1024x600 screen right now, so you are limiting potential users!

Keep up the good work and keep us posted here about new versions.

Cheers
Marc

An observation I have for the keyboard is that a lot of touchscreens are not sensitive enough for finger touch typing. They appear to be designed to register a touch only when the touch area is quite small. That means touch typing on the screen can be a little frustrating because of unregistered taps. I experimented typing with the tip of my finger nails and found it surprising effective in making perfect tap every time. I found that I could type close to the speed of a normal keyboard using the tips of nails of my index fingers and a thumb. Speed typing using finger nails can potentially do damage to the screen. This is just to report my own expereience and not suggesting anyone should do the same. Use this information at your own risk.

I really had no problem with the Q1U screen. I can type quite happily with the pads of my fingers. I was surprised how fast I could type.

I had a thought of a feature that would make this really special. But no idea how hard it would be to implement....

Allow the user to set the opacity level of the software, so you can see underneath and thus see what you are typing.

I know quite a few apps can do this, but no idea what considerations you nee to make in building the application to support this.

Looking at winamp that lets you set the opacity, I think a ratio of about 70% opaque would work brilliantly.

Version 7.8.1 is up.

This release fixes a problem with the peek function in -NoBumpBox mode not working properly. The key clicking sound is fixed for shifted alphanumerics. The lag between a key press and the click sound being heard has been reduced.

The keyboard relies on Windows winmm.dll for it's sound capability. This dll is not currently working properly on Vista. I sugguest the key click sound be turned off using the -quiet command line option when the keyboard is being used on Vista. Hopefully, Microsoft will fix this dll soon.

So what do you think about the possibility of a semi transparent version?

If you have written it in Visual Studio .Net (a guess from your requirements on your web page). Then it appears adjusting the opacity of a windows form is really easy!

See here:

http://msdn2.microsoft.com/en-us/library/czke9azk(vs.80).aspx

You could easily make a command line parameter to set the forms opacity couldn't you? Something like -opacity 0.75 to set it at 75%

Please!

Thanks for all your interest in this keyboard as well as your comments. There will be many features yet come for the keyboard. In particular, dynamic resolution for different systems as well as opacity settings. I am looking into automatic settings that reduces the need for user intervension.

Quote:

I may introduce such an option as a temporary measure in the next version.

Great!

I look forward to seeing future versions.

Have you thought about adding a pop-up menu to the Orange Z box? Perhaps you could put settings in there if it is right clicked?

Quote:

Fantastic! This would make it a killer app for me.

Version 7.8.4 released.

This version removes the leading "-" in all command line options. Please change any existing shortcuts or start up procedures accordingly. The following options are supported:

Quiet
NoBumpBox
NoTapBox
NoPhysKb
Transparent=nn%


Finally, the much requested transparency feature is now here. To start the keyboard in half see through mode, use the command line option "Transparent=50%". Supported values are 0% (not transparent) to 80% (almost complete transparent). While the keyboard is running, the transparency can be adjusted in 1% steps using the Fn key followed by the Up and Dn keys on ZW Keyboard.

Okay, now the title of this thread is correct!

It is brilliant!

The transparency feature has made it a must have application for me. I've tried other full screen keyboards for portable devices in the past (mainly PDAs) and they all fail because you haven't got a clue what you are typing!

I have no problem typing with the pads of my fingers on this and find it really quick. I also find it better with no sound.

Thank you very much!

Version 7.8.5 is up.

This version incorporates code to keep the keyboard and the Tap Box above other special top level windows such as pull down menus, task bar, and pop ups like the IE URL history list.

Whenever necessary the keyboard will bring itself to the fore within 1/10 of a second of another window appearing in front of it. The timing for the tap box is more relaxed. The tap box will rise to the top within 2 seconds.