First of all, you cannot give reference to javascript object(function test) into AKD_DLLADD call. That particular parameter must be raw (low level) code address of stdcall call convention. If you pass object as you did, you'll pass address of data associated with object(i.e. raw internal metadata of javascript interpreter).. and when AP try to call it - you will get access violation. You probably missed it in code:
Code: Select all
HK_CallBackAddr = oSys.RegisterCallback(HK_CallBack);
func_opentop = AddFunction(rott,_HK_RT,HK_CallBackAddr,CBC_OPENTOP);
func_openall = AddFunction(rota,_HK_RA,HK_CallBackAddr,CBC_OPENALL);
func_showhide = AddFunction(showhide,_HK_SH,HK_CallBackAddr,CBC_SHOWHIDE);
You see, 1st line "converts" javascript function into "native" function address, and only then we register hotkey(in this case we reuse the same function).
Second: script must be resident. Once you registered hotkey, your script must not finish until it unregisters it, or else in best case it will not work, in worst - crash on hotkey activation. The code below is typical pattern of creating resident scripts
Code: Select all
//! INITIALIZATION OF SCRIPT BUSINESS LOGIC: EACH SCRIPT DO IT DIFFERENTLY. WE - PREPARE HOTKEYS
HK_CallBackAddr = oSys.RegisterCallback(HK_CallBack);
func_opentop = AddFunction(rott,_HK_RT,HK_CallBackAddr,CBC_OPENTOP);
func_openall = AddFunction(rota,_HK_RA,HK_CallBackAddr,CBC_OPENALL);
func_showhide = AddFunction(showhide,_HK_SH,HK_CallBackAddr,CBC_SHOWHIDE);
//! HOOK AKELPAD EVENT QUEUE - THIS GIVES SCRIPT ABILITY REACT ON EVENTS
if(AkelPad.WindowSubClass( WSC_MAINPROC, AkelPadCallBack,
AKDN_OPENDOCUMENT_FINISH, // THIS IS EVENT RELATED TO BUSINESS LOGIC OF SCRIPT
AKDN_MAIN_ONFINISH, // THIS EVENT SHOULD BE HOOKED BY ALL RESIDENT SCRIPTS - FIRED WHEN AKELPAD ABOUT TO CLOSE, SO SCRIPT MUST FINISH ITSELF
AKDN_FRAME_DESTROY // THIS IS EVENT RELATED TO BUSINESS LOGIC OF SCRIPT
))
{
//! DECLARED OURSELF(SCRIPT) RESIDENT
AkelPad.ScriptNoMutex();
//! PROCESS EVENT QUEUE (SCRIPT SITS HERE UNTIL IT IS TIME TO FINISH)
AkelPad.WindowGetMessage();
//! UNHOOK EVENT QUEUE - SCRIPTS FINISHES, NOT INTRESTED IN EVENT ANYMORE
AkelPad.WindowUnsubClass( WSC_MAINPROC );
}
//! CLEANUP EVERYTHING HERE: WE UNREGISTER
DelFunction(func_opentop);
DelFunction(func_openall);
DelFunction(func_showhide);
oSys.UnregisterCallback(HK_CallBackAddr);
In script you see:
HK_CallBack - javascript function which we want to be called on hotkey event
HK_CallBackAddr - PROPER low level function address which (and only it) can be passed to AddFunction.
AkelPadCallBack - handler of AkelPad internal events.. You should rewrite it for your needs. But at least handling of AKDN_MAIN_ONFINISH must be done (to save your time of analysis: call PostQuitMessage(0); must be performed)
When you successfully register script as resident, you will see 'Running' label in script list on it. And if hotkey registered successfully, you will see it in HotKeys plugin in list of "All keys..." (your "test" label will be there).
Why it is so sophisticated? Well, it is one of oldest resident scripts which never was rewritten for new API (+code to handle business logic is not light). I have not followed Scripts plugin development much lately, I suspect there are some easy to use functions introduced, I never rewritten script, because it works as is. Actually this code more or less equal to code on pure C used in plugins (i.e. plugin API used directly). Few magic functions of AkelPad object made it possible to create such complex functionally, which was possible implement only as plugin.