[Paraview-developers] {Int, Double}VectorProperties now require a {Int, Double}RangeDomain element?

[Kyle Lutz]

It uses qDebug() to print the messages so you would need a debug build
(i.e. CMAKE_BUILD_TYPE = "Debug").

-kyle

On Thu, Dec 6, 2012 at 10:55 PM, Biddiscombe, John A. <biddisco at cscs.ch> wrote:
> Kyle
>
>> Could you run ParaView with the PV_DEBUG_PANELS environment variable set?
>
> Didn't produce any output on the command prompt or elsewhere. Do I  need to rebuild with an extra option set?
>
> JB
>
> -----Original Message-----
> From: Kyle Lutz [mailto:kyle.lutz at kitware.com]
> Sent: 06 December 2012 23:10
> To: Cory Quammen
> Cc: Biddiscombe, John A.; ParaView Developers
> Subject: Re: [Paraview-developers] {Int, Double}VectorProperties now require a {Int, Double}RangeDomain element?
>
> Hi John, Cory,
>
> Could you run ParaView with the PV_DEBUG_PANELS environment variable set? This will cause ParaView to print out why (or why not) each panel widget item was created. Looking though the list for your property should give some insight on what is happening.
>
> -kyle
>
> On Thu, Dec 6, 2012 at 1:52 PM, Cory Quammen <cquammen at cs.unc.edu> wrote:
>> I just looked through the history up to v3.98.0 and didn't see any
>> obvious changes that would make it revert to this behavior.
>>
>> I'll see if I can reproduce.
>>
>> Cory
>>
>>
>> On Thu, Dec 6, 2012 at 4:20 PM, Biddiscombe, John A.
>> <biddisco at cscs.ch>
>> wrote:
>>>
>>> Cory
>>>
>>>
>>>
>>> >
>>>
>>> The patch is in ParaView 3.98, and it was for ints as well. Do
>>> default domains for doubles show you the numeric entry in the GUI?
>>>
>>> <
>>>
>>>
>>>
>>> Nope. The double vectors have the same problem. No input box/field in
>>> the gui.
>>>
>>>
>>>
>>> JB
>>>
>>>
>>
>>
>>
>>
>> --
>> Cory Quammen
>> Research Associate
>> Department of Computer Science
>> The University of North Carolina at Chapel Hill
>>