[Paraview] Qt 4.6 Cocoa Strangeness with ParaView 3.6.2

[Michael Jackson]

Utkarsh,
   I was able to pull the latest CVS HEAD for ParaView and compiled  
that against the Qt 4.6.1 Cocoa build that I have and it seems that  
what ever was changed on CVS HEAD fixed the problem.

Thanks for the heads up.
___________________________________________________________
Mike Jackson                      www.bluequartz.net

On Feb 19, 2010, at 4:49 PM, Utkarsh Ayachit wrote:

> We've started supporting Cocoa only with ParaView CVS (and in future
> with 3.8). Can you see if you can reproduce the issue with CVS? There
> have been several fixes to CVS to work with Cocoa.
>
> Utkarsh
>
> On Fri, Feb 19, 2010 at 4:37 PM, Michael Jackson
> <mike.jackson at bluequartz.net> wrote:
>> I'll state up front that I know 3.6.2 only officially supports Qt  
>> 4.3.x but
>> I'll go ahead with my bug report/question any ways.
>>
>>  So I built Qt 4.6.1 with Cocoa (OS X) and then compiled ParaView  
>> 3.6.2 from
>> source using shared libraries. Everything compiles fine. ParaView  
>> then
>> launches fine. I setup up some sort of pipeline (Does not matter  
>> what) then
>> the strangeness happens. For example, load up a Box source, then  
>> glyph it.
>>
>>  Now, click on the "Glyph1" to activate it. Now, click on the  
>> Display tab to
>> adjust some parameter (Again, does not matter what). Now Click back  
>> on the
>> "Box1" in the Pipeline Browser. Now try to click on the  
>> "Properties" or
>> "Information" tabs. What happens is that the Object inspector  
>> windows goes
>> blank and the Pipeline Browser elements all become un-selected.
>>
>>  It seems the only way to select a new element in the Pipeline  
>> browser and
>> have it "stick" to to actually double-click on a pipeline browser  
>> element.
>> Then you can select something in the "Object Inspector" area.
>>
>>  If I build with Qt 4.6.1 with Carbon none of this happens. I will  
>> assume
>> that this is a problem with Qt itself since switching to Qt/Carbon  
>> seems to
>> fix the problem. Just wondering if anyone else has seen this  
>> behavior. I can
>> reproduce it on a Mac Pro (Xeon 5500 with ATI 4870) and a MacBook  
>> Pro with
>> nVidea 8600m graphics.
>>
>>  What I have not tried is to go back to Qt 4.5.3 Cocoa/Carbon and  
>> try those
>> to see if they work/don't work.
>>
>> Thanks for any feedback.
>> ___________________________________________________________
>> Mike Jackson                      www.bluequartz.net
>> Principal Software Engineer       mike.jackson at bluequartz.net
>> BlueQuartz Software               Dayton, Ohio
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.paraview.org/mailman/listinfo/paraview
>>