wosk steals focus on start up


I am testing wosk on a project using adobe air.
We want to use it in conjunction of our adobe air application. However when the application starts wosk when a user hits a text field, wosk gains focus which means that the application is no longer focused. As a result the user hitting the keys in wosk has no effect in the application. In order for the application to get the characters representing the keys that the user is hitting, the user has to hit the text field of the application again so that the application regain focus.
Is there anyway to avoid wosk to steal the focus from the application when it starts?
I am using the keyboard on windows 7.
Many thanks

file attachments


Ekus wrote Dec 9, 2010 at 3:02 PM

I see.. perhaps I could add some code for this.. so as not to activate the app on start (or rather deactivate it, which should probably re-activate the previously active app).
I will look into it.
BTW, it's interesting scenario.. Any chance for a screenshot of your app?

quinrou wrote Dec 10, 2010 at 10:35 AM


Many thanks for taking the time to look into this.

I didn't specify it but wosk needs to remain on the top at the even after loosing focus. So that it seats on the top of the air application.

I am afraid at this point I cannot provide you with a screen shot but as soon as I have realised the app I will.

When do you think you will have this implemented?


Ekus wrote Dec 10, 2010 at 2:46 PM

I will look into it during the weekend, but now I am not sure if this is really needed. If your application starts wosk, then perhaps it could itself regain focus programatically (something like calling this.activate)..

quinrou wrote Dec 13, 2010 at 2:00 PM

I did try this before dropping you a line but it did not work hence why I contacted you.
I tried to regain focus by watching the focus. as soon as I lost focus I was trying to regain it but it was unsuccessful.


quinrou wrote Dec 14, 2010 at 2:20 PM

Any luck with the focus stuff?

wrote Dec 14, 2010 at 10:06 PM

Ekus wrote Dec 14, 2010 at 10:06 PM

I've tested a solution and it seems to work OK, based on code from

I have cleaned Wosk up a bit (commited the source code already), got rid of two windows (menu and keyboard, merged them into single window). Please be aware that wosk is largely a proof of concept and not a complete app. I would suggest it's not production ready yet, especially the keyboard layouts may vary and be incomplete.

Please feel free to update your copy of wosk and its layouts yourself (and send me any changes :-).

wrote Dec 14, 2010 at 10:07 PM

quinrou wrote Dec 26, 2010 at 3:58 PM


Many thanks for your work. I'll be testing this next week.

We are also looking at new solution which came to me while messing with the come from wosk.

Many thanks.


wrote Feb 14, 2013 at 6:14 PM

wrote May 16, 2013 at 8:20 AM

wrote May 16, 2013 at 8:20 AM

wrote Jun 14, 2013 at 7:00 AM