Great keyboard, thanks! I think I will use it more than TiP or any other I've tried. One thing though: when using IE7 and typing a URL, the history pops up on top of the keyboard, making it unusable. Any ideas on how to solve that? I know I can clear my history...but I'd rather not.

He could do a check of say, every 64 pixels or so (checking every pixel would slow it down horribly, plus most windows are larger than 64 pixels in either width/height), using the XYtoHWND API (I could provide it if he wants) to check if any windows manage to get over top of the OSK. And if one is detected he could force it behind the OSK.

He'd only need to do the check once a second or two as well.

Though 64 pix might be big enough that if the bar had only one item in it, it could slip by undetected. He'd just have to make the Y increment smaller than the X one, make Y the size of one item, and X 64 or larger. That would actually work better

elempoimen:

Great keyboard, thanks! I think I will use it more than TiP or any other I've tried. One thing though: when using IE7 and typing a URL, the history pops up on top of the keyboard, making it unusable. Any ideas on how to solve that? I know I can clear my history...but I'd rather not.

That's a vista specific problem. I haven't a solution so far apart from praying in the direction of Bill Gates and begging the almighty wisdom to make his OS' compatible with one another.

On other windows as well as Vista running on faster systems, the keyboard automatically rises above all windows pop-ups when it detects them via normal Windows API. The API does not report these pesky pop ups  on Vista installed on UMPC's.

I will consider adding a command line option to enable aggressive take over of the high ground on the Windows Desktop. Look out for the next version of the keyboard.

Actually, I'm on XP. Now for some reason it seemed to work OK today, but it was a major problem last night. I'm using it now, though. And it's pretty slick!

I've read some of the thread. It be interesting to hear you describe it. For example, is it the the dial keys thing ? Not sure about vista support. just wanted to understand more about what it is.

Not completely sure what your question is relating to. If you want to know what the keyboard is, the best way to find out is to get a copy and run it. It is definitely not dial keys. ZW keyboard is for people into serious typing, but who are seriously not wanting to carry a physical keyboard with them and pretend they have a laptop.

In a nut shell, ZWKB is for people wanting to do biz on their UMPC.

Version 7.8.30 released.

Just a minor update that adds "StayOnTop" command line option. The keyboard already has a builtin non-aggressive Stay On Top capability that allows it to automatically rise above various windows pop ups that might obscure keys and making typing difficult. However this capability does not appear to be effective in all situations. The new command line option ensures the keyboard stays on top unconditionally. The StayOnTop option increases the keyboard's CPU usage by a noticeable amount (only while the keyboard is visible). This option should be avoided unless necessary.

To start the keyboard with the aggressive stay on top capability:

    zwkb.exe StayOnTop

DevDoo6:

Not completely sure what your question is relating to. If you want to know what the keyboard is, the best way to find out is to get a copy and run it. It is definitely not dial keys. ZW keyboard is for people into serious typing, but who are seriously not wanting to carry a physical keyboard with them and pretend they have a laptop.

In a nut shell, ZWKB is for people wanting to do biz on their UMPC.

Thanks for that. I'll give it a go, though I'm not into work related stuff right now.

Version 7.9.2 released.

www.freshnet8.com

This versions adds a Background command line option to allow selection of a start up colour for the keyboard background. There are 24 colours in the background palette. When used with the 32 colour foreground palette, hundreds of distinct combinations of keyboard colours become possible.

The keyboard background can also be changed while the keyboard is already running. Turn on the Alt key, then use the Hom/End keys to cycle through the available background colours. While the colour is being changed this way, the number for the colour is displayed on the space bar. This number can then be used for the Background parameter.

For example:

zwkb.exe Foreground=14 Background=19 Transparent=50% Res=1024x600x180%

sets the foreground (symbols) colour to medium yellow and keyboard background to medium blue. This colour combination along with the transparency and font enlargement offers excellent visibility for the keyboard as well as for applications underneath it on the the Q1Ultra.

There are many more brilliant combinations waiting to be explored.

Note: the colour numbers for Foreground and Background options are not directly equivalent. For instance, black is colour 0 in the foreground palette and colour 2 in the background palette.

Note 2: The foreground and background cannot be set to the same colour. For instance, if both the foreground and background are set to black, the keyboard will automatically select the next colour for the foreground. In this case, colour 1, dark grey will be selected by the keyboard for the symbols on keys.

You really should be making an option screen rather than making an designed to be a keyboard, on a keyboardless device, require you to use a keyboard

A self keyboarding keyboard is in the same vein as the classic self compiling compiler paradigm. Doing it this way makes people appreciate the value of this keyboard. Of course it is also for my convinience. I can foresee a time when zwkb takes no parameters. That time isn't yet.

(this message is from my Q1U empowered by zwkb)

DevDoo6:

A self keyboarding keyboard ....

I don't think we're talking about the same thing here.

Using a command line is very unintuitive on UMPCs. You have enough settings where your excuse that we can use shortcuts doesn't apply. Editing shortcuts is still a hassle.

I can give you the code for my number selection box from my minesweeper and Origami Experience clone. But you really should be thinking about user friendliness from the start, you're wasting time by continuing to support the command line when you could implement something much better.

The keyboard shortcut keys were slightly better, but still inelegant as now you require users to read a manual to know about them. An option button leading to an option screen would be much better

NeoTechni:

You really should be making an option screen rather than making an designed to be a keyboard, on a keyboardless device, require you to use a keyboard

lol ironic isn't it?

The existing user interface for the keyboard is adequate for its purpose. By no means does it resembles the final design in the slightest. I have assigned no further priority in this area whilst numerous other features are waiting to be implemented. There will be plenty more command line options to come. I dare say there is a chance the keyboard will receive the most verbose and lengthy command line in history before it is done.

I am sure many of the existing users of the keyboard already know that the best way to start the keyboard is through a window shortcut where the preferred parameters need only be defined once using the keyboard itself. This is where the self keyboarding keyboard shines.

I am sure many of the existing users of the keyboard already know that the best way to start the keyboard is through a window shortcut where the preferred parameters need only be defined once using the keyboard itself.

Which as I said is an unintuitive/inelegant/unuserfriendly solution. And the longer you ignore the problem, and add more command line options, the worse it will get.

Editing shortcuts is not only tedious but annoying, as the stylus is not good for selecting insertion points, plus the whole thing about you trying to make a keyboard. You shouldn't need another keyboard to use your program.

A simple options form wouldn't take more than an hour, especially if you accept my offer to use the touch-optimized number selection box.

As a programmer, the interface should be your priority. 90% of a program is the UI.
Get it user friendly first, rather than reworking the program later on, you're just making more work for yourself.