UI

A good read about memory leaks in WPF and Silverlight. Most of the UI memory leaks are evolved around events registration with no unregistrating them which causes the GC not to collect objects.

 

Here are the main causes:

 

  1. Event handlers to objects in parent windows
  2. Registering to events from static objects
  3. Using timers
  4. Data binding
  5. Changing the Text property of a text box (unlimited undo operations)

 

If you ever used a composite approach (like Prism) and EventsAggregators you may have come to appreciate the weak event pattern and the weak reference.

 

menny 10/02/2012 - 23:57

 A blog post on the role of pixel density when developing mobile apps.

 

Whereas in the past user interface design would largely be concerned with screen size or display resolution only, now the question of how many pixels make up one inch becomes relevant as well. This measure is called pixel density, and expressed in dpi or ppi values. Nowhere is pixel density as broadly distributed as in the mobile world. A low-end android mobile may have a 180 dpi screen, while a high-end one, like the retina display, will boast up to a 326 dpi screen.

 

Read more: danielsz.posterous.com/pixel-density-in-a-troubled-world

danielsz 05/01/2011 - 13:42
Syndicate content