I could add the ability to my program, to detect screen resizes and close/open the program

I've been meaning to update the ini with the changed settings.

Anyone wanna fill me in on all the changes?

The keyboard positioning and size issues will be fixed for the next release. It's increasingly apparent the effects of the problems are pretty random and deleterious to user experience.

DevDoo6:

The keyboard positioning and size issues will be fixed for the next release. It's increasingly apparent the effects of the problems are pretty random and deleterious to user experience.

ree:

With respect to the remote desktop issue (ZWKB being open and full screen after logging into remote session or back into the console), do you have any idea why that's happening?  Or are you just going to make the keyboard periodically check it's size relative to the screen resolution even when it is open (i.e. not just when being unhidden)?

Only the keyboard size and position will be fixed for a release to be made this evening GMT.

It is unclear from your description what the other problem is in relation to remote desktop - is ZWKB running on the remote machine or on the machine accessing the remote machine ? Is the size of ZWKB filling the desktop of remote machine or that of the local machine ?

ZWKB should not be open if you did not open it yourself. In any case, once the keyboard or part of it is no longer shown off screen, you will be able to hide+reopen it or shut it down as required.

Version 7.10.30 released

www.freshnet8.com

A quick change to incorporate auto-sizing and positioning of the keyboard whenever the desktop resolution is changed while the keyboard is visible. This ensures the entire keyboard is useable at all times.

Also fixed is the left-shift + right-shift toggle for the right shift activation on the physical keyboard.

Additional minor refinements have also been made.

ree:

Here's all I need to do to reproduce the problem:
- start logged in via screen on the UMPC (i.e. local console)
- make sure zwkb is running if it's not already and make sure it's hidden if it's not already
- go to another computer and remote desktop into the UMPC
at this point ZWKB is not hidden any more on the UMPC.  It fills the whole desktop on the UMPC.

Next :
- via the remote desktop session, hide ZWKB on the UMPC
- go to the UMPC and connect/log in via touch screen
at this point ZWKB is again not hidden.  It filles the whole desktop on the UMPC.

In neither of these cases of logging in/connecting did I explicitly open ZWKB.

I have done a quick test using your steps and these do not produce the effect described on my windows 2003. I think the problem probably occurs on XP because the remote desktop session is same as the local session on that remote machine. It's possible that remote desktop sends a right shift toggle to the remote session to reset the keyboard shift state upon connection. If that is the case, you can use "zwkb.exe NoPhysKb" command line to prevent zwkb intercepting key presses and interpreting the right shift toggle as a signal to open. Of course, this command line will also prevent you from intentionally opening zwkb using the right shift key on the machine running remote desktop.

If this suggestion doesn't help, then you will have to live with the minor inconvinience for now.

DevDoo6:

I have done a quick test using your steps and these do not produce the effect described on my windows 2003. I think the problem probably occurs on XP because the remote desktop session is same as the local session on that remote machine. It's possible that remote desktop sends a right shift toggle to the remote session to reset the keyboard shift state upon connection. If that is the case, you can use "zwkb.exe NoPhysKb" command line to prevent zwkb intercepting key presses and interpreting the right shift toggle as a signal to open. Of course, this command line will also prevent you from intentionally opening zwkb using the right shift key on the machine running remote desktop.

If this suggestion doesn't help, then you will have to live with the minor inconvinience for now.

mikey:

I apologise if this has been posted, but on the Everun hitting the arrow up key turns on and off the zwk! Found that by accident

The peek function temporarily hides the keyboard while the right mouse button is pressed. If your hardware up arrow is mapped to the right mouse button, then ZWKB is working as intended.

ZWKB is designed to be shown or hidden by the right shift key on machines that have a right shift key. If your hardware up arrow is mapped to the right shift key, then ZWKB is again working as intended. If you don't want the special action of the right shift key, then use the NoPhysKb command line option to disable the feature.

If the arrow up you are referring to is the on-screen Up key on ZWKB, it shouldn't do that. Although if the Up key is pressed by a fast double tap, the keyboard goes into typematic mode where by the Up key will automatically repeat. During the repeat, transparency of ZWKB may be increased, depending on the default/defined setting of the TypematicTransparency command line option in relation to the current typing transparency of the keyboard. Higher transparency during typematic action can be disabled using the TypematicTransparency=0% command line option.

DevDoo6:

mikey:

I apologise if this has been posted, but on the Everun hitting the arrow up key turns on and off the zwk! Found that by accident

The peek function temporarily hides the keyboard while the right mouse button is pressed. If your hardware up arrow is mapped to the right mouse button, then ZWKB is working as intended.

ZWKB is designed to be shown or hidden by the right shift key on machines that have a right shift key. If your hardware up arrow is mapped to the right shift key, then ZWKB is again working as intended. If you don't want the special action of the right shift key, then use the NoPhysKb command line option to disable the feature.

If the arrow up you are referring to is the on-screen Up key on ZWKB, it shouldn't do that. Although if the Up key is pressed by a fast double tap, the keyboard goes into typematic mode where by the Up key will automatically repeat. During the repeat, transparency of ZWKB may be increased, depending on the default/defined setting of the TypematicTransparency command line option in relation to the current typing transparency of the keyboard. Higher transparency during typematic action can be disabled using the TypematicTransparency=0% command line option.

has anyone tried the inscribe keyboard by illium?. this is also a free download. i been using on my q1 for several months and is everything i was looking for. i can customize my own keyboard, drag it on the screen, change the size, adjust the transparancy and minimize it to an unobtrusive size that stays on screen. i don't know why they offer it for free, but i'm not complaining. i haven't tried this other keyboard so i can't compare.

I haven't tried the inscribe, but I can recommend everyone go download it and use it. Once the novelty wears off, everyone can come back to good'ol ZWKB. By then a new release should be ready with some added cool features.

ZWKB is all about minimizing energy expenditure from the user. I am quite sure many will find that characteristic irresistible.