I am pretty sure I know the response to this but I am stuck having to ask this anyhow.
I have a Dynamic List that is data bound to a DGV, I know the standard behaviour is to commit when you come off of the row and this works perfectly when the object is valid.
I am having an issue when I go to come off of the DGV and the object is not valid(it will throw a commit issue), I was originally handling this in "RowValidating" saying when the object is not valid don't move off the row. and this works brilliantly with the left click!
The DGV I am using is our own custom DGV which when you right click a cell the cell will become selected and will also become the current cell. This is what is causing the error I believe.
I have been asked if I am handling the commit error correctly or if the row should just show in error until it has been filled out and then commit?
Any help would be appreciated
Normally Windows users don't expect to be trapped in a control (a textbox, grid cell, etc.), and that can cause issues depending on how it is implemented (such as trapping the user in the app as well as in a control).
So yes, normally people would expect to leave the row and have the row show error status information.
Does this mean that the dynamic list is inadvisable for normal window users?
Is trapping them in the control the correct way to use the dynamic list?
Copyright (c) Marimer LLC