FastTableModel switched from default single-select to multi
Breaking all code that expects selectedItem to be not-nil.
Is that wanted behaviour? I noticed it broke SpecGenerator.
I have no strong opinion on this, and welcome all Spec progress.
Re: FastTableModel switched from default single-select to multi
Is this in the Glamour model or in the Spec one?
If it's the glamour one I made some changes to the Glamour one but I don't remember changing the default to multiple selection. Maybe it's a bug :)
Cheers,
Andrei
On Mon, Feb 13, 2017 at 12:38 AM, Stephan Eggermont <[hidden email]> wrote: > Breaking all code that expects selectedItem to be not-nil. > Is that wanted behaviour? I noticed it broke SpecGenerator. > I have no strong opinion on this, and welcome all Spec progress. > > Stephan > >
Re: FastTableModel switched from default single-select to multi
On 16/02/17 20:37, Martin Dias wrote:
> I set the case to "Milestone Later"... I reproduced the bug in Pharo 5
It is somewhat more complex. I have the problem with doubleClick,
but not if only adding a doubleClick handler. In SpecGenerator
I set some more properties.