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

setantialiasing not working if set too early #1447

Closed
doutriaux1 opened this Issue Jul 7, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@doutriaux1
Member

doutriaux1 commented Jul 7, 2015

429: /lgm/uvcdat/2015-07-06/lib/python2.7/site-packages/vcs/VTKPlots.py:950: UserWarning: no RenderWindow ready, skipping setantialiasing call, please reissue at a later time
429:   warnings.warn("no RenderWindow ready, skipping setantialiasing call, please reissue at a later time")

I think if the rendering window is not present, this call should still set some value somewhere that will be used when the rendering window is created.

@doutriaux1 doutriaux1 added this to the 2.3 milestone Jul 7, 2015

@sankhesh

This comment has been minimized.

Contributor

sankhesh commented Jul 9, 2015

This issue is fixed with my antialiasing branch and is merged in master.
The antialiasing value is cached and later used when creating the render window

Ref: de85f8f?diff=unified

@sankhesh sankhesh closed this Jul 9, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment