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);
}
On Mon, Oct 15, 2012 at 5:49 PM, Bradley Gabe <witha...@gmail.com> wrote:
> The problem is, I don't know what the offending 'code' is per say, but the
> line that it logs is:
>
> # INFO : VK_UP caught
> # INFO : VK_UP caught
> # INFO : VK_UP caught
> # INFO : VK_UP caught
>
> So it's not been very helpful for tracking down. I've looked through all
> of the non-compiled Python for any iinstances of the string 'caught' or
> 'VK_UP' and nothing at all is turning up.
> Also couldn't find anything in the PySide sources. I think it's in
> something that's been compiled.
>
> Incidentally, the string is not showing up in Maya. It's only in Soft.
>
>
> On Mon, Oct 15, 2012 at 5:39 PM, Steven Caron <car...@gmail.com> wrote:
>
>> already searched all my code, not with grep, but with a 'find in
>> files...' in my code editor, and its no where to be found.
>>
>>
>> On Mon, Oct 15, 2012 at 2:37 PM, Matt Lind <ml...@carbinestudios.com>wrote:
>>
>>> Couldn’t you run a ‘grep’ or equivalent on the python code for the
>>> offending line?****
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> Matt****
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> *From:* softimage-boun...@listproc.autodesk.com [mailto:
>>> softimage-boun...@listproc.autodesk.com] *On Behalf Of *Steven Caron
>>> *Sent:* Monday, October 15, 2012 2:34 PM
>>> *To:* softimage@listproc.autodesk.com
>>> *Subject:* Re: Qt Wrapper command log issue****
>>>
>>> ** **
>>>
>>> dont know what to tell ya, but to keep digging... try a simple pyside
>>> app and a simple pyqt app, or maybe try your apps in maya see if it logs.
>>> get out your widdl'n knife
>>>
>>> s****
>>>
>>> On Mon, Oct 15, 2012 at 2:18 PM, Bradley Gabe <witha...@gmail.com>
>>> wrote:****
>>>
>>> I disabled all of the QT events and it's still logging the message. Also
>>> reproduced it on Todd's system.****
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> On Mon, Oct 15, 2012 at 5:05 PM, Steven Caron <car...@gmail.com> wrote:*
>>> ***
>>>
>>> ok, can disable the key up and key down events in softimage, create the
>>> application, see if it still outputs the message...
>>>
>>> s****
>>>
>>> ** **
>>>
>>> On Mon, Oct 15, 2012 at 1:17 PM, Bradley Gabe <witha...@gmail.com>
>>> wrote:****
>>>
>>> It was Tony who sent me back to the list here looking for a clue :)****
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> On Mon, Oct 15, 2012 at 4:14 PM, Steven Caron <car...@gmail.com> wrote:*
>>> ***
>>>
>>> there is no place the plugin that logs that message, the place where we
>>> map the keys and key codes is here...
>>>
>>> https://github.com/caron/PyQtForSoftimage/blob/master/src/qtevents.py#L27
>>>
>>> if i remember correctly, Tony Barbieri made our plugin work with PySide,
>>> so i can't be sure he didn't make some changes which are not in our plugin.
>>> can you check with him?
>>>
>>> s****
>>>
>>> ** **
>>>
>>> On Mon, Oct 15, 2012 at 12:50 PM, Bradley Gabe <witha...@gmail.com>
>>> wrote:****
>>>
>>> Anyone else using Steven's Qt Wrapper for Softimage? (
>>> https://github.com/caron/PyQtForSoftimage)****
>>>
>>> ** **
>>>
>>> Once PySide is up and running in memory, every time I press the up arrow
>>> key, the command history repeatedly logs "VK_UP caught"****
>>>
>>> Somewhere there's a line of debugging code reporting that event, but I
>>> can't seem to track it down in either the wrapper code or the compiled
>>> code. :-)****
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> ______________________________________________________________________
>>> This email has been scanned by the Symantec Email Security.cloud service.
>>> For more information please visit http://www.symanteccloud.com
>>> ______________________________________________________________________
>>>
>>
>>
>
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
