Experimental Physics and
| |||||||||||||||||
|
Hi Jamie,
On Thu, Mar 19, 2015 at 10:04 PM, Jameson Graef Rollins <[email protected]> wrote: On Thu, Mar 19 2015, Matt Newville <[email protected]> wrote: I think it kind of depends what you're trying to do. FWIW, I have lots of GUIs that display Epics variables and get control values in a "lazy manner". Generally, one can create a PV, then ask some function to be run when the GUI is not busy where you wait-for-connection, get the control variables, and add callbacks (in the case where the widgets don't even exist when the PV is created-without-connection). Another approach would be to use a Timer loop look for newly connected PVs (those for which pv.connected was False and is now True) and finish setting up the pvs as they connect (including getting ctrl vars). Is there really no other option? There are always options! I still don't understand why the That would be possible. It's not clear to me that every PV always needs CTRL variables to be fetched as part of the automatic connection process -- I might be persuaded to add this as an option,, but am not certain it's necessarily always a good idea. It might slow down the connection (I have not profiled it carefully), but it's probably acceptable in many situations. --Matt Newville
| ||||||||||||||||
ANJ, 16 Dec 2015 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |