DataPtr vs. TrackPtr in the collection browser

[Alexandre Oliveira]

Because for the collection model it doesn't matter what the data is.
As long as it knows how to extract information from it, no problem.
And DataPtrs are enough for that, at least for now, and makes things
much easier, as I don't need to handle them differently.

On 5/17/07, Ian Monroe <ian at monroe.nu> wrote:
> Why does the Collection Browser work with DataPtrs as opposed to
> TrackPtrs. One would assume it needs TrackPtrs anyways.
>
> When you start talking about casting QList< KSharedPtr< Meta::MetaBase
> > > to QList< KSharedPtr< Meta::Track> > things start getting
> complicated. :) I don't know how to cast it at least.
>
> The playlist is written in terms of TrackPtrs currently.
>
> Thanks,
> Ian
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>