For some reason, the Key object version I currently have doesn't recognize all the keys. Has there been an update that adds any missing keyboard values that pick it up?
Some keyboard inputs that aren't recognized by Key Object:
- [?/] Key
- [_-] Key
Hmm...... Seems that all OTHER keys seem to work though. Just those 2, as far as I can tell.
I might look at re-writing the key object extension at some point in the next 2 years, I feel it could use a little bit of improvement, it uses twice the resources it needs just to check for any key press and mouse wheel is also ignored.
But don't hold your breath.
Oh, YOU wrote the key object extension? THAT explains why you're replying to most of my messages relating to the object. XD
It really does come useful. Otherwise, I wouldn't know WHERE else to go to write my input script to work while it's off focus. :)
Umm... Okay so, I double checked the Key Object, and it says it's made by LIJI. Though the link given ion the object popup window is either broken, or just redirects to the clickteam website.
No I didn't write it... I just want to rewrite it because it's very old and not optimised for what I need it for. I'm fairly sure it's not unicode compatible, so people typing in french or russian will not register key presses. I don't think the original author is still around. His profile has no history:
http://community.clickteam.com/members/5125-LIJI
Quite frankly, we really could use a new key object of some kind. If you choose to make one, then you could put it on the Clickstore if you wanted to and then you could make quite a bit of money from it (if there are as many people who would want it as I think), or you could ask for funding in advance alternatively, in either case that's if you feel the need to get money from it. If you don't feel the need to get money from it, then you could go ahead and make it pretty much just whenever you feel like it.
Well.... If there comes a new Key Object, it would definitely help my application script to be more accurate to record more keys as well. Though I don't expect it, but I'm hoping if it does get replaced, the conditions would be the same, or similar so I wouldn't have to rewrite the entire script just for the new key object compatibility. But I guess the key object we have now is okay for my needs, anyway. XD
Well, unless Ryan (or anyone else who plans on making such an object) can get access to the source code of the old version of the object (or at least the IDs for the actions/conditions/expressions), then it's not really possible for it to be compatible/an updated version of the object, though they could be made similar (again, they wouldn't be compatible, so you'd still have to manually convert the actions and such).
Hi,
Have you tried controlx ? Its what I use...
With kind regards,
Bradley
I tried it, but control x does NOT work virtually. In other words, it does not detect if the frame window is off focus, with another window being on focus, which is what I need, which the Key Object can do.
All of the keys you mentioned in your first post work for me.
e.g. the "?" key on my german keyboard need the following events to trigger:
Is key "shift" down?
+ Is key "ß" down?
So holding shift+ß which respresents "?" works fine.
I used the dialog option to recognize the keys no the actual IDs.
Key Object 1.2 (1.2.2RC2)