1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 <2016> 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 <2016> 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: BOY Linking Container doesn't support OPI Search Path? |
From: | Phil Atkin <[email protected]> |
To: | "Pearson, Matthew R." <[email protected]> |
Cc: | "[email protected] list" <[email protected]> |
Date: | Fri, 29 Jan 2016 16:17:21 +0000 |
Matt, Thanks - it seems like that would work for me. I'll give it a try. Just for completeness: I guess it's -share_link, not -share-link? I don't suppose this is documented anywhere? Cheers, Phil On 29/01/2016 15:03, Pearson, Matthew
R. wrote:
Hi Phil, The way we do this is via the command line option “-share-link” to set up a different project for the OPI screens. I’ve pasted our CSS command line below. We have all our common screens in one place called “share”, which is actually located at /home/controls/share/master on the filesystem. In the CSS navigator this appears as simply “share”. So OPI buttons in our beamline specific projects use a relative link to get to the OPI screens located in the share project, e.g the file path would be something like “../../share/opi/blah.opi” There’s a reason we use relative links rather than absolute paths for the file path used by the action button (which I think is related to remote access via a web server), but either should work. Cheers, Matt /home/controls/css/CSS/css -consoleLog -pluginCustomization /home/controls/bl4b/css/combined_settings.ini -workspace_prompt /home/controls/var/workspaces/mkp/bl4b-dassrv1 -share_link /home/controls/share/master=/share,/home/controls/bl4b=/bl4b,/home/controls/var/tmp=/tmp --launcher.appendVmargs -vmargs -Dorg.eclipse.swt.internal.gtk.cairoGraphics=false -Dorg.eclipse.swt.internal.gtk.useCairo=false -Dorg.eclipse.swt.browser.DefaultType=mozilla -Dorg.eclipse.swt.browser.XULRunnerPath=/home/controls/css/xulrunner Data Acquisition and Control Engineer Spallation Neutron Source Oak Ridge National LabOn Jan 29, 2016, at 9:07 AM, Phil Atkin <[email protected]> wrote: Hi Michael, and thanks for your response. >From it I can conclude that no: I'm not missing anything. I'm such a beginner with all this that I don't really feel qualified to request a new feature - but at least now I don't need to spend any more time looking for it. Cheers, Phil On 29/01/2016 13:58, Michael Davidsaver wrote:Hi Phil, IMO this is as good a forum as any. You might also open an issue: https://github.com/ControlSystemStudio/cs-studio/issues That said, others have requested this feature in years past (myself included) and had it denied. I'd be happy to find that it has been added though. Michael On 01/29/2016 06:47 AM, Phil Atkin wrote:Is this the wrong forum for this question? I found a Google Groups forum for CSS BOY, but activity seems low and I haven't had any responses there, either. Phil On 26/01/2016 14:57, Phil Atkin wrote:Hi, I had hoped that BOY would support a global 'search path' facility like medm's "EPICS_DISPLAY_PATH". I thought I had found it with the "OPI Search Path" setting (under Preferences... CSS Applications... Display... BOY). But although I find that menus with 'Open OPI' actions search this path, it seems that Linking Container objects do not. (I see an error message reporting a FileNotFoundException; the missing path is to the container's directory). Am I missing something? (I'm developing controls for an areaDetector driver, and I'm trying to reference standard areaDetector opi screens defined in a central location without copying them). I'm running under Windows 64. Help... About reports 'CS-Studio 4.1.5-SNAPSHOT'. Thanks, Phil -- *Pixel Analytics* is a limited company registered in England. Company number: 7747526; Registered office: 93A New Road, Haslingfield, Cambridge CB23 1LP-- *Pixel Analytics* is a limited company registered in England. Company number: 7747526; Registered office: 93A New Road, Haslingfield, Cambridge CB23 1LP-- <Logo small.png>Pixel Analytics is a limited company registered in England. Company number: 7747526; Registered office: 93A New Road, Haslingfield, Cambridge CB23 1LP --
![]() |