Closed marcpley closed 2 days ago
I keep thinking about this enhancement...
"Keep focused cell on Refresh" don't need to be an option in config dialog (complexification of config). I think it can be the regular behavior.
"Automatic Refresh table data on Commit" would not be an option in config dialog because the user may want the automatic refresh or not, depending of the modifications he performs. There is 2 possibilities:
So I simplify my initial request: Just try to keep the focused cell on Refresh, all the time (but if it a config option I don't mind). And eventually change the order of the button, from general to detail: refresh commit rollback addrow deleterow to have the commit and refresh buttons side by side. More logical order in my opinion.
Seems good.
I just have few notes to be aware of:
In such cases the re-focusing would not work.
It is acceptable that the refocus don't work all the time. In most cases the user will understand why the row disappears. This enhancement could start basic and be more performant in the future.
@marcpley please fetch update from git and see how it works for you regarding cell focus.
It's working for me too. Great :-) Triggers list is ok too.
Details
When inserting or update rows in grid view, triggers firing on commit could generate values for generated columns. But those generated values are not visibles as the user continue to imput data.
User need to click Commit button AND Refresh button AND refocus on the row he work on.
Those options would be great: