Just bringing this thread back to life.

 We are getting more into using PYQT here and I am looking into completely
replacing synoptics and use PYQT instead.

I was hoping somebody could help me figure out how to get information from
XSI sent to PYQT currently everything that I have done has been the
opposite, where PYQT drives something, but does very little evaluation of
the scene.

An example would be.

When a characters facial animation is animated, and the time slider scrubs,
I will need the PYQT slider that drives that facial animation to detect the
value change in XSI and show its new value in the menu.

Currently I don't really know how to do that, as the example SignalSlot
function that comes with this implementation only covers something with a
registered event.

Do I need to create onValueChanged events for every value on the rig?

any help would be awesome, I'm pretty new to PYQT still.

thanks,
 Enrique

On Wed, Feb 29, 2012 at 3:29 PM, Enrique Caballero <
[email protected]> wrote:

> For those of us using linux, is there an out of box PYQT implementation
> such as this that we can use?
>
>
>
> On Thu, Dec 8, 2011 at 6:45 AM, Alok Gandhi <[email protected]>wrote:
>
>> Oh ok, thanks for the info Steven.
>>
>>
>> On Wed, Dec 7, 2011 at 5:24 PM, Steven Caron <[email protected]> wrote:
>>
>>> well for your reference, i am using Alan Jones' cmake softimage module.
>>> it automates a lot of the process for creating softimage plugins with
>>> cmake. it can be found in the src\CMake\Modules folder. its very handy :)
>>>
>>> s
>>>
>>>
>>> On Wed, Dec 7, 2011 at 2:21 PM, Alok Gandhi 
>>> <[email protected]>wrote:
>>>
>>>> Yep that works too, I knew that it did not need shader lib for sure,
>>>> but was not sure, so I set the path anyways.
>>>>
>>>>
>>>> On Wed, Dec 7, 2011 at 2:08 PM, Steven Caron <[email protected]> wrote:
>>>>
>>>>> well it doesn't need that actually, let the entry in the cmake gui
>>>>> stay red. just hit generate... does this work for you?
>>>>>
>>>>>
>>>>
>>>> --
>>>>
>>>>
>>>
>>
>>
>> --
>>
>>
>

Reply via email to