I often use button rows to change another column in the same row (eg, check a box, change a date), which then filters out that row of the table (eg, mark as done, mark a row as “reviewed,” snooze an item). However, once I click the button, the row stays there until I click outside the row. I understand why this is (for text fields, it would be awful if the row went away while you were still editing it), but for button columns this is a major inconvenience.
I suggest an option in each button column’s settings to deselect the row when the button is pushed.
1 Like
I agree with David, for users who have no idea (or care) about how coda works it is confusing that the row remains when it should be filtered out.
Maybe it could be implemented as an action to unselect the current row?
1 Like
In case this is helpful for anyone, I’ve figured out that if you get the ObjectLink() of another row and open it, it will select that row without going into detail view, which simulates ‘clicking outside the row’ by removing the focus and allowing it to be filtered out or sorted.
RunActions(
WhateverAction(),
Table.filter(WhateverCriteria).first().ObjectLink().OpenWindow()
)
If the result of the filter is not the row from where the button was clicked, it will remove focus of the current row.
Hope this helps,
Pablo