Bug 233466 - Amarok.Engine.newMetaData is not documented
Summary: Amarok.Engine.newMetaData is not documented
Status: RESOLVED DUPLICATE of bug 313283
Alias: None
Product: amarok
Classification: Applications
Component: Tools/Script Manager (show other bugs)
Version: 2.3.1-GIT
Platform: Ubuntu Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
: 245837 246603 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-04-06 11:22 UTC by Dennis Schridde
Modified: 2013-04-24 15:39 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Schridde 2010-04-06 11:22:03 UTC 
Version:           2.3.0 (using KDE 4.4.2)
Installed from:    Ubuntu Packages

Amarok.Engine.newMetaData is not documented on http://amarok.kde.org/wiki/Development/Script_API#Amarok.Engine
Since it takes two parameters, of which the purpose of one is not obvious, also the parameters should be documented in addition to the signal being listed.

Further it is not clear to me why "QHash<qint64,QString> &newData" is even necessary. Is there data that cannot be determined from Amarok.Engine.currentTrack?
Comment 1 Dennis Schridde 2010-08-17 11:44:07 UTC 
Any progress with this?
Comment 2 Myriam Schweingruber 2010-08-17 17:28:04 UTC 
Not yet done, I think the developers simply didn't find time to do so. You can also ask in #amarok on irc.freenode.net or on the forum at http://forum.kde.org/amarok if you need these informations ASAP. Feel free to add more information to the wiki if needed.
Comment 3 Myriam Schweingruber 2013-04-09 15:59:17 UTC 
*** Bug 245837 has been marked as a duplicate of this bug. ***
Comment 4 Myriam Schweingruber 2013-04-09 15:59:35 UTC 
*** Bug 246603 has been marked as a duplicate of this bug. ***
Comment 5 Anmol Ahuja 2013-04-24 15:10:32 UTC 
Mark duplicate of 313283.
Comment 6 Dennis Schridde 2013-04-24 15:39:37 UTC 

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