Experimental Physics and
Industrial Control System

Mark Rivers <[email protected]> · Tue, 29 May 2018 13:26:29 +0000

Hi Lewis,

Even if you succeed in opening simDetector.opi from the command line you will soon run into another problem.  The simDetector.opi file has related displays for many other opi files, i.e. for the plugins, for the asynRecord, sseq record, etc.  These will fail to open.

As far as I know CSS does not have the equivalent of medm's EPICS_DISPLAY_PATH to tell it where to look for other opi files.  Rather in CSS the path can be specifically specified in each screen to find the related display.  However, this does not work for autoconverted medm files, and in general is hard to manage for generic software distributions like areaDetector and synApps.

Here is what I do that seems to work well.  I have a little script that copies all of the opi files in the synApps/support tree to a single directory.  Note that in practice this is also what I do for medm, and then I set EPICS_DISPLAY_PATH to this single directory.

corvette:ADCore/ADApp/ADSrc>more ~/bin/sync_opis_devel
opidir=/home/epics/opi_devel/
opipath='/home/epics/devel'
find $opipath -name '*.opi' -exec cp -f -p {} $opidir \;

/home/epics/devel is what might also be called /home/epics/synApps/support.  It contains asyn, areaDetector, the rest of synApps modules, etc.

So this script copies all of the opi files to /home/epics/opi_devel.

I then open CSS with no command line arguments and then use File/Open in CSS to open the top-level display, for example ADTop.opi.  From there I can open simDetector.opi and all related displays, and CSS will find them with no problem because they are all in the same directory as ADTop.opi.

Mark

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of J. Lewis Muir
Sent: Friday, May 25, 2018 5:43 PM
To: EPICS Tech-Talk <[email protected]>
Subject: Open .opi filenames with spaces from command line?

Hello.

According to:

  http://cs-studio.sourceforge.net/docbook/ch29.html

the way to open a .opi file from the command line is:

===
$ css --launcher.openFile some_file.opi
===

Will that work if the .opi file has a space in its name?

For example:

===
$ css --launcher.openFile 'some file.opi'
===

I'm asking because I looked at the "--launcher.openFile" option documentation at:

  https://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fruntime-options.html

and it says:

  --launcher.openFile <space separated list of files> (Executable)

    a space separated list of files to pass to the application. This
    option is typically used to pass a list of files to be opened
    by an Eclipse application. This option requires SWT in order
    to fire the necessary SWT_OPENDOC event for the files that are
    specified. Relative paths will be resolved first against the current
    working directory, and second against the eclipse program directory.

Obviously, if a space is used as the list delimiter, there needs to be a way to escape a space, or otherwise specify the list, when you don't want it to be interpreted as a list delimiter.

Thanks,

Lewis

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System