If the BaseTexture dimensions don't match the texture frame then we need a new texture anyway because it's part of a texture atlas

Fixed var declaration

InteractiveManager tweaks

Merge branch 'dev' of https://github.com/GoodBoyDigital/pixi.js into dev

Removed TODO comment

little MovieClip optimization

Optimized getBounds for Sprite

Merge pull request #1179 from pnstickne/wip-pixi-docs ...

Documentation - type cleanup and fixes

Merge pull request #1173 from kambing86/dev ...

solve issue #1172, fix updateCache not clearing the cached texture

Documentation - type cleanup ...

- {Number ..} was incorrectly used as a type in a few placed; updated to
  {Number}.

- Removed {} braces incorrectly used with @type; it doesn't affect the
  document rendering, but it does affect the YUIDoc metadata..

- Fixed space in "Rounded Rectangle" type

- Fixed over-qualified type name

- Changed over-qualified {PIXI.scaleModes} back to {Number} for
  consistency with rest of documentation where scale modes are used.

- @returns to @return

- Added types to normalized arrays, when such was easily visible

Added tint to Canvas Graphics

changed vec4 to vec2 for color

Merge branch 'dev' of https://github.com/GoodBoyDigital/pixi.js into dev

little optimization on toLocal + toGlobal

Merge pull request #1177 from pnstickne/wip-pixi-docs ...

Documentation - Initial stubs, fixes, unification. Free lunch fer your beer.

Documentation - Array(Normalization) ...

YUIDoc does not have a standard (or really any) way of describing inner
types of arrays and there are two general forms used in the current pixi
code:

- `Array<X>`
- `Array An array of X`, or an _inconsistent_ variation of such

The first form is not even parsed correctly by the YUIDoc tool and the
contained type, X, does not appear in the documentation output (or parsed
data) at all. Other similar forms that fail to work are: `X[]`,
`Array{X}`m and `Array.<X>`.

The second form mixes the type (`Array`) and the description of the type
("An array of X"). It would suiting to say "Array of X".

Thus thus commit changes _both_ of the above forms into a normalized
`Array(X)`

While I do not want to impose this as the final chosen representation for
such types, it does _immediately_ address the documentation issues
mentioned above _and_ renders the nested type name in the documentation
output.

If a better method or converntion is found this _consistent_ and
generatable intermim VB-like syntax can be trivially found and replaced.

Another alternative of course, it to forbid anything more complex than
`Array` as a type.

Documentation - updates wrt. comments and fixes ...

- Corrected invalid '@name' to '@method'.

- {Integer} reverted to {Number}.

- Changed the 'scaleModes' link to 'PIXI.scaleModes'

- Removed base/prefix types; verified return signaures.

- Fixed mah typos.

Documentation - the rest of 'em changes ...

- Forgot to the scaleMode link changes

Documentation - initial stubs and fixes ...

- Pixi.js
  - Added basic YUIDoc entries to Pixi.js, including the addition of the
  "namespace-class".

- CanvasTinter
  - Removed constructor from invalid double static/constructor pair
  - Added static annotations

- VideoTexture
  - Added initial documentation/stubs

- Updated all "scaleMode" params to link-to PIXI.scaleModes

- Fixed autoDetect* method documentation so they show up in PIXI class

fix updateCache not clearing the cached texture ...

this will clear the cached texture before render

removed dead space

Fixed Graphics.arcTo issue

Merge branch 'master' into dev

republished files

Merge pull request #1164 from GillesVermeulen/non-rotated-pivot-fix ...

Fix pivot of non rotated display objects

Fix pivot of non rotated display objects

republished files for v2.1

Merge branch 'dev'

added default blend mode to strip

Merge pull request #1162 from glafarge/patch-1 ...

Fix unused variable WebGLRenderer.instances