Thanks for your reply.
I don’t see the justification for declining the request to add a row drag over event, the explanation provided does not make any sense to me.
“As per the development team, For our row moving, there is no such customization. After the row is moved, user cannot customize anything. It’s the reason we think an event like RowDragMoveOver should not be added. Otherwise, there will be a lot of similar event like column moving, row/column resizing, cell selecting…”
I’m going to try to parse this explanation and break down how it reads to me.
“As per the development team”
Ok, this part is easy - you’re telling me the development team have communicated with you.
“For our row moving, there is no such customization”
Yes, we know this - that’s what I was asking about.
“After the row is moved, user cannot customize anything”
Yes - again, we know this - that’s what I was asking about.
I don’t know if this is a statement of what is current fact, or what is decreed law by the developers and they are stating that “thou shalt not customise anything once a row has moved”.
What “row is moved” really means here is unclear - if we take the past tense literal interpretation of moved, you refer to once the user has released the mouse button and the RowDragMoveCompleted has already been raised - but I don’t want to customise anything at that point.
“It’s the reason we think an event like RowDragMoveOver should not be added”
I’m sorry, what? What reason? Point to the reason. I missed the reason. No reasons have been presented. Perhaps you refer to the previous sentence “After the row is moved, user cannot customize anything” - which is not a reason, but a statement - but if you were referring to that, then that would be a circular reference.
“Otherwise, there will be a lot of similar event like column moving, row/column resizing, cell selecting…”
I get that for the sake of consistency if you add a RowDragOver event people are going to expect you to also have a corresponding ColumnDragOver event… but is that really such a big deal?
You could always not add a ColumnDragOver event if it’s such an effort and just provide the RowDragOver event and worry about anyone complaining about that inconsistency when that happens.
But, I’m now doing your job for you and negotiating compromises that could be made to minimise the apparent insurmountable suffering that this improvement would impose on the developers.
You can decline the request, I’ve coded around this limitation already - I just don’t accept the reasons provided.