I'm showing a simple table that includes a unique numeric sort column.
I want to allow the user to select a row (unfortunately I cannot only show a selected cell, but that is only a cosmetic quibble) and then specify that the row be moved up or down in the sequence.
I do this by changing the value in the sort cell, using an intermediary "+0.5" value to maintain the uniqueness. While doing this the Sort naturally changes the row number of the tweaked row. I can cope with this, with a bit of brain pummelling, plus a global that stops the invocations of my _SelectionChanged(ColumnName, RowIndex) Sub having any effect when the change in selection is due to this sorting and not user action.
But the selected cell is not showing up as I expect. What are the rules for which cell is considered to be selected when actions such as filtering or sorting, or for that matter adding a new row, take place? And can a cell be considered to be selected while not being shown as such (by inverse font)?
I want to allow the user to select a row (unfortunately I cannot only show a selected cell, but that is only a cosmetic quibble) and then specify that the row be moved up or down in the sequence.
I do this by changing the value in the sort cell, using an intermediary "+0.5" value to maintain the uniqueness. While doing this the Sort naturally changes the row number of the tweaked row. I can cope with this, with a bit of brain pummelling, plus a global that stops the invocations of my _SelectionChanged(ColumnName, RowIndex) Sub having any effect when the change in selection is due to this sorting and not user action.
But the selected cell is not showing up as I expect. What are the rules for which cell is considered to be selected when actions such as filtering or sorting, or for that matter adding a new row, take place? And can a cell be considered to be selected while not being shown as such (by inverse font)?