AutoHotkey Community

No, not pushy at all, <pushy>Dallas</pushy>. In fact, I think very highly of your assertiveness, <pushy>Dallas</pushy>. I look forward to your continued ideas and support, <pushy>Dallas</pushy>.

I will try to have it up on the 20th, Wednesday. I am adding a new right-click launching method, among other things.

_________________

All right, I lied. I'll try to have it up by Friday at the latest. Sorry.

_________________

I lied again. It's Saturday and still noticeably absent.

_________________

Micahs, thanks for the update. Would it be possible for you to post or send me the fix to the zero. I'd really like to start looking at what I can do with it. Thanks.

The new version is up. I have yet to explain any new features in detail, though, so be warned. Not all of the keyboard layouts have been updated to reflect new requirements and changes so they might behave poorly. The only one up to date is the "English-Fancy" layout (I use this one for testing as I go.)
I will update the others shortly so they will be usable. I also plan to post a comprehensive xml structure/syntax soon.

There are several new features worth noting quickly:

• Fixed the no zero problem.
• Fixed Sympad. It is now an xml layout.
• Multiple gui support - Have any number of keyboards open at once.
• HotStrings - kb_hotstrings.txt is located in the resource folder. Supports no backspace and no end char options.
• FastStrings - kb_faststrings.txt located in resource folder. User added commonly used phrases to speed up typing.
• Different fonts for each row/key.
• New launching method. Right-click for 500ms and a thumbnail of the keyboard appears. Click on it and the keyboard opens. If you move the mouse off of the thumb without clicking, it disappears. This method is now the default.

Changed button labels (some are obvious, some aren't.) If you are running XP they should appear correctly. If using another os and the specified font is not there, you might have to edit the xml layout to change it back to words.


Showing the thumblauncher and the keyboard.


Faststrings in action.


This one is a doozy. I have the Sympad button pointing to the same xml file used for the main kb (recursion is kept to 4 iterations.) Each kb has the numpad open. This just demonstrates the multiple kb capabilities.


I will update the first post later.

_________________

Mechas, I think I'm missing something, where is the new posting? I downloaded the only one I could find and it didn't bring up the keyboard, and when I changed to Numpad, same thing. However, when I went back to right click the icon, exit was not there. I had to close it in the task manager. I'm totally lost. Thanks.

In my previous post I stated, but did not emphasize, that the new method of launching would be the thumb-launcher. I'm sorry for the confusion. I should have waited a while after adding a feature before changing it to the default behavior.
To activate, right-click for >500ms and a thumbnail image of the keyboard will appear. Then click on it to show the keyboard. To ignore it, just move the mouse off of it and it will disappear.

Because you say that the 'Exit' menu option is not there, it may be another problem, though. What version of AHK are you using? You might want to update to the latest version and see if that fixes it. I might have used a command or something that isn't supported in previous versions.

_________________

Yup, that was it. I must have read right through the right click. As for the exit button not being there, I see what it is. You must be in the Keyboard before it shows. Don't know if you meant to or not but this code wasn't in the numpad.xml:

<traymenu>
<command value="show">Show</command>
<command value="hide">Hide</command>
<command value="exit">Exit</command>
</traymenu>

By adding it you can now exit the program from the NUMPAD.

Thanks again for this great application.

Micahs, I haven't used this yet on an actual touch screen but it dawned on me, there is no keyboard, so how do you active it. I'll get a chance to check this out next weekend on a touch screen but thought I'd go ahead and run it by you.

A keyboard is not required to use it. But I just thought of a problem with using the thumb launcher with a touch screen--how do you right-click? I've used touch screens in the past, but there was always a mouse handy too. I never needed to right click with the touch screen. It might be easier to stay with the placeholder launch method.

As far as the numpad not having the command localization, that was intentional because that one is supposed to be a supplemental kb--not a main kb. It might not be a bad idea to add those commands to all kbs, just in case! I'll go ahead and do this. Thanks for the input.

_________________

Yup, actually I said keyboard but meant mouse. I want to use this on a stricktly touchscreen system that doesn't have a kb or mouse. How can I have it activate when it loads? thanks again.

Micahs, I was able to get to a touch screen today on a Terminal server session. I ran OSKB on the terminal (for the touchscreen session) but wasn't able to activate it at the touchscreen. I went back to the terminal server (with kb and mouse) and activated it. I was able to see and move the OSKB, however, when I loaded a web page, OSKB wouldn't send the keys to the browser. This may have something to do with the touchscreen driver because I loaded the same WEB application on my laptop and was able to use my mouse to click the keys, and they were sent to the WEB applciation. Hadn't tried the same test on the touch screens though. Will try that next.

The main thing I could use is when the OSKB loads have it go active, and let the user right click the icon in the tray to hide, show or exit.. This way we wouldn't need a right click..

Thanks Micahs.

[EDIT] I started this post before your second post above.
I think I'll stick with my first thought:

I was thinking of using this, but why go though all the trouble of remapping left and right clicks just to hold the right button down to activate AHKOSK? The better solution might be to just use the placeholder method (the thing docked to the titlebar that you hover the mouse over to activate.)
I know that on the touch screens I have used, if you put your finger close almost-but-not-quite-touching the screen, the pointer will move but not register a click. This might work for you.

Also, if you use the placeholder method, you can click on it and the pointer will stay there. After .5 sec the kb will appear and then just click at will. That might be your best bet.
Hmm, I just realized that clicking on the placeholder will steal focus because it is not considered one of the kbs. Just for you I uploaded a new version where the placeholder does not steal focus - so this will work now.

BTW, that right-clicker I mentioned before might be something you'll want to look into if you use the touchscreen often.

_________________

For your second post, that's easy! Just edit the kb.ini file. The two entries you will want to change are:
titlebarDock=0
thumbLauncher=0

This will make the kb stay active when started. To hide and show, click "Hide" or "Show" on the icon menu. Is this what you had in mind?

I can't think of why it wouldn't work in the web browser. Let me know what you come up with. I have no access now to a touch screen.

_________________

Thanks Micahs, I plan to try it on a terminal server session and a stand along touchscreen application. I'll let you know how it goes.