I added a method to DQSDTools last night to map virtual key codes to character codes. I'm thinking this will prevent having to change the DLL as much if we add more keycode detection. For example, I had modified the DLL to detect an F8 and send a WM_CHAR 2 to the search bar window. But, I thought it was weird to hardcode this arbitrary mapping of F8 to the character code 2. And, others may not want to use F8. With this new method, I wouldn't have to modify the DLL. I just need to make a call to MapKeyCode...
keyboardHook.MapKeyCode( 0x77, 2 ); // 0x77 = VK_F8 ...and then modify the okp() method to handle an event.keyCode value of 2. Of course, it would make more sense to go further and make this a preference. Maybe something like this... if ( doskeySearchVirtualKeyCode != 0 ) keyboardHook.MapKeyCode( doskeySearchVirtualKeyCode, 2 ); The checked in script doesn't use this new method yet, so you should be able to pull the latest script and not have any trouble. Later, Glenn _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Dqsd-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-users http://sourceforge.net/mailarchive/forum.php?forum_id=8601
