MantisBT - ParaView
View Issue Details
0011251ParaViewFeaturepublic2010-09-20 14:082010-10-27 21:01
Utkarsh Ayachit 
Sebastien Jourdain 
normalminorhave not tried
closedfixed 
 
3.10 
0011251: Mechanisms to distribute macros with Paraview
Mechanisms to distribute macros with Paraview.
No tags attached.
related to 0009672closed Sebastien Jourdain Separate Python tracing/macros from Python shell dialog 
Issue History
2010-09-20 14:08Utkarsh AyachitNew Issue
2010-09-20 14:08Utkarsh AyachitStatusbacklog => tabled
2010-09-20 14:08Utkarsh AyachitAssigned To => Sebastiennn Jourdain
2010-09-20 14:08Utkarsh AyachitRelationship addedrelated to 0009672
2010-09-27 10:43Sebastien JourdainNote Added: 0022368
2010-09-27 10:43Sebastien JourdainStatustabled => @80@
2010-09-27 10:43Sebastien JourdainFixed in Version => 3.10
2010-09-27 10:43Sebastien JourdainResolutionopen => fixed
2010-10-27 21:01Alan ScottNote Added: 0022723
2010-10-27 21:01Alan ScottStatus@80@ => closed
2011-06-16 13:10Zack GalbreathCategoryFeature Request => Feature

Notes
(0022368)
Sebastien Jourdain   
2010-09-27 10:43   
Fixed provided inside the commit 8d67360bcc130352b75f5ff8c334ca09b729cf74

- Now the storage of macros is on the filesystem directly
- When a macro is added, the script file is copied into a ParaView user specific configuration directory.
- When a macro is deleted, the script file is kept inside the same ParaView Macros directory but it is renamed with a dot at the head of the filename
- The macro list is retreived by listing the content of application and user "Macros" directory.
- If two created/deleted macro have the same name the newest is renamed with the following pattern fileName-X.py where X is an integer that start at one and is incremented till the file do not exist.
(0022723)
Alan Scott   
2010-10-27 21:01   
Tested local server, Windows, trunk.