From Sukender, "I experienced as some users before: I tried to rescale an image without a valid rendering context... And had problems to unserstand what the "GL_OUT_OF_MEMORY" meant! So I added a few comments for future users."
This commit is contained in:
@@ -135,10 +135,14 @@ class OSG_EXPORT Image : public BufferData
|
||||
virtual void readImageFromCurrentTexture(unsigned int contextID, bool copyMipMapsIfAvailable, GLenum type = GL_UNSIGNED_BYTE);
|
||||
|
||||
|
||||
/** Scale image to specified size. */
|
||||
/** Scale image to specified size.
|
||||
* \warning The method uses gluScaleImage() and thus needs a valid rendering context.
|
||||
*/
|
||||
void scaleImage(int s,int t,int r) { scaleImage(s,t,r, getDataType()); }
|
||||
|
||||
/** Scale image to specified size and with specified data type. */
|
||||
/** Scale image to specified size and with specified data type.
|
||||
* \warning The method uses gluScaleImage() and thus needs a valid rendering context.
|
||||
*/
|
||||
virtual void scaleImage(int s,int t,int r, GLenum newDataType);
|
||||
|
||||
/** Copy a source Image into a subpart of this Image at specified position.
|
||||
|
||||
Reference in New Issue
Block a user