We can send prev, current and next Caspa playlist ids too somewhere...

Enviado desde mi BlackBerry

-----Original Message-----
From: Tomas Neme <notifications@github.com>
Date: Sat, 13 Apr 2013 16:28:56 
To: inaes-tic/mbc-mosto<mbc-mosto@noreply.github.com>
Reply-To: inaes-tic/mbc-mosto <reply@reply.github.com>
Cc: Juan Martin Runge<jmrunge@gmail.com>
Subject: Re: [mbc-mosto] NOT FOR MERGE please review (#54)

> +            if( i < meltedStatus.current ) {
> +                if( clips[i].playlist_id != status.show.current ) {
> +                    status.show.previous = { _id: clips[i].playlist_id };
> +                }
> +            } else if ( i > meltedStatus.current ) {
> +                if( clips[i].playlist_id != status.show.current ) {
> +                    // I'm pass `previous` and the first into `next`, so I'm
> +                    // done here
> +                    status.show.next = { _id: clips[i].playlist_id };
> +                    break;
> +                }
> +            }
> +        }
> +
> +        this.status = _.extend(this.status, status);
> +        // except next. If that's undefined, I just don't know!

can someone think of a workaround for this? if the current playlist goes all the way to the end of the clips list, I have no way of knowing what's the next show going to be!

---
Reply to this email directly or view it on GitHub:
https://github.com/inaes-tic/mbc-mosto/pull/54/files#r3784755