Fix memory leak for font assets

Each call to Typeface.createFromAsset will load a new instance of the typeface into memory,
and this memory is not consistently get garbage collected
    http://code.google.com/p/android/issues/detail?id=9904
(It states released but even on Lollipop you can see the typefaces accumulate even after
multiple GC passes)

You can detect this by running:
adb shell dumpsys meminfo com.your.packagenage

You will see output like:

 Asset Allocations
    zip:/data/app/com.your.packagenage-1.apk:/assets/Roboto-Medium.ttf: 125K
    zip:/data/app/com.your.packagenage-1.apk:/assets/Roboto-Medium.ttf: 125K
    zip:/data/app/com.your.packagenage-1.apk:/assets/Roboto-Medium.ttf: 125K
    zip:/data/app/com.your.packagenage-1.apk:/assets/Roboto-Regular.ttf: 123K
    zip:/data/app/com.your.packagenage-1.apk:/assets/Roboto-Medium.ttf: 125K

The workaround is to keep a reference to the loaded typeface and reuse it
Merge pull request #101 from teslacoil/typefacehelper

Fix memory leak for font assets
Release 0.4.4. See README for changelog.
Merge remote-tracking branch 'origin/master'
Cleanup changelogs for release 0.4.4
Fixed crash when itemsCallbackMultiChoice() was called with no selectedIndices (null as per the javadoc)

Also fixed a typo and updated buildToolsVersion
Added missing functions in MaterialDialogCompat.Builder
Merge pull request #108 from jrgonzalezg/master

Fixed crash when itemsCallbackMultiChoice() was called with no selectedIndices...
Merge pull request #112 from AEFeinstein/master

Added missing functions in MaterialDialogCompat.Builder
Add Builder.customViewRaw and cleanup padding

customViewRaw allows bypassing the default scrollview and padding applied to
custom views, for example if the custom view has it's own scrollable content.

This also makes minor changes to how padding is distributed, but changes to the
implementation are major.

The title bar is now always fixed (previously it scrolled for custom content)
The padding between the title bar and content is now split evenly between
the title bar topMargin and the content paddingTop, if the content is scrollable
the divider is placed half way between.

Likewise the button bar padding is split between the button bar and content.