On Thu, Feb 10, 2011 at 03:48:09PM +0000, Juha Jäykkä wrote: > Now, I thought setting mlab.gcf().scene.disable_render to "True" would > prevent the rendering during these changes, but it does not seem to be > so. Indeed, it does not even prevent re-rendering during the changes!
That seems wrong. I my experience disable_render works. There have been some buggy functions that were reseting it to false (for instance mlab.clf()). But we fixed all that we found. Do you have a small example demonstrating this bug (disable_render not working). It would help us find the problem. > The cause of the problems is mlab.pipeline.threshold-object's methods > upper_threshold and auto_reset_upper. (I need auto_reset to find the > new maximum value, but then I immediately want to change it to 0 in > case the maximum was > 0 - this is just a way of making sure I never > set an upper limit larger than what is present in the data, which > causes other error messages. Those errors are unnecessary, in my > opinion, but that's a design decision, not a bug.). Yes, I agree that this behavior is not optimal. I have already hit it in other settings. However, this behavior is fairly deepely rooted in the way we validate input with Traits. I am Ccing the enthought-dev mailing list to see if anybody has a good suggestion. One way of working around this mis-feature would be to sublass the Trait to have one that simply thresholds using a converted, as CFloat does it. Enthought-dev people, what would you think about this option? > P.S. Is the citation still "P. Ramachandran and G. Varoquaux, Computing in > Science and Engineering (2011)" or do you have the volume and page numbers > already? The preprint will be out - hopefully - today. The publisher is doing the page layout right now. The volume will be March/Apri 2011 (vol. 13 issue. 2). It's a special edition on Python in Science. Should be interesting, hopefully. Gaël ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ MayaVi-users mailing list MayaVi-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mayavi-users
