Dear Burlen,
Thank you for your comments. It does not look like the Xdmf reader has
any custom panel methods. It does, however, have some logic which
caches file-data characteristics before-after RequestInformation(),
which might be wrong-footing state file loading?
(
Hi guys,
Issue #13317 should be fixed in ParaView-master.
Also, I added a debug flag to help track down these apply button
issues. Doing export PV_DEBUG_APPLY_BUTTON=1 before running ParaView
will cause messages similar to the following to be output to the
console:
$ export
Hi Ian,
You mention ver 3.14 and loading state files. so to me it sounds likely
to be a different bug. if the xdmf reader makes use of the new
properties panel it may have been fixed. All of this is pure speculation
on my part. Kyle is the authority.
Burlen
On 09/13/2012 10:38 AM, Ian
Hello Burlen, Kyle,
I am noticing very similar UIstate file related marked as
modified problems, and wonder if it can be related. Please see
report at: http://paraview.org/Bug/view.php?id=13317
Any suggestions?
-Ian
Wednesday, August 15, 2012, 5:20:32 PM, you wrote:
Hi Burlen,
Could you try the panels with the newest ParaView from git?
The display button should move to the bottom if it is collapsed and
the properties section is filled up with widgets.
-kyle
On Wed, Aug 15, 2012 at 4:31 PM, Burlen Loring blor...@lbl.gov wrote:
Hi Kyle,
Have you noticed
Hi Kyle, It's looking great, and working well. I like your new design a lot.
Burlen
On 08/28/2012 07:09 AM, Kyle Lutz wrote:
Hi Burlen,
Could you try the panels with the newest ParaView from git?
The display button should move to the bottom if it is collapsed and
the properties section is
Hi Burlen,
On Mon, Aug 13, 2012 at 8:50 AM, burlen burlen.lor...@gmail.com wrote:
I've noticed that the slice filter is having similar issue: apply activated
by selecting in the pipeline browser. In my panels this was because pv is
creating/destroying the panel as the object is
Hi Kyle,
Thanks, the following steps reproduce slice filter issue:
start paraview, build the following pipeline:
wavelet source - slice
in the pipeline browser:
select wavelet, select slice, select wavelet
The slice filter is marked modified.
Is there going to be a way of undocking the
Hi Kyle,
Have you noticed that sources with 3d widgets (eg line source) have
duplicate entries?
I just pulled from master and saw the new property and display buttons
to collapse their respective properties, that's nice! It would be great
if when collapsed the display button would then move
I've noticed that the slice filter is having similar issue: apply
activated by selecting in the pipeline browser. In my panels this was
because pv is creating/destroying the panel as the object is
selected/deselected in the browser so I had to be more careful during
the initialization not to
Hi Utkarsh,
I'm noticing a that custom panels derived from
pqAutoGeneratedObjectPanel don't respect the new panel_visibility
attribute, however they still honor the property show hint. Is this
going to change for the next release?
Also having some weird issues in custom panels derived from
Burlen,
Kyle can give you more details, but the theme is that
pqAutoGeneratedObjectPanel and related classes are going to be
deprecated. For backwards compatibility sake, these will be around for
the next release and when a custom-panel is provided using the past
mechanisms, ParaView will indeed
Burlen,
Incidentally just yesterday we were discussing that it won't be long
before we see an email on the mailing list asking where are my filter
properties :)? And to avoid that, we had decided to change the
default behavior to remain consistent with the past versions
I attempted to use my plugin with the master branch today and ran into
some UI issues.
I found it confusing that none of the properties were displayed until I
hit the advanced button. Is there a way to make all the properties show
up by default?
also, properties that were hidden via the
14 matches
Mail list logo
