Sorry, misread your reply, sounds like you would prefer to keep
visit-bridge on. But will you disabled point-sprite in the binary
release? I noticed that when the client has it but server does not it
causes a crash.
On 03/05/2012 11:11 AM, Burlen Loring wrote:
So are you disabling VisIt bridge in the binary release? If not would
it still lead to a crash if the binary has VB on, and the server has
VB off?
On 03/05/2012 11:21 AM, Utkarsh Ayachit wrote:
Yes, I believe we ran into that as well. Short of re-factoring the
PointSpritePlugin, the work around for now is to disable the
point-sprite plugin when using visit-bridge and static builds.
Utkarsh
On Mon, Mar 5, 2012 at 1:36 PM, Burlen Loring<blor...@lbl.gov> wrote:
Utkarsh,
By the way, not a huge issue but I also had a problem with static
builds
when trying to enable the visit bridge. The visit bridge and the Point
Sprite Pluign both had copies of some of the same code.
http://paraview.org/Bug/view.php?id=12972
Burlen
On 03/05/2012 10:12 AM, Utkarsh Ayachit wrote:
Burlen,
To give you an update, we have decided to put out a patch release
within the next week or so that should include the fix for this bug.
Utkarsh
On Wed, Feb 29, 2012 at 6:41 PM, Burlen Loring<blor...@lbl.gov>
wrote:
That seems to have fixed the problem, thanks Utkarsh!
On 02/29/2012 03:43 PM, Utkarsh Ayachit wrote:
Burlen,
Attached is a patch. Can you please verify if that solves the issue?
Seems to working now in my tests.
Thanks
Utkarsh
On Wed, Feb 29, 2012 at 3:33 PM, Utkarsh Ayachit
<utkarsh.ayac...@kitware.com> wrote:
Burlen,
I haven't tried reproducing the problem, but looking at the
code, it's
pretty obvious why it could fail. I'll work on a fix soon. I think
this and few other state file backwards compatibility related
issues
that been reported may warrant a quick patch release. But I'll
check
with the team once I get back next week and give everyone an
update.
Utkarsh
On Wed, Feb 29, 2012 at 10:43 AM, Burlen Loring<blor...@lbl.gov>
wrote:
Hi Rick,
yes things are fine in 3.12 it's only with 3.14 that I'm having
this
issue.
Burlen
On 02/29/2012 10:52 AM, Angelini, Richard C CIV (US) wrote:
Burlen - I've been testing with 3.12, not 3.14 ... did things
work
for
you
in 3.12 and they are now broken in 3.14?
________________________________
Rick Angelini
USArmy Research Laboratory
Computational Sciences Division/Computing Architectures Branch
HPC Architectures Development Team
ARL/DSRC (DoD Shared Resource Center) Data Analysis&
Assessment
Center
Phone: 410-278-6266
________________________________________
From: Burlen Loring [blor...@lbl.gov]
Sent: Wednesday, February 29, 2012 1:29 PM
To: Angelini, Richard C CIV (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] 3.14 pvsc enumeration issues
Hi Rick,
Good, maybe it's something specific to my configuration
although I
don't
have any idea what it could be off hand. Just to be sure: do
you mean
that you haven't had noticed problems or that you've positively
verified
that after using the enum once you could change the value?
thanks
Burlen
On 02/29/2012 10:31 AM, Angelini, Richard C CIV (US) wrote:
What platform is the client running on? We make extensive
use of
pvsc
and enumerations and have not seen this (mis)behavior on our
Mac/Linux
client workstations......
________________________________
Rick Angelini
USArmy Research Laboratory
Computational Sciences Division/Computing Architectures Branch
HPC Architectures Development Team
ARL/DSRC (DoD Shared Resource Center) Data Analysis&
Assessment
Center
Phone: 410-278-6266
________________________________________
From: paraview-boun...@paraview.org
[paraview-boun...@paraview.org]
on
behalf of Burlen Loring [blor...@lbl.gov]
Sent: Wednesday, February 29, 2012 12:58 PM
To: paraview@paraview.org
Subject: [Paraview] 3.14 pvsc enumeration issues
Hi,
I've encountered bugs with pvsc enumerations in version
3.14.0. I
have
the attached pvsc that makes use of a couple of enumerations.
After
connecting once w/ this pvsc, neither of the enums save the
user's
choice in the GUI the next time the server is used. However they
seem
to
remember the user's last choice internally and always uses that
instead
of what the user has selected in the GUI. Neither setting
save=false
or
removing the default attribute helps. I filed the bug report
here.
http://paraview.org/Bug/view.php?id=12969 If it's confirmed
would
the
bug be fixed in another 3.14 release? or should I simply remove
enumerations from our pvsc's for 3.14?
Burlen
_______________________________________________
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
_______________________________________________
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