You may want to have a look at the source of the mmexplore sample util if have not yet.

----- Original Message -----
From: Sebastian Kiesel <community-noreply@qnx.com>
To: development-multimedia <post49571@community.qnx.com>
Sent: Tue Mar 16 05:16:40 2010
Subject: [MME] Correct usage of mme_explore_playlist_find_file()

Hi all,

the documentation in the header file is different from that in the pdf.

API-Call from the Header file:
const mme_explore_info_t *mme_explore_playlist_find_file(mme_hdl_t *hdl, uint64_t msid, const char *entry,  const char *
path,  const char *metadata_types,  uint32_t flags);

Docu - Header file
hdl:= Handle to the MME
...
Docu - PDF
hdl:= A handle to the MME returned by mme_explore_start() 
...
=> mme_explore_start returns a pointer to a mme_explore_hdl_t

More over in the PDF it is indicated that the result of mme_explore_playlist_find_file() - which is a mme_explore_info_t
 - has to be released using mme_explore_info_free(). 
=> mme_explore_info_free() is also documented in in different ways:

API-Call from the Header file:
int mme_explore_info_free(mme_hdl_t *hdl, const mme_explore_info_t *info);

Docu - Header file
hdl:=  Handle to the MME
...
Docu - PDF
hdl:= A handle to the MME returned by mme_explore_start() 
...
=> mme_explore_start returns a pointer to a mmm_explore_hdl_t

Is it only a copy and paste typo within the PDF documentation - what I guess?
Do I need a pointer to a mme_explore_hdl_t at all while using mme_explore_playlist_find_file()?

Thanks a lot,
Sebastian



_______________________________________________

Development
http://community.qnx.com/sf/go/post49571

> Is it only a copy and paste typo within the PDF documentation - what I guess?
> Do I need a pointer to a mme_explore_hdl_t at all while using 
> mme_explore_playlist_find_file()?

I've created an internal PR:75404 to update the documentation. The header files are correct, for that API you need to 
pass in the mme_hdl_t.


Regards,
Gilles