Okay, problem solved. Tony removed that questionable code block and recompiled. I just tested a QTextEdit widget to make sure the up and down arrow keys weren't nuked as a result, and everything seems to be functioning properly.
Thanks for checking up on the code on your end. I'm having Tony add a comment to github. -Bradley On Mon, Oct 15, 2012 at 6:11 PM, Steven Caron <[email protected]> wrote: > also, i do not get this message when i hit up and down arrow keys. > > s > > > On Mon, Oct 15, 2012 at 3:08 PM, Steven Caron <[email protected]> wrote: > >> we would have to ask jo, but i always thought that was key up and key >> down... not arrow up and arrow down. after a bit of looking it seems its >> arrow up and down... >> >> http://msdn.microsoft.com/en-us/library/ms927178.aspx >> >> it might not be the start of code jo was writing to handle all the key >> code mapping in c++ instead of in python. regardless, we are not logging >> the message you are referring to... we are just switching on it. >> >> s >> >> >> On Mon, Oct 15, 2012 at 3:02 PM, Bradley Gabe <[email protected]> wrote: >> >>> Tony is curious as to what's going on with this block, since it directly >>> refers to VK_UP. Why are the up and down arrow keys the only ones with a >>> mention in the compiled code? >>> >>> LRESULT CALLBACK >>> >>> listener(int ncode, WPARAM wparam, LPARAM lparam) >>> >>> >>> >>> >>> >>> { >>> >>> if (sianchor) { >>> >>> >>> >>> >>> >>> switch (wparam) >>> >>> >>> >>> >>> >>> { >>> >>> case (VK_UP): >>> >>> >>> >>> >>> >>> { >>> >>> QKeyEvent e = >>> QKeyEvent(QEvent::KeyPress, Q_KEY_UP, 0); >>> >>> >>> >>> >>> >>> for (int i=0; >>> i<sianchor->children().count(); ++i) { >>> >>> >>> >>> >>> >>> >>> QApplication::sendEvent(sianchor->children().at(i), &e); >>> >>> >>> >>> >>> >>> } >>> >>> } >>> case (VK_DOWN): >>> >>> >>> >>> >>> >>> { >>> >>> QKeyEvent e = >>> QKeyEvent(QEvent::KeyPress, Q_KEY_DOWN, 0); >>> >>> >>> >>> >>> >>> for (int i=0; >>> i<sianchor->children().count(); ++i) { >>> >>> >>> >>> >>> >>> >>> QApplication::sendEvent(sianchor->children()[i], &e); >>> >>> >>> >>> >>> >>> } >>> >>> } >>> } >>> >>> >>> >>> >>> >>> } >>> >>> return CallNextHookEx(hook, ncode, wparam, lparam); >>> >>> >>> >>> >>> >>> } >>> >>> >>> >>> >>> > > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > ______________________________________________________________________ >
