Feature request -- Memory View

[Controls Guy]

Most brands allow me in a memory table to write while polling.  In fact, I'm not aware of any that even have a snapshot mode.  I take it that the assumption is that if you want a data view, you want it to be live.  Always good to have options, so there is probably a case where snapshot mode is superior.  Even so, I'd like it to be live and writable at the same time, and polling by default.  Thanks!

[BobO]

Yeah, that's limiting. We can do better.

[Controls Guy]

Even so, kudos for adding it in the first place!  I use it all the time as it is.

[franji1]

It is that way by design.  Most UIs do NOT mix editing and reporting from the same field.  Especially for reporting data that is polled live.

[BobO]

I'm with Steve on this. I think it is limiting. There are reasonable answers...like suspending updates when you start an edit.

[Controls Guy]

It is that way by design.  Most UIs do NOT mix editing and reporting from the same field.  Especially for reporting data that is polled live.

PLC programming UI's?  That hasn't been my experience.  AB's all do, and I haven't managed to shoot my eye out yet.

[Controls Guy]

I'm with Steve on this. I think it is limiting. There are reasonable answers...like suspending updates when you start an edit.

That should be manageable, particularly if the suspension is only on the edited register, but even if not.  Also, I'd like when entering edit mode by double clicking to highlight the current value by default, so as to replace it with whatever I type, rather than no selection and add scroll buttons.  Personally I'd ditch the scroll buttons anyway.

[ATU]

I'm with Darth on this one.

[Controls Guy]

I think it is limiting.

It really is.  My typical write goes something like the following:  "OK, let's write this register.  Double click.  Why is it not highlighting?  Oh yeah, I'm in read-only.  Click on Toggle Read-Only.  Double-click on register.  Opens for editing but not highlighted/selected.  Double click again to highlight.  Enter new value, and <enter>.  Is it written?  Doesn't seem to be working.  Oh yeah, write isn't committed yet.  Not in auto-write mode because we just got out of read-only and it was cleared.  Choose one of the five write modes, and click.....AND there's a confirmation that you didn't just spend the last 15 seconds and 23 clicks trying to edit the register unintentionally."  And then, assuming I remember to, I have to re-enable polling, but that's still two steps because I have to enter read-only and re-enable polling in two separate steps.

So a big part of this is me and that all the steps are not yet burned in to an automatic level for me, but I think even objectively, it's way too many clicks, way too many modes, and way too much caution, none of which be turned off by default.  The competitive version is Click-type-enter, and it works like a charm.  User-selectable confirm-to-write and read-only modes would be nice for certain applications, so long as you can leave them off by default, and not just for the current session.

Update:  Did come up with one workaround -- open two identical MV's and configure one for polling and one for writing.