[REVIEW REQUEST] RT-33442: isSelected in TableViewSelectionModel is called too many times

[Jonathan Giles]

I do make use of a similar concept within the selection models
themselves (makeAtomic) to coalesce events, but my experience is is that
if this is toggled incorrectly or out of order, all sorts of things can
go awry. I did think about making something like this public, but I fear
that I'd just be signing up for years worth of bug reports.

My gut feeling is that perhaps we put the fix for RT-33442 on the
backburner until an 8.x.y release and consider alternatives (such as
this) as well. As always, I'll wait to see what the community has to say.

-- Jonathan

On 22/10/2013 3:29 a.m., Jeff Martin wrote:
> I'm late to this discussion, and I don't see anything wrong with the selectRange() API, but perhaps another option worth considering would be to add a DisableSelectionEvents or CoalesceSelectionEvents attribute.
>
> The only advantage to that I can think of is that it could allow bulk selection of non-contiguous cells which might otherwise also exhibit the slowdown.
>
> jeff
>
>
>