Bug 1057904 (Part 2) - Make imgFrame::LockImageData and UnlockImageData private. r=tn

This commit is contained in:
Seth Fowler 2014-11-26 13:22:10 -08:00
parent 10e5d880fa
commit dbd2810ea1

View File

@ -64,9 +64,8 @@ public:
* This is appropriate to use when drawing content into an imgFrame, as it
* uses the same graphics backend as normal content drawing. The downside is
* that the underlying surface may not be stored in a volatile buffer on all
* platforms, and raw access to the surface (using RawAccessRef() or
* LockImageData()) may be much more expensive than in the InitForDecoder()
* case.
* platforms, and raw access to the surface (using RawAccessRef()) may be much
* more expensive than in the InitForDecoder() case.
*/
nsresult InitWithDrawable(gfxDrawable* aDrawable,
const nsIntSize& aSize,
@ -113,9 +112,6 @@ public:
bool GetCompositingFailed() const;
void SetCompositingFailed(bool val);
nsresult LockImageData();
nsresult UnlockImageData();
void SetDiscardable();
void SetOptimizable();
@ -151,6 +147,8 @@ private: // methods
~imgFrame();
nsresult LockImageData();
nsresult UnlockImageData();
nsresult Optimize();
struct SurfaceWithFormat {