GetUserTopArtists & GetUserPlayHistory API calls return no result (Featured Dibo post)

The Featured Discussion Board Post this week is GetUserTopArtists & GetUserPlayHistory API calls return no result started by Loghorn

Loghorn is developing a Nokia MixRadio Windows Phone based application. He is trying to collect user data using GetUserTopArtists and GetUserPlayHistory, but these API calls do not return the expected results.

Mattcooper acknowledges that the current live version of MixRadio version 4.2 contains a defect that prevents user activity from being returned by these methods. He adds that it has been fixed and will be included in the next live release of MixRadio version 4.3.

Andrewlong.com meanwhile tells how he works-around this problem: if GetUserTopArtists does not return any data, he uses data from GetTopArtistsAsync so he can show the user some artists, even if he does not have their artist. Loghorn confirms that he did the same and also looked at the artist of the local music library as an alternative.

We decided to feature this article because it highlights the bug and its impending fix in the Nokia MixRadio Windows Phone API.

Keep those interesting questions coming!

See About Featured Discussion Board Posts for more information.

Advertisements

BitmapImage Memory Footprint

The Featured Discussion Board Post this week is BitmapImage Memory Footprint, started by Lee McPherson.

Lee is trying to reduce the memory that a 3000×4000 jpeg image would take when shown in full screen on Windows Phone, and was trying to determine if it is better to create a separate smaller thumbnail file and load it, or just load the original jpeg using DecodePixelWidth.

The discussion surfaced several ideas for handling large image files: João Cardoso recommended using the Nokia Imaging SDK, Vinay Patil suggested an example from MSDN on Limiting image size and Loukt highlighted the wiki article Memory-efficient Navigation in very High Resolution Images on Windows Phone.

Lee’s current implementation uses Scrollviewer and ViewportControl. After trying some of the suggestions, Lee accepted that the Nokia Imaging SDK might have been the best solution, and will consider it for the next iteration.

The discussion was selected for featuring because it highlights some of the possible problems and solutions for working with large image files.

See About Featured Discussion Board Posts for more information, and keep those interesting questions coming – that’s what a community is all about!