   VK_Fn ambiguity
  Hi, i am using virtual keys for my program and i have this problems so far:VK_F6 doesn't work, probable ambiguity with a standard windows command.VK_F10 is treated as VK_MENU and is thereby filtered out before it gets to the child window in which i need that message.This is just what i think is the most acceptable reason. But, does anyone know how to fix it ?For message handling i use the standardswitch(message){  case WM_KEYDOWN:  {    switch(wParam){type of code.Thanks[edited by - Tree Penguin on February 5, 2004 6:14:49 AM]
  If you are using MSCV some of the Fx keys are used for debuging/IDE or something like that so you can''t use them. It should work if you compile in release mode and execute program out of IDE. If you''re not using MSCV then just ignore this reply.   You should never let your fears become the boundaries of your dreams. ;  I tried that already but it didn't work .And another thing to notice: VK_F7,8 and 9 work properly!   [edited by - Tree Penguin on February 5, 2004 7:24:03 AM];  Try removing the TranslateMsg(&msg) call in the loop.Just guessing... ;  No, actually there is no TranslateMsg(&msg) call. I did disable all PreTranslateMsg(&msg) calls but that didn''t work.Some extra info, i am using an MDI interface, the menu gets the F10 (probably also the F6) and i want the F10/F6 keydown message to reach the child view of the active child frame.Thanks 