2) Know your iconography.
3) Support Information – Test Case 5.6.
4) Toast Notification – Test Case 6.2
5) Applications Running Under a Locked Screen – Test Case 6.3
6) Back Button – Test Case 5.2.4
7) Themes – Test Case 5.1.1
8) Languages.
9) Failures upon Upload to the Marketplace
10) Windows Phone Developer Tools.
I've spent a large chunk of the last weekend playing with the Silverlight PivotViewer from Microsoft.
Overall the PAuthor project for creating PivotViewer for Silveright datasets works great - I've used in in .Net4 for 4 separate command line apps :)
However, when working on some large data sets (around 75000 Items) I found the following problems - mostly to do with corrupt items in my input.
Hope this post helps other people...
Problems seen in collectionCreator.Create(m_dziPaths, m_dzcPath); in ParallelDeepZoomCreator.cs
To fix these I just wrapped the call with:
List<String> toRemove = new List<string>(); foreach (var c in m_dziPaths) { try { System.Security.Permissions.FileIOPermission f = new System.Security.Permissions.FileIOPermission( System.Security.Permissions.FileIOPermissionAccess.AllAccess, c); } catch (ArgumentException exc) { toRemove.Add(c); System.Diagnostics.Trace.WriteLine("INVALID PATH " + c); } } foreach (var c in toRemove) { m_dziPaths.Remove(c); } while (true) { try { DZ.CollectionCreator collectionCreator = new DZ.CollectionCreator(); collectionCreator.Create(m_dziPaths, m_dzcPath); break; } catch (System.IO.FileNotFoundException exc) { System.Diagnostics.Trace.WriteLine("STUART - SORRY - REMOVING " + exc.FileName); m_dziPaths.Remove(exc.FileName); } }
Some multithreaded problem seen in image download
The finalizer for PivotImage.cs occasionally sees IO exceptions in the File.Delete operation - the exception claims that the fie is currently open in another process.
Not sure what is causing this - my guess is it's a multithreading issue of some description.
To fix (mask) this I simple added a try catch to the finalizer:
~PivotImage() { if (m_shouldDelete == false) return; if (File.Exists(m_sourcePath) == false) return; try { File.Delete(m_sourcePath); } catch (IOException) { System.Diagnostics.Trace.WriteLine("Some clean up needed " + m_sourcePath); } } That's it - hope it helps someone.
Make sure you've set the mimetype for .cxml, .dzi, .dzc all as
text/xml within IIS for your current website.
Worked for me :)
Helpful suggestion found on :
http://forums.silverlight.net/forums/p/194861/452655.aspx
public class JsonEnumConverter<T> : JsonConverter
{
public override bool CanConvert(Type objectType)
{
return objectType == typeof(T);
}
public override void WriteJson(JsonWriter writer, object
value, JsonSerializer serializer)
{
writer.WriteValue(((T)value).ToString());
}
public override object ReadJson(JsonReader reader, Type
objectType, object existingValue, JsonSerializer serializer)
{
return Enum.Parse(typeof(T), reader.Value.ToString());
}
}
This allowed me to serialize/deserialize using attributes like:
[JsonObject]
public class MyClass
{
[JsonConverter(typeof(SerializationUtils.JsonEnumConverter<DateTimeTestFormat>))]
public DateTimeTestFormat DateTimeTestFormat { get; set; }
}
However, eventually I worked out that I could just use a more general
solution - and that I could pass that in to the top-level JsonConvert
methods:
public class GeneralJsonEnumConverter : JsonConverter
{
public override bool CanConvert(Type objectType)
{
return objectType.IsEnum;
}
public override void WriteJson(JsonWriter writer, object
value, JsonSerializer serializer)
{
writer.WriteValue(value.ToString());
}
public override object ReadJson(JsonReader reader, Type
objectType, object existingValue, JsonSerializer serializer)
{
return Enum.Parse(objectType, reader.Value.ToString());
}
}
Much easier... :)
>> What's the impact on the battery when doing frequent GPS resolutions?
The answer is battery life varies dependent on phone...
On an iPhone you have to really mess about to improve battery life -
the only way of doing it on older phones is to start playing out audio
(e.g. a playlist) - then you can turn the screen off but still keep
your app alive and capturing GPS.
On my WM6.5 Omnia II, it's easy to keep the app/GPS alive but to save
some power. If I do that and still monitor the GPS, then up to 6 hours
battery life is OK - so pretty good.
On a Bada Wave, there's a SYSTEM_SERVICE level call to make so that
the app can carries on even when the screen is off - locked I can
manage 3-4 hours easy - not tried any longer yet - but suspect 6 is
about the current limit.
On my Nokia 5800, it seems that the Nokia ST app managed 2-3 hours OK
- not tried it any longer.
On Android, it's too early for me to say - but I know that the Google
MyTracks app can manage long sessions - 6 hours+ - although they do
have some sample-rate dropping code to do that - basically it depends
what your activity is:
- if you're walking, then you can probably get away with sampling only
every few minutes
- but if you ever want to do turn-by-turn directions in a car, then
you'll need to up the sampling rate to something much more frequent.