Open claudio-rosati opened 5 years ago
Maybe you're using the PVManager-probe. Display builder uses vtype.pv. They each have their own local PVs.
Use EPICS PV Tree, PV Table, or actually anything but PVManager-probe. Or use phoebus.
Phoebus will be the final solution, but for now people just send PVs to the Probe, and they don't know the probe is PVManager or not, they just expect to see it working. Moreover it seems to me contrary to the philosophy of the context menu, where when a menu item is present is because it should work on the selected widget (or, in general, PV provider). Anyway, next week I'll start working on the Display Builder Phoebus plugin, hoping to move very soon away from the eclipse-based CS-Studio.
It's up to you if you want to include org.csstudio.diag.probe or org.csstudio.diag.pvmanager.probe. Pick the one that works, or the one that doesn't.
Is org.csstudio.diag.probe the one working with Display Builder?
Yes. It's using the vtype_pv just like pretty much everything but BOY.
The issue are related to the cursor. Run the Image Widget example, click inside the bottom image: the position is updated in the two Text Entry widgets on the OPI's bottom right.
Now right-click on one of those Text Entry widgets, and send the PV to the Probe: nothing is displayed in the probe, even if the cursor is mode inside the image. Why?