its a key event inside softimage. if a widget is in focus we stop softimage from getting it and send it to qt. so if there is no qapplication running, its passed through. if there is one, it tests if its focused.
i wouldn't worry about that until the damn thing shows parented under softimage window. On Tue, Jan 22, 2013 at 5:21 PM, ran sariel <[email protected]> wrote: > when is the qt_events.py being called?, > I used the example to get the anchor (cast through sip), and pass it as a > parent to my Dialog, maybe I'm missing something... > > > > > On Tue, Jan 22, 2013 at 4:47 PM, Steven Caron <[email protected]> wrote: > >> i need to double check with jo, but i thought the lisenter wasn't >> necessary. it was an incomplete attempt at implementing the key events in >> cpp. the python code in qt_events.py handles the key events using a >> softimage key up/down event and forwarding it to the qt app. >> >> i have been meang to remove it and test on windows, just not much time >> lately. >> s >> >> >> On Tue, Jan 22, 2013 at 4:33 PM, ran sariel <[email protected]> wrote: >> >>> >>> Hi Steven >>> >>> Tried the reparent method for X and managed to compile and link it on >>> centos6.2, >>> the app and widget are created on the plugin side, the anchor is >>> parented to the app handle (or at least doesn't tell me that it's failing) >>> The thing is that the "show" method doesn't raise the dialog that I >>> create and parent to the "anchor" widget. >>> I still need to figure out how to implement the listener function on X, >>> (wasn't sure if it was needed just to get the dialog to show...), hoping >>> that this will lead to the same behavior you have on Windows. let me know >>> if you have any insights on this one. >>> >>> Cheers >>> Ran >>> >>> >>> >>> On Fri, Jan 18, 2013 at 5:26 PM, Steven Caron <[email protected]> wrote: >>> >>>> well i think you might need to use the os specific function for >>>> parenting, otherwise we would have used the Qt method. if there is a Qt >>>> method for parenting then i might handle the platform for us and make the >>>> code work on both operating systems. but i think you will need to use the >>>> os specific function call, which i linked to in the email. >>>> >>>> you are correct about the plugin's design, use cpp to setup the >>>> application and a dummy widget that you return to scripting. all subsequent >>>> widgets are parented to (in python) using the return value. >>>> >>>> s >>>> >>>> >>>> >>>> On Fri, Jan 18, 2013 at 5:12 PM, ran sariel <[email protected]>wrote: >>>> >>>>> so you're creating the app on the plugin, and create a "dummy widget" >>>>> (sianchor) , as a child of xsi main window. >>>>> and from there on any widget you create is parented under siacnchor. >>>>> I believe the return of getApplicationWindowHandle on linux is an x >>>>> window, >>>>> there should be a way in qt to parent a widget to x window, - never >>>>> used it though, Will take a look on Monday, and see if I can make any >>>>> progress there. >>>>> >>>> >>> >> >
