Re: [cadcdev-tiki] Re: Making m_txr protected vs private so Texture can be extended and m_txr

[atani <at...@at...>]

On Jan 1, 2006, at 11:28 AM, Dan Potter wrote:

> On Jan 1, 2006, at 10:52 AM, cadcdev-svn- 
> co...@li... wrote:
>
>> Making m_txr protected vs private so Texture can be extended and  
>> m_txr accessed.
>
> Speaking of this, am I the only one who wished they'd put an  
> access_cast in C++? I think the protected/private stuff is a good  
> guideline to follow (and when it

Very true.  Having a way to get at the "private" methods would be  
cool... I am not sure how best to implement this and ensure that  
things are still protected properly from tampering..  In this case I  
just wanted to be able to extend the Texture class so I can have  
BZ2Texture which is basically a raw KMG that has been bzip'd.  This  
resulted in a smaller file than with png/jpg compression.

In Tiki, I think I already pushed this change out, if not I will get  
it pushed out shortly.  I am thinking of adding a RawTexture class  
which you define the raw texture data which should be uploaded  
directly to opengl, think of this as a way to handle generated  
texture data that does not change.

Mike