Databases
StackOverflow2013
Postsdbo
POImageJ GenericDialog - String containing backslashes is not escaped when recording macro
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POImageJ GenericDialog - String containing backslashes is not escaped when recording macro
    primarykey
    data
    text
    <p>I am developing an ImageJ plugin and I ran into this problem. </p> <p>I am using <code>GenericDialog</code> with a text field so the user can input a file system path to a file. On windows, the path contains backslashes. When I am recording a macro for this plugin, I get this result:</p> <pre><code>run("Example ", "path=C:\results.txt"); </code></pre> <p>The backslash is not escaped and when i try to run the recorded command, the backslash is interpreted as an escape character and obviously, the file can't be found.</p> <p>Is there a way to use <code>GenericDialog</code> in a way that it correctly records text field containing backslashes? Or I can't use <code>GenericDialog</code> and have to implement macro recording functionality myself?</p> <p>EDIT: example plugin with the problem:</p> <pre><code>import ij.IJ; import ij.ImagePlus; import ij.gui.GenericDialog; import ij.plugin.filter.ExtendedPlugInFilter; import ij.plugin.filter.PlugInFilter; import ij.plugin.filter.PlugInFilterRunner; import ij.process.ImageProcessor; public class Example_ implements ExtendedPlugInFilter { public int showDialog(ImagePlus imp, String command, PlugInFilterRunner pfr) { GenericDialog gd = new GenericDialog("Example"); gd.addStringField("path", "C:\\results.txt"); gd.showDialog(); String path = gd.getNextString(); IJ.showMessage("path = " + path); return PlugInFilter.DONE; } public void setNPasses(int nPasses) { } public int setup(String arg, ImagePlus imp) { return PlugInFilter.NO_IMAGE_REQUIRED; } public void run(ImageProcessor ip) { } } </code></pre> <p>When i run the macro recorded from this plugin, it shows "path = C:esults.txt".</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJosef Borkovec
    1. USJosef Borkovec
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COThat's apparently a bug in the macro recorder. Chances are high that this will be fixed quickly if you report this to the [ImageJ mailing list](http://imagej.nih.gov/ij/list.html).
      singulars
      1. POImageJ GenericDialog - String containing backslashes is not escaped when recording macro
      1. USJan Eglinger
    2. COWith an up-to-date version of [Fiji](http://fiji.sc/Fiji) (ImageJ 1.47s), the macro recorder records `run("Results... ", "open=C:\\results.txt");` when I run the command _File > Import > Results..._. Did you check if your ImageJ version is up to date? My ImageJ doesn't know the command "Import results", but only "Results...", are you sure you're using the correct command?
      singulars
      1. POImageJ GenericDialog - String containing backslashes is not escaped when recording macro
      1. USJan Eglinger
    3. CO`Import results` in this case is not the built-in command but a plugin i am developing. I will add a SSCCE to the question shortly.
      singulars
      1. POImageJ GenericDialog - String containing backslashes is not escaped when recording macro
      1. USJosef Borkovec
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload