Quote:
Maybe you could post your script so others can try to make it work with PKL.
My script is very very modest at the moment, cause I am doing some tests before developping it really.
Here is my test script:
Code:
Gui, Add, Button, x26 y17 w110 h40 , GCP
Gui, Add, Button, x186 y17 w110 h40 , dtSearch
Gui, Add, Button, x26 y77 w110 h40 , Doc
Gui, Font, S8 CDefault Bold, Verdana
Gui, Show, x131 y91 h581 w353, New GUI Window
Return
GuiClose:
ExitApp
ButtonGCP:
run, K:\Data\GCP_V07-04.mdb
return
ButtondtSearch:
run, C:\Programme\dtSearch\bin\dtsrun.exe
return
ButtonDoc:
run, K:\Data\Doc
return
#F12::Run, Notepad
::cad::c'est-à-dire
::aaa::pour voir
::rrr::encore un pour voir
The button commands works perfectly (that's why I said running two AHK scripts is not a problem)
The #F12 hotkey works too...
concerning the replacement:
cad and rrr do not work but aaa does. That means it is a mapping problem. "a" is at the same place on the bépo and on the QWERTZ, but it's not the case of "r", "c" and "d".
I have three PKL layouts : bépo with a qwertz mapping, another bépo I created for German with a qwertz mapping too (means all shorcuts are the same like on a qwertz keyboard) and a bépo with bépo mapping. It works with no one. *But*, with the bépo pilot, all work perfectly. So it's definitely a mapping problem!
The question is : is there any possibility to solve this problem?
Of course, I could use the bépo-pilot to write but I can't install it as standard cause I m not the only one using this computer, and when it's not standard, you have to switch the keyboard in every application you start, quite annoying. With my PKL, I just have to connect my flash drive and all what I need is there.
I thought a possible solution would be to write a script that sets the bépo-pilot as standard when being launched and that sets the "normal" keyboard back when closing the script.
Would it be possible?
Guillaume
[/quote]