Repository navigation
Conversation
|
@LordIdra, not sure about the copy scenario... Currently PVs can only occur once per alarm configuration. Or is it about copying between different configurations? |
Yeah that's just a silly oversight on my part, I did not realise that you could only have one instance of a PV per config as I never tried to add a duplicate one. I will just prompt the user for a rename each time and check the whole tree for an existing duplicate PV. Right now you cannot copy/paste between configs but this is definitely a good use case. So I think I'm going to change the implementation to actually use the system clipboard to facilitate this. |
… cut/paste into child
538134d to
fbf8834
Compare
So this is rather more complicated than I thought at first... There is no inbuilt serialization for alarm nodes (and don't want to add it just for this...) so just made the clipboard static to persist it across trees. Not ideal, but I think it should not pose a problem in practice. The problem now is that cut doesn't really work across multiple configs because it requires action across multiple configs which may not be loaded... e.g. if I cut a node in Config A and then navigate to Config B and paste it, Config A is no longer loaded so I cannot delete the item from there. I have solved this by just popping up an error box when the user tried to cut/paste across multiple configs. I also found and fixed some more issues. Unfortunately it has turned into a bit of a special case hell when pasting. Here is the latest demo: 2026-11-19.10-39-06.1.mp4Should all be ready now. |
|



Part of #3995
Headline change: adds 3 new context menu buttons

2026-11-17.16-42-30.mp4
Implementation details
Other changes
(Sorry for the inflated diff because of refactors - figured if I was touching these classes anyway I may as well do some small cleanups)
Checklist
Testing:
Documentation: