Closed tonybarbieri closed 11 years ago
This is using PySide btw.
thanks, could you show me exactly what code you removed? maybe on your fork of the repo?
i think jo was planning on using cpp to do the key mapping/redirecting.
I commented out lines 41->42, 44, 48 -> 79, 86->87, 105.
https://gist.github.com/3896147
If you aren't getting this with PyQt, then that makes me think it's a PySide logging issue. I quickly searched through the PySide source and can't see any areas where "caught" is being logged.
thank you, i will discuss this with jo and see what the exact purpose of that code was. i would also like to try and reproduce this.
Great, thanks so much Steven. I'll keep investigating as well to see if I can find where it's happening. I'd like to nail it in case the decision is made to go full cpp for the Signals.
Ok I found another way that fixes it. For the VK_UP code jo had written on line 58:
QApplication::sendEvent(sianchor->children().at(i), &e);
But he had written for the VK_DOWN (which wasn't giving us the log message) on line 65:
QApplication::sendEvent(sianchor->children().[i], &e);
changing the VK_UP code to match the VK_DOWN code seems to solve it. I have no idea why.
-tony
I'm sorry, there should be no '.' before [i] it should read:
QApplication::sendEvent(sianchor->children()[i], &e);
this is fixed in 08a65b1481c70a5b94211a63e5272e3a0a2b3773
Removing the listener and hook in the .cpp seems to solve this. Not sure exactly where the logging is occuring.