You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@wroy-ca, it was a good idea to create a ticket for it for future reference, thanks for that! Looks like the Qt folks unfortunately haven't got around looking into that issue yet. I'm wondering at this point if it's worth looking at some Qt internals and sending them a patch for that, as this issue has been created ages ago.
@wroy-ca, it was a good idea to create a ticket for it for future reference, thanks for that! Looks like the Qt folks unfortunately haven't got around looking into that issue yet. I'm wondering at this point if it's worth looking at some Qt internals and sending them a patch for that, as this issue has been created ages ago.
It is as you said. Meanwhile, I believe I’d be worth it to investigate QDirect3D12Widget::event to figure out what and/or which commit caused the regression so that a workaround can be made, once again, for the time being. This is assuming that it worked fine prior to the day. 🙂
Edit:
The issue is now more explicit that this is about the workaround not working anymore rather than the Qt bug itself. I apologies for the confusion—if any—.
ghost
changed the title
Key strokes are not received by QKeyEvent.
Key strokes are not received anymore with the QKeyEvent workaround.
Aug 23, 2021
ghost
changed the title
Key strokes are not received anymore with the QKeyEvent workaround.
Key strokes are not received anymore with the QTBUG-42183 workaround.
Aug 23, 2021
Following #11 (comment) brought to my attention that key strokes are not received anymore with the QTBUG-42183 workaround.
QtDirect3D/source/QDirect3D12Widget/QDirect3D12Widget.cpp
Lines 481 to 523 in 91dd31c
The text was updated successfully, but these errors were encountered: