Don't swap in graphic when only the type is needed.

Change-Id: I0066e7ffff216e02c75561844650127c3d866c10
Do not check a reference

Change-Id: I5baac12f97ea7fa36293844331ca548b7bc2cdfd
Always call ImplAfterDataChange() when data is changed

Call it inside ImplAssignGraphicData() which assign
GraphicObject members using Graphic's data. With that
ImplAfterDataChange() method also called in constructors.

It's important to call ImplAfterDataChange(), because this
will triger the auto swaping mechanism.

Change-Id: I45af91f8df2fb5b0143fcc5eb05e82e4d408d0bc
Avoid using null pointer as a special indicator

When ImpGraphic::ImplSwapOut() is called with null
pointer it was assumed that it is becase the graphic is
a link and so we don't need to swap out it actually (we can
load it anytime using the link), only clear the graphic's
internal data.

The problem with that it can happen that ImplSwapOut()
is called with null pointer accidentally on a non-link
graphic object which leads to that we loose the graphic.
Seems more robust to use an explicit indicator
(GRFMGR_AUTOSWAPSTREAM_LINK) for links swapout.
indicator

Change-Id: Icf31524a192c7866278ba6a13eb85648aa69f554
Test ODF import / export of images

Change-Id: Ib3ac4f285a49e5f7b2a6613466080329bdb490ac
Remove manual SwapOut() call in ODF export

We have a good auto swapout mechanism which will
prevent excessive memory use.

Change-Id: I362f51c724ac31704561abe8b961910f5d490f04
MS export: don't need to manually swapout images after swapin them

We have some good auto mechanisms for that.

Change-Id: I487dbf4a5fc69c7563dfbc5c21f9ebdb05ba6b9e
DOC import: avoid manual swapout call.

No reason to swapout the image directly after the import
because it will be used for rendering just a second later.

Change-Id: I78c8ef9225c55f306182dc5efd7bcaf0e88521c0
Make SetSwapState() an internal method

So we can be sure it is always called when user data changed.

Change-Id: If107907afffb85a7a57817f5807847a5c028416c
Don't call SetUserData() when it actually does not change

This call leads to infinite loop, because SetUserDat() set
graphic state to swapped out which triggers ImportGraphic..

Change-Id: Id49c38e60a0bb924ff5ec0465e4fb141df61abe5