My suggestion is to look into the possibility of allowing the user to open two device properties windows at the same time.
Here is why I think that this would be a good idea for helping with tasks such as:
- When working on two similar devices, for example with an Axis Device or an IO Device, it is quite normal to take information from one and copy or paste it into the other.
- We also sometimes have them open side by side to compare and check someone's work.
- Axis Device IO mapping assignments, Bit State ON/OFF Captions and Formatting.
- We would be able to carry out the same work without needing to use the XML, which is the current "shortcut" for this.
This is, of course, is to be used when we are not able to simply use an existing device and create a new instance via the "network device install / install from file" workflow.
In a perfect world, we would create the device once, then clone it. But sometimes things don't work out consequently and we have to work concurrently. Meaning that there is no "Master Config" ready to use.
Other times, we may just need a part of the IO, such as a section of an IO Master to copy into a regular Simulated IO device.
For the uses that I can think of, I would not need to have "write" privileges for both devices. I would be perfectly happy with write access on one device and "read only" on the second.
As the portal will attempt to lock both devices, a window could provide the choice to edit properties on both devices at the same time or select which one to open with write privileges and which one for read only. The behaviour where the rest of the UI is locked out while the properties window is open is still desired. I like that aspect to prevent a user from leaving a properties window open and hidden somewhere.
Screenshot Below with two devices side by side (screenshot generated outside of Nav)
Please sign in to leave a comment.