[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-multimedia
Subject:    Re: noatun api question
From:       Charles Samuels <charles () kde ! org>
Date:       2001-06-29 16:55:41
[Download RAW message or body]

On Friday 29 June 2001 04:40 am, Benedikt Elser wrote:

> Hi,
>
> i've noticed, that there have been many bug reports/technical
> discussions on this list, but no more simple questions. So here is one:
>
> How did you get the playlists in the CVS tree, to move to the current
> track when the song changes? Looking at the source didn't help me very
> much, due to the fact, that C++ isn't quite my native lang <purpose of
> this is to learn it>. After spending lots of time wondering what kdoc is
> doing, while using 97% CPU for quite some time without generating ANY
> documentation, I decided to ask the techs. Purpose of all this is to get
> a plugin -  for xosd (http://www.ignavus.net/software.html)
> visualization - working WITHOUT pressing a button (which isn't quite
> what I want).
>
> So if any of you has hints like "kdoc works better when you don't start
> it in an infinite loop" or "use this header file to catch this signal"
> I'd be quite thankful.

The Playlist API and the API for every other plugin is a bit separated, what 
you want is to connect the signal from the Player class.

connect(napp->player(), SIGNAL(newSong()), .... );

Then, I'm assuming you want information on a song, napp->player()->current() 
will return either 0, or the currently playing song.  (PlaylistItem is the 
type, however, we changed it from PlayListItem in KDE 2.1 to PlaylistItem in 
the unreleased 2.2, because we think Playlist is one word, just be warned).  
That playlistitem has all the functions necessary to create an 
on-screend-display.

May the force be with you :)

-Charles
_______________________________________________
Kde-multimedia mailing list
Kde-multimedia@master.kde.org
http://master.kde.org/mailman/listinfo/kde-multimedia

[prev in list] [next in list] [prev in thread] [next in thread]