| Summary: | engineNewMetadata in scripting API undocumented | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Manuel Amador (Rudd-O) <rudd-o> |
| Component: | Documentation | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version: | 2.3.1-GIT | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Bug Depends on: | 313283 | ||
| Bug Blocks: | |||
*** This bug has been marked as a duplicate of bug 233466 *** |
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