[FEATURE] Keep tag editor dataset value editor open on loss of focus

Ignition
1

I'm sure I've already raised this before but I can't find it..

8.1.30

The number of times I accidentally close and wipe all of my changes while editing a dataset tag's value is embarrassing, but at the moment all it takes is to remove focus from the dataset editor and all your changes are gone. This is so easy to do, for example an email comes in and you want to read it, a chat message comes in, you quickly swap to Excel to copy something to paste into the dataset cells and poof! all your changes have disintegratored (mispelling and hence pun intended).

Can this please be made to not close on loss of focus?

image
image827×491 12.8 KB

Edit:
More locations in the tag editor affected by this:

  • Query tag's "Query" value editor
  • OPC tag's "OPC Item Path" browser
1 Like
2

Same with the built in OPC browser as well please.

1 Like
3

I've added that into my OP to keep them in one post

1 Like
4

What's ideal UX here?

  • Commit changes on focus loss?
  • Prompt to commit changes before losing focus?
    • Only if changes have been detected?
  • A more 'permanent' frame that doesn't close on focus loss. If so... what if you close the overall tag editor? What happens to the frame then?
5

I think... That's a good question.
I think the permanent frame is best. If you close the tag editor without apply or ok, then it should discard like any other changes would be. I think it should apply if you have it open and press apply or ok on the tag editor though

6

Personally, I've always been a fan of this. Tell the user, hey you're about to lose the changes you made, and then let them decide if they should be committed or not. If the no changes have been detected then close away.

1 Like
7

Loss of focus shouldn't be closing anything with a close/apply/cancel button.

2 Likes
8

I think a permanent frame (that closes w/o committing, perhaps after confirmation box, if the parent closes).

I regularly have multiple windows or panels open - some for context, some for reference, and maybe more than one for editing. If I have to close my edit window to see the context then I end up using screenshots and notepad++ and Post-It notes to keep the right info in view while entering the code. It is a lot easier if I can drag the edit dialog out of the way instead. (Also, I should be able to move the edit window...)

And for Loss of Focus? So an unrelated system notification that I can't predict closes the window and loses my work? Or I need to stop the music, mute the mic, or reply to a chat? Yeah, ... that seems harsh.

2 Likes