Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't keep "Solid Color" in export from Paraview #408

Closed
liamtimms opened this issue Aug 2, 2021 · 2 comments
Closed

Can't keep "Solid Color" in export from Paraview #408

liamtimms opened this issue Aug 2, 2021 · 2 comments

Comments

@liamtimms
Copy link

liamtimms commented Aug 2, 2021

Hi,

I am attempting to export a scene from Paraview desktop into Paraview Glance. In the simplest case, I have a .vtp surface which I am selecting to display as a "Surface" in Paraview with coloring defined as "Solid Color" and a color selected from the "Basic Colors" provided in the Paraview color picker. I can successfully export this scene into an embedded Paraview Glance instance .html file using the procedure outlined here: https://blog.kitware.com/exporting-paraview-scenes-to-paraview-glance/

However, when loaded the display always defaults to a "Scalars_" coloring and the "solid color" option must be manually selected to recover the intended representation. The following errors are given:

ParaViewGlance: 4.17.1
Mozilla/5.0 (X11; Linux x86_64; rv:90.0) Gecko/20100101 Firefox/90.0

attempt to set zero width color range
attempt to set zero width color range
attempt to set zero width color range

There does not appear to be an issue with the solid color representation once it is manually selected, it displays as intended. However in cases where we have multiple surfaces, asking each viewer to manually change each individual surface to a "Solid Color" is unreasonable.

An example of the html is available here: https://liamtimms.net/paraview/test_simple_artery.html

@liamtimms liamtimms changed the title Can't set colors in export Can't keep "Solid Color" in export from Paraview Aug 2, 2021
@liamtimms
Copy link
Author

Workaround is setting up and saving glance displays directly instead.

@hbraunDSP
Copy link

My team has encountered what I believe is the same bug. I opened a new issue at #504.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants