AutoHotkey Community

Guess you just proved yourself wrong! :D

Good job tracking this down. I will review it and incorporate this into the main code. BTW, I recently got a Nook Color that I put full Android 2.3 on; it just hit me that now I can try a VNC solution to see if the touchscreen on it allows me to test the touch-specific problems and your fix. Thanks!

EDIT: Yes, I tested it and I can replicate the touchscreen bug with the NC using a VNC app. Finally, I'll be able to make this work for touchscreens (though it looks like you've done the heavy lifting!)

micahs

_________________

Ok, now that the must haves are done, lets go onto the nice to haves.

1) what does doc supposed to do?
- I can't figure it out.

2) similarly, what it when the keyboard disappears and those pink squares,
or blue oval show up? I never want the OSK to "disappear", and thirdly,

3) why does it "jump" occasionally? it jumps from my touchscreen to some other area and I don't know why. I think it has something to do with my accidentally hitting "doc" but I don't want it.

4) I need the keyboard to be basically stationary and visible (the half transparancy is ok) ALL the time, and it can't disappear.

Any advise?

Sincerely,

jleslie48

Absolutely!

The blue (or red - it's normally red; not sure why yours is blue) oval is the kb activator. When it is docked, the oval shows up on the titlebar of the active window. You hover over it for a few seconds to make the kb appear. If this does not work for your application, just turn it off! Look inside "\res\kb.ini" for two entries:
Above is the default setting for each. To make the kb float on startup, set both to zero. These are alternate kb activator settings, so to make the kb float you have to turn them both off.

The kb jumping is a feature that lets you bump the keyboard out of your way if it is over something you want to see (IE: textbox on a web form or something.) It activates by quickly moving the mouse over and then back off the keyboard. The direction of mouse movement off the keyboard controls which direction the kb jumps. To me, this is quicker than dragging the kb out of your way. To disable this feature, look in the same ini file for:
Set this to '0' to disable it.

There is no 'doc' button, but there is a 'dock' button. You might have your dpi set so that the entire word does not appear... The 'dock' button hides (or docks) the kb and turns on a kb activator (either the red/blue oval or the right-click thumb launcher.) You could edit the xml to remove the dock button if you want to make darn sure you don't accidentally click it.

Gotta go (I'm on break!) HTH

micahs

_________________

You da man!! This is looking great. Thanks again! - Jon

It won't possition itself right when called form second display - it will show up in edge of first one - though you can still move it there

Yeah, I had only a single monitor when I was doing the bulk of the project. I now have two, so I need to carve out some time to make this multiple-monitor friendly. Thanks for the reminder!

I need to do work on the touchscreen version, too. I have lots of other ideas for this project, but just haven't had time lately.

micahs

_________________

I just got for work a panasonic cf-h2 toughbook and it has a really nice built-in version of a osk very similar to yours. What it did was when you hid it (auto or manual) it would "slide" off the screen to the left (user selectable left|right|top|bottom, middle|corner1|corner2) and leave just a thin bar showing, just a few pixels wide and as long as the keyboard is wide. Just wide enough so if you clicked it, it would register and expand.

Hi, I love this app. I am having trouble with my layout and could use some pointers, though. Instead of 12 function keys I need 16. I also need shifted function keys 17 through 32. Although I did not expect them all to work I initially defined them as below:

obviously F13 and above did not work. The unexpected thing however, was that once I pressed a key above F12 that key and any function key after that produced a capital F. What I actually need, for instance when I press F16, is for it to send a multi-key sequence, which in this case would be alt+F6. F32, then, would be shift+alt+F6. As shown by the XML above, I need the shifted value to show on the keyboard. How might I accomplish this?

I had thought about user functions but, when I tried that they did not fire. Upon looking at the code, it appeared as though there was no code written to execute user functions. Since my AHK programming is somewhat limited and it has been over a year and a half since I wrote my last AHK GUI script, and those were limited, I thought perhaps I missed something. Since I also wish to define special keys that do things such as a screen capture straight to a JPG file, any suggestions on how I can get user functions to work would be helpful as well. Thanxx.

BTW: I would be happy to help test any touchscreen or multi-monitor changes. I just added a touchscreen specifically to run this and other AHK GUI scripts.