Bug 246603 - engineNewMetadata in scripting API undocumented
Summary: engineNewMetadata in scripting API undocumented
Status: RESOLVED DUPLICATE of bug 233466
Alias: None
Product: amarok
Classification: Applications
Component: Documentation (show other bugs)
Version: 2.3.1-GIT
Platform: Unlisted Binaries Linux
: NOR wishlist
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on: Script_API
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-03 13:10 UTC by Manuel Amador (Rudd-O)
Modified: 2013-04-09 15:59 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Manuel Amador (Rudd-O) 2010-08-03 13:10:17 UTC
Version:           2.3-GIT
OS:                Linux

The engineNewMetadata in scripting API looks like it could be useful -- as far as I understand, it is a way to signal Amarok that a script changed the metadata of some file, to prompt it to reload the new metadata from the DB in the playlist / collection..

Unfortunately, it is undocumented:

    void AmarokEngineScript::engineNewMetaData( const QHash<qint64, QString> &newData, bool trackChanged )
    {
        emit newMetaData( newData, trackChanged );
    }

What is the qhash?  How does one calculate it and what value ought it have / where does this value ought to come from?  Bool trackchanged?  Is this supposed to be a slot that I can connect events from my script to?

These are important things for us script writers.  And the scripting api says nothing about it.

Reproducible: Always
Comment 1 Myriam Schweingruber 2013-04-09 15:59:35 UTC

*** This bug has been marked as a duplicate of bug 233466 ***