|
Notes |
|
|
(0022343)
|
|
Sebastien Jourdain
|
|
2010-09-24 16:10
|
|
|
|
|
(0022504)
|
|
Alan Scott
|
|
2010-10-15 20:53
|
|
I don't see either how to do this, or where it is documented on the Wiki. Mind giving me some directions?
Thanks! |
|
|
|
(0022658)
|
|
Sebastien Jourdain
|
|
2010-10-22 10:01
|
|
commit d37a8cd2233b59747c285a4a348ef4952997768e
Merge: f5f9a47 2d052f1
Author: Sebastien Jourdain <sebastien.jourdain@kitware.com>
Date: Fri Oct 22 09:52:11 2010 -0400
Merge topic 'python-trace-ui'
2d052f1 Change strategy around Python trace usage
commit 2d052f1d9ba54bbdee6cc9b89bbb8f01095adf39
Author: Sebastien Jourdain <sebastien.jourdain@kitware.com>
Date: Fri Oct 22 09:43:19 2010 -0400
Change strategy around Python trace usage
Now the user can only start/stop trace. When the user stop a trace,
the Python editor Popup with the content of the trace. The user has
to choose what he wants to do with it. He can discard it, save it as
a file or save it as a Macro.
Caution: As only one editor is used for Python code editing inside
ParaView. If the user do not save its trace and re-run
another one, when it stop it, the editor will be reset
to the later trace content. The same thing happen when
you try to edit a Macro while the editor is open. |
|
|
|
(0022720)
|
|
Alan Scott
|
|
2010-10-27 20:49
|
|
|
Excellent. Tested local server, Windows, trunk. |
|