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: Phoebus and dynamic macros |
From: | GAGET Alexis via Tech-talk <tech-talk at aps.anl.gov> |
To: | "Kasemir, Kay" <kasemirk at ornl.gov>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Wed, 2 Nov 2022 15:16:09 +0000 |
Ok, thanks the example is perfect.
I have looked in the example before but haven't looked in the correct section (i was looking in Macros ...) De : Kasemir, Kay <kasemirk at ornl.gov> >
I was ... using script. As we've promised from the start, details of the script API are subject to change.Transitioning from BOY/Eclipse/SWT
to Display Builder/Plain JRE/JavaFX, i.e. a completely new implementation, does require adjustments to scripts, and script of course won't work at all in the web runtime that uses HTML/CSS/_javascript_. To port your BOY scripts, see
https://github.com/ControlSystemStudio/phoebus/wiki/Display-Builder-Script-Compatibility regarding _javascript_ vs. jython, and for an example of updating macros for an embedded display see display builder examples, embedded displays, specifically
https://github.com/ControlSystemStudio/phoebus/blob/master/app/display/model/src/main/resources/examples/embedded/update_display.py -Kay From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of GAGET Alexis
via Tech-talk <tech-talk at aps.anl.gov> Hello, I’m trying to migrate to Phoebus for our new development and I’d like to be able to set Macro dynamically (for my hundreds of acquisition channel for example). I was
able to do that with CSS boy using script. According to
https://control-system-studio.readthedocs.io/en/latest/app/display/editor/doc/property_type.html?highlight=macros#macros-property it seems possible also. But when I applied the example to an “Embedded Display”: importPackage(Packages.org.csstudio.opibuilder.scriptUtil); var macroInput = DataUtil.createMacrosInput(true); macroInput.put("CHANNEL", PVUtil.getString(pvs[0])); widget.setPropertyValue("macros", macroInput); I got the following exception : [..] Caused by: java.lang.Exception: Need Macros, got {CHANNEL=2} [..]
CHANNEL=2 because my PV loc://macroValue is set to 2. seems to come from here but it's not really understandable for me Is the example incorrect, or is it not usable on an "Embedded Display" I've tried on a simple windows, i got the same result Thanks in advance CEA Saclay - DRF/Irfu/DIS/LDISC Bâtiment 472 - pièce 105 |