[Paraview-developers] pqObjectInspector
Utkarsh Ayachit
utkarsh.ayachit at kitware.com
Wed Oct 22 14:11:04 EDT 2014
John,
Speaking of the "gear" thingy -- while it's believable there are bugs,
it's less likely since it's widely used and no one reported any issues
with it so far. Just to make sure we're clear in our expectations from
it, let me explain some of the usage details:
1. There are basically 2 types of properties -- advanced and default.
2. When the "gear" is pressed, all properties including the properties
labeled default or advanced are shown. When the "gear" is unpressed,
only the default properties are shown.
3. The search box is used to search for properties -- all properties,
including advanced and default, irrespective of the gear state. As
soon as you start typing, the gear gets disabled to indicate that it
doesn't matter what "mode" the panel was in, all properties are now
being searched.
4. The search matches the text typed with the label used for the
properties. Only those properties that have label text matching the
typed text will be shown, if there's non-empty text in the search box.
Utkarsh
On Wed, Oct 22, 2014 at 6:41 AM, Dan Lipsa <dan.lipsa at kitware.com> wrote:
> John,
> You can submitted your patches to gerrit for review.
>
> http://www.paraview.org/Wiki/ParaView/Git/Develop
>
> Dan
>
>
> On Wed, Oct 22, 2014 at 6:28 AM, Biddiscombe, John A. <biddisco at cscs.ch>
> wrote:
>>
>> Dan, Utkarsh
>>
>>
>>
>> Thanks for the links. (I didn’t want to use a property widget as I need
>> the apply button feature in my own dock window etc).
>>
>>
>>
>> I’m of the opinion that the greyed out buttons (for view/display/etc)
>> should be invisible if the panel mode does not include them.
>>
>> Attached is a patch to hide them. #001
>>
>>
>>
>> I needed to subclass panel properties to override some methods so that I
>> can intercept apply and other methods.
>>
>> Attached is a patch which makes a couple of functions virtual and also
>> adds a preapplied signal emitted before new properties are ‘applied’. #002,
>>
>>
>>
>> The gear search thingy seems very broken - I’ll submit a patch if and when
>> I find what’s wrong.
>>
>>
>>
>> it’d be lovely if these patches could be applied to master.
>>
>>
>>
>> (PS. any news of when I can do this via a github #PR and have it part of
>> the accepted means of contributing?)
>>
>>
>>
>> thanks very much, all seems to be working as before now, (subject to a few
>> ongoing tweaks)
>>
>>
>>
>> JB
>>
>>
>>
>> From: Dan Lipsa [mailto:dan.lipsa at kitware.com]
>> Sent: 20 October 2014 16:28
>> To: Biddiscombe, John A.
>> Cc: paraview-developers at paraview.org
>> Subject: Re: [Paraview-developers] pqObjectInspector
>>
>>
>>
>> See also
>>
>>
>> http://www.paraview.org/Wiki/Plugin_HowTo#Adding_Customizations_for_Properties_Panel
>>
>>
>>
>> Dan
>>
>>
>>
>>
>>
>> On Mon, Oct 20, 2014 at 10:25 AM, Dan Lipsa <dan.lipsa at kitware.com> wrote:
>>
>> Hi John,
>>
>> Not a direct answer to your question but I found the following wiki entry
>> useful in adding/debugging entries in the properties panel.
>>
>> See especially the environment variable PV_DEBUG_PANELS
>>
>>
>>
>> http://www.paraview.org/Wiki/ParaView/Properties_Panel
>>
>>
>>
>> Dan
>>
>>
>>
>>
>>
>> On Mon, Oct 20, 2014 at 9:52 AM, Biddiscombe, John A. <biddisco at cscs.ch>
>> wrote:
>>
>> I managed to get something working with a pqPropertiesPanel and creating
>> my own pqPipelineSource, so properties become visible.
>>
>>
>>
>> Question:
>>
>> My panel has SOURCE_PROPERTIES set, but I get two (of each) greyed out,
>> save and default buttons for (presumable) the view properties and display
>> properties which I don’t need. Can I make them hidden?
>>
>>
>>
>> There appears to be a bug in the advanced properties gear button thingy,
>> because one you type something in there, everything disappears and never
>> comes back! (I noticed in the main preferences, lots of options are hidden
>> until you enter a space in the search box, then tons appear - as if by magic
>> - could there be something wrong with the property search feature?)
>>
>>
>>
>> ta
>>
>>
>>
>> JB
>>
>>
>>
>> From: Paraview-developers
>> [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Biddiscombe,
>> John A.
>> Sent: 17 October 2014 14:48
>> To: paraview-developers at paraview.org
>> Subject: [Paraview-developers] pqObjectInspector
>>
>>
>>
>> I used to use pqObjectInspector quite heavily, in fact my plugin has a
>> subclass of it which displays all the properties of my live-viz manager
>> class inside a window.
>>
>> Now that pqObjectInspector has gone, I tried to use a pqPropertiesPanel,
>> but it does not have a setProxy method, and only seems to want
>> pqPipeLinesource objects.
>>
>>
>>
>> is there something I can use to display all my stuff and have an
>> accept/reset button like the old object inspector ?
>>
>>
>>
>> thanks
>>
>>
>>
>> JB
>>
>>
>>
>> --
>>
>> John Biddiscombe, email:biddisco @.at.@ cscs.ch
>>
>> http://www.cscs.ch/
>>
>> CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07
>>
>> Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82
>>
>>
>>
>>
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>>
>>
>>
>
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
More information about the Paraview-developers
mailing list