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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: New Display Builder widget question using Navigation Tabs |
From: | "Kasemir, Kay" <[email protected]> |
To: | Amien Crombie <[email protected]>, "[email protected]" <[email protected]> |
Date: | Tue, 22 Aug 2017 13:23:28 +0000 |
Hi:
--- I have a display that host the 'nav tabs'. As you know, the navtabs works (in my case) by having a single bob with 5 groups consisting of widgets etc (you can see the 5 groups on my pic). So my navtabs works well. But I want to have an embedded display on the lower part of my navtab that will become visible when I do certain things from my navtab widgets. I know an embedded display cannot be accessed so I used a 'group' widget that contains the embedded one. So I should be able to access the 'group' widget's visibility setting as it will not change. So in my script, that is attached to each widget on my navtab, I want to be able to 'show' or hide' the 'group' widget that contains the embedded display.. In a perfect world my script should sends the $(pv_name) down to the embedded display. This is where I am lost now.. ---
I'm still not clear what you have, but let's assume it's somewhat like this: Main display has navtabs with 5 tabs, i.e. an embedded display that selects one of 5 sub displays Tab1, Tab2, .., Tab 5. In addition, that main display has another embedded display.
You somehow want to influence that other embedded display from within Tab1, .. Tab5. The scripts for any of these displays (main, Tab1, .. Tab5, the other embedded display) are all sandboxed to within their display, they cannot locate widgets in other displays. What you can use to communicate between these is PVs, either real PVs or local PVs. A script in Tab2 can write to loc://do_something(0) or loc://the_name(""), and a script attached to the other embedded display can react to changes in these local PVs.
I would start to worry, though, that this is morphing from a control system display to a video game. If the content of the tabs is related to what's shown below, why isn't the stuff below simply included in the tab? I.e. make the tabs larger and include the other embedded display inside Tab1, Tab2, .., Tab5.
Thanks, -Kay
|