[PySide] Any workaround to access QtCore.MSG "message" field?

[David Anes]

Hi.

I patched the MSG struct following John Ehresman and Anand messages here:
https://codereview.qt-project.org/#/c/67938/

I included the patch attached that fixes PYSIDE-84 bug:
https://bugreports.qt-project.org/browse/PYSIDE-84

Tested on win8 32bit and win8.1 64bit (with Python 2.7.7):
https://dl.dropboxusercontent.com/u/22516050/PySide-1.3.0dev.win32-py2.7.exe

Anyone can test it in win7 and other possibly affected environments and
push this upstream?

Thank you.
David.


2014-06-16 23:23 GMT+02:00 David Anes <david.anes at gmail.com>:

> HI Anand.
>
> I completely missed that one, as I didn't find the patch after a lot of
> googling around.
>
> I'll try it out. Thank you.
>
> Meanwhile, if you need help testing or anything to help you aout, let me
> know as I want to contribute to PySide.
>
> Thank you so much!
> David.
>
>
> 2014-06-16 7:56 GMT+02:00 Gadiyar, Anand <gadiyar at ti.com>:
>
>   David,
>>
>>
>>
>> I had posted this patch to gerrit last year.
>>
>> https://codereview.qt-project.org/#/c/67938/
>>
>>
>>
>> John Ehresman had a comment that I had not followed up on. I’ll take
>> another look at it and try to address his comment this week – I had
>> forgotten about it. But the patch I posted works for me on Win7 x64 with
>> both 32-bit and 64-bit builds of PySide.
>>
>>
>>
>> Hope it helps,
>>
>> Anand
>>
>>
>>
>>
>>
>> *From:* pyside-bounces+gadiyar=ti.com at qt-project.org [mailto:
>> pyside-bounces+gadiyar=ti.com at qt-project.org] *On Behalf Of *David Anes
>> *Sent:* Sunday, June 15, 2014 11:52 PM
>> *To:* pyside at qt-project.org
>> *Subject:* [PySide] Any workaround to access QtCore.MSG "message" field?
>>
>>
>>
>> There is a bug (PYSIDE-84:
>> https://bugreports.qt-project.org/browse/PYSIDE-84) that states that
>> PySide.QtCore.MSG.message field (and wParam) is not populated... while this
>> is sorted out, QCoreApplication::winEventFilter is unusable.
>>
>>
>>
>> Has anyone had the chance to find a workaround to access the message type
>> somehow? I would like even to read about "hackish" ways to achieve it.
>>
>>
>>
>> Thank you a lot in advance.
>>
>> David.
>>
>>
>>
>> --
>>
>> David "kraptor" Anes Alcolea
>> * @kraptor <http://twitter.com/kraptor> @simlaps
>> <http://twitter.com/simlaps>
>>
>> * linkedin.com/in/davidanes
>> * kraptor.com | simlaps.com | 900grados.es
>>
>
>
>
> --
> David "kraptor" Anes Alcolea
> * @kraptor <http://twitter.com/kraptor> @simlaps
> <http://twitter.com/simlaps>
> * linkedin.com/in/davidanes
> * kraptor.com | simlaps.com | 900grados.es
>  <http://simlaps.com>
>



-- 
David "kraptor" Anes Alcolea
* @kraptor <http://twitter.com/kraptor> @simlaps
<http://twitter.com/simlaps>
* linkedin.com/in/davidanes
* kraptor.com | simlaps.com | 900grados.es
<http://simlaps.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20140618/6b0efd21/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: MSG-wparam-and-message-types-Fix-PYSIDE84.patch
Type: application/octet-stream
Size: 718 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20140618/6b0efd21/attachment.obj>