Frank La Vigne

Fear and Loathing in .NET

MVP Logo
Tablet PC MVP

Social Networks

Subscription Options

Add to Google

Subscribe in Bloglines

My Links


Post Categories

Archives

Image Galleries

Cached @ 9/3/2010 2:52:25 AMControl ASP.skins_marvin3_controls_archivelinks_ascx

GamerTag

Dev Community Events

Blog Stats

Cached @ 9/3/2010 2:52:25 AMControl ASP.skins_marvin3_controls_blogstats_ascx  

News


Blog Roll

Favorite Sites

Gadget Blogs

Tablet PC Links

Cached @ 9/3/2010 2:52:25 AMControl ASP.skins_marvin3_controls_categorydisplay_ascx

Pushing Blend to Its Limits

I'm currently in the middle of creating an interactive map of the world in XAML and quickly learning the limits of Blend.

I've also learned a lot about geography.

Did you know that there are *a lot* of islands in the world.

Including Blend's annoying habit of drawing a blue bounding box around an object.

Mapping

When you're trying to group all the paths into a canvas of Indonesia, with its 17,000+ islands, the screen gets a bit cluttered with blue lines.

Thankfully, my source map didn't express all of Indonesia's islands, but it does have roughly 1200 paths.

This is case where I wish I could turn of the lines but keep the selection indicators. (View -> Show Handles is an all or nothing proposition.)

Eventually, I've had to split the world out into regions, as Blend would periodically freeze as it parsed and rendered the 20mb XAML file.

With everything broken out into continents, the largest XAML file is around 3mb and performance has gotten a lot better.

I sure wish there was some kind of integration with MapPoint and WPF.  I mean MapPoint uses vector data.

There's got to be a way to do the conversion to XAML.

 

posted on Thursday, April 03, 2008 3:21 PM

============ Debug Build ============
Dottext Version: 0.95.2004.102
Machine Name: IIS07902
.NET Version: 2.0.50727.3053
No User
============ Debug Build ============