Smalltalk › Pharo › Pharo Smalltalk Developers

FTDataSource API

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Uko2

FTDataSource API

Hi,

I’m a bit confused because FTDataSource has two methods #cellColumn:row: and #elementAt: with subclassResponsibility. I understand when FTSimpleDataSource implements #elementAt: and uses it in #cellColumn:row:. But as #cellColumn:row: is more general, why is there #elementAt: defined in FTDataSource?

Uko

EstebanLM

Re: FTDataSource API

mmm… that’s an error :)
I’m using (wrongly) #elementAt: to pick up drag&drop passengers in FTTableMorph>>#startDrag:, and that is a mistake (it should call some #passegerAt: method).

can you fill a bug report, please?

Esteban

> On 09 Sep 2015, at 17:03, Yuriy Tymchuk <[hidden email]> wrote:
>
> Hi,
>
> I’m a bit confused because FTDataSource has two methods #cellColumn:row: and #elementAt: with subclassResponsibility. I understand when FTSimpleDataSource implements #elementAt: and uses it in #cellColumn:row:. But as #cellColumn:row: is more general, why is there #elementAt: defined in FTDataSource?
>
> Uko

Uko2

Re: FTDataSource API

Done https://pharo.fogbugz.com/f/cases/16537/FTDataSource-elementAt-should-not-be-there

> On 09 Sep 2015, at 17:48, Esteban Lorenzano <[hidden email]> wrote:
>
> mmm… that’s an error :)
> I’m using (wrongly) #elementAt: to pick up drag&drop passengers in FTTableMorph>>#startDrag:, and that is a mistake (it should call some #passegerAt: method).
>
> can you fill a bug report, please?
>
> Esteban
>
>
>
>> On 09 Sep 2015, at 17:03, Yuriy Tymchuk <[hidden email]> wrote:
>>
>> Hi,
>>
>> I’m a bit confused because FTDataSource has two methods #cellColumn:row: and #elementAt: with subclassResponsibility. I understand when FTSimpleDataSource implements #elementAt: and uses it in #cellColumn:row:. But as #cellColumn:row: is more general, why is there #elementAt: defined in FTDataSource?
>>
>> Uko
>
>