On Windows, stack trace records paths with backslash, saving as macros fails expecting forward slash
I am operating on Windows 10. I loaded a dataset, did some operations including merge blocks, exterior surface, and triangulate. I started the trace recorder (tools->start trace0and did a save data, checking enable coloring. Then I stopped the trace recording (tools->stop trace) and in the trace recording popup window I selected 'save as macro.'
Because of the way I chose my output file during the save data dialog, e.g. D:\external_suface_triangle_ply_files\reload_testing\triangles_out_1.ply (with back slashes),
the macro failed to work--it said it could not open the .ply file. When I went in and changed the backslashes to forward slashes by hand, the macro worked.
I think this only comes up if you do something like use the windows file explorer to get the path to the directory you want to use and do a copy/paste into the paraview save data dialog file selection. But it works correctly when you do it in the gui, but it fails in the python macro.
In the (broken) macro the save data call looks like
SaveData('D:\external_suface_triangle_ply_files\reload_testing\triangles_out_1.ply', proxy=triangulate4, EnableColoring=1, ColorArrayName=['POINTS', 'VON_MISES'], LookupTable=vON_MISESLUT)
changing '' to '/' enables the macro to work.
The fix needs to be for either the macro saving to correct the paths to '/' or have SaveData be okay with either '' or '/' in the file path, or change everywhere to use the os path file separator function to get the right thing (which is probably problematic in client-server with the server on one O/S and the client on another).
Maybe accept '' in SaveData on windows but issue some kind of warning? Maybe just change '' to '/' in paths in trace recordings or macro saves?