Re: [Paraview] Forcing a Qt version

If there's a qmake in your PATH, it takes precedence over whatever you set QTDIR to be. By the way, the use of QTDIR has been deprecated by Trolltech. Another thing you can do is set QT_QMAKE_EXECUTABLE in the cmake-gui before you hit configure for the first time, and it won't matter what you

Re: [Paraview] [CMake] Forcing a Qt version

An updated FindQt4.cmake has been committed to CVS that makes this easier. If you change the qmake pointed to, the includes, libraries, etc... are re-found. So you can change the Qt you're using for your project simply by changing the QT_QMAKE_EXECUTABLE variable. Clint On Oct 8, 2008,

Re: [Paraview] Object Panel <-> Model Communication

If its because its an information property, I think adding a show="1" attribute to the property will make it show up. Clint Utkarsh Ayachit wrote: You will have to create a custom panel. Look at the custom panel example in Examples/Plugin. Utkarsh On Sat, Jan 3, 2009 at 4:29 PM, Nehme Bila

Re: [Paraview] CVS head crashes on Leopard at vtkCarbonRenderWindow

Sean McBride wrote: On 1/15/09 6:54 AM, David Cole said: Sean, would you mind (1) fixing this or (2) reverting your vtkCarbonRenderWindow change of 1.75 until somebody can figure out what it takes to fix this...? I've returned CVS to a working state. Sorry about the troubles! Clinto

Re: [Paraview] building code as part of paraview

I've updated the wiki with the information of where you can place plugins for paraview to pick them up automatically without setting PV_PLUGIN_PATH. There's a system-wide location (if paraview is installed that way), and a user specific l

Re: [Paraview] Compute cell area

What about the "Mesh Quality" filter? You can select "Area" for triangle and quadrilateral quality. You get a cell data array with results for each cell. Clint Moreland, Kenneth wrote: John, Thanks. I already look into both of those filters. Although both filters internally compute pol

Re: [Paraview] Windows / building error on pqCommandServerStartup

This should answer your question. http://www.qtsoftware.com/developer/task-tracker/index_html?id=228612&method=entry You can patch the qatomic_windows.h header file. Clint Pierre-Olivier Dallaire wrote: Hi, I'm trying to build ParaView on Windows using MinGW - does anybody had this error in

Re: [Paraview] Ver 3.4.0 Qt lib missing ?

What's the version of CMake you are using? Later versions of CMake can handle that problem. Some Linux distros don't install those development packages when the Qt development package is installed, which means they had to modify the Qt installation in ways that CMake's FindQt4.cmake didn't ex

Re: [Paraview] 64Bit Experiment

Attached is a patch if you wanted to build it too. It also needs cmake 2.6.3 if you want to build with Qt/Cocoa. And when you configure Qt 4.5, add the "-cocoa" and "-arch x86_64" flags to configure. The progress bar code in the patch isn't perfect yet. I didn't have any more time to debug it.

Re: [Paraview] 64Bit Experiment

Michael Jackson wrote: Thanks, I'll try to take a look at it. Also reported issue http://public.kitware.com/Bug/view.php?id=8671 against the FindQt4.cmake file. Patch is attached to the bug. Synopsis: The Carbon framework is being added to the link line when it should not when Qt4.5 built wi

Re: [Paraview] 64Bit Experiment

n McBride wrote: On 3/4/09 8:49 AM, Clinton Stimpson said: Thanks, I'll try to take a look at it. Also reported issue http://public.kitware.com/Bug/view.php?id=8671 against the FindQt4.cmake file. Patch is attached to the bug. Synopsis: The Carbon framework is being added to the link lin

Re: [Paraview] Problems in loading plugin

Here's a few things to check: Check your qconfig.h file in your Qt build to see if the QT_BUILD_KEY contains the whole "8.0.50727.867" version for the compiler. If so, then that's going to prevent it from working anyways. The QT_BUILD_KEY must be the same as what Kitware had when they built P

Re: [Paraview] qvtk problems with the pipeline

Dominik Szczerba wrote: My pipeline works all right and gets updated on demand properly. I achieve it by connecting spinboxes/lineedits etc. to functions that set parameters of my filters before I explicitly hit the final 'apply' button. The annoying problem is that the pipeline gets executed a

Re: [Paraview] qvtk problems with the pipeline

On 08/01/2009 05:01 AM, Dominik Szczerba wrote: Many thanks for the feedback. Pls see below: Clinton Stimpson wrote: Dominik Szczerba wrote: My pipeline works all right and gets updated on demand properly. I achieve it by connecting spinboxes/lineedits etc. to functions that set parameters

Re: [Paraview] OSX 10.6, Qt 4.5

:) A "configure -nomake examples -nomake demos" will cut off some time. The examples can be compiled on demand if you wanted. Clint On Tuesday 20 October 2009 02:47:34 pm Berk Geveci wrote: > I am too scared of Qt to change its build settings :-) Some probably > think the same about ParaView. >

Re: [Paraview] OSX 10.6, Qt 4.5

ilder.h) > > > Michael > > > Thanks. Just to add to the thread, fwiw, I ended up doing (after re- > > installing mysql, sigh): > > > > (path-to)/qt-all-opensource-src-4.5.3$ ./configure -opensource - > > cocoa - > > framework -arch x86_64 -nomake

Re: [Paraview] OSX 10.6, Qt 4.5

Oh, and that last email I sent had a patch on it removing some obsolete workarounds for older CMake versions. Not that it would help any, but they were workarounds in files you had issues with. Clint On Wednesday 21 October 2009 02:35:15 pm Clinton Stimpson wrote: > Did you set "-a

Re: [Paraview] Plugins in Windows 3.6.2 binary

I've not seen multiple versions of the CRT load unless it was VS 8 and VS 9 compiled code used together combined. Can you just remove the manifests from the plugins, by not embedding them? Clint On 01/05/2010 05:31 PM, Mike Jackson wrote: Loading 2 sets of MSVC libraries would make sense. Th

Re: [Paraview] Problem linking Cocoa pqWidgets

Did you use the CVS version of CMake? FindQt4/UseQt don't put the extra dependencies in there anymore unless Qt is static. So if pqWidgets uses Cocoa, it needs to link against the Cocoa framework. Clint On Wednesday 06 January 2010 01:35:39 pm Eric E. Monson wrote: > Hello, > > On one of my m

Re: [Paraview] Problem linking Cocoa pqWidgets

d in other framework dependencies (like > Carbon, ApplicationServices or AppKit) automatically based on what Qt was > built with? Correct. So, your suggestion to fix Qt/Widgets/CMakeLists.txt needs to happen. Clint > > Thanks, > -Eric > > On Jan 6, 2010, at 4:36 PM, Clinton St

Re: [Paraview] Plugins in Windows 3.6.2 binary

Can you fix that issue some people might have by not embedding the manifests into the plugin dlls, where embedding them is the default behavior? Clint On Wednesday 06 January 2010 03:58:54 pm Dave Partyka wrote: > Hi All, > > I have tracked down the issue. That being an inconspicuous Visual Stu

Re: [Paraview] Plugins in Windows 3.6.2 binary

x27;t work on non-updated systems. Clint On Wednesday 06 January 2010 04:06:01 pm Dave Partyka wrote: > So you're saying that if I don't embed any manifest (which the IDE does by > default) into the plugins it should just work? > > On Wed, Jan 6, 2010 at 6:02 PM, Clinton S

Re: [Paraview] X Error: BadLength on OpenSUSE11.2

I've seen BadLength errors when mixing mesa-dri and nvidia for glx client/server side. "glxinfo | grep -i vendor" in a terminal can probably verify that. Clint On Tuesday 26 January 2010 11:04:02 am Robert Sawko wrote: > Dear All, > > I was getting acquainted with ParaView features via tutoria

Re: [Paraview] Dashdoard Breakage

On Friday 19 March 2010 10:37:33 am Kevin H. Hobbs wrote: > On 03/19/2010 12:05 PM, Clinton Stimpson wrote: > > I'll fix it. I missed a few places with yesterday's fixes. > > > > Thanks, > > Clint > > If you send me a note when you're done, then I

Re: [Paraview] Dashdoard Breakage

I'll fix it. I missed a few places with yesterday's fixes. Thanks, Clint On Friday 19 March 2010 08:55:35 am Utkarsh Ayachit wrote: > Clint, > > Can you take a look at this please? It may have been a side effect of > your commit on March 17. > http://cmake.org/gitweb?p=cmake.git;a=commit;h=108