On Mon, 2 Oct 2000, Stefan Seefeld wrote:
> "Brian S. Julin" wrote:
> >
> > On Sat, 30 Sep 2000, Lee Brown wrote:
> > > I think I see what you are trying to do. You could use a structure to associate
>the filename with the visual.
> > >
> > > struct texture {
> > > ggi_visual vis;
> > > char* filename;
> > > };
> > >
> > > Then work with the texture structure instead, dereferencing each member as
>appropriate when neccessary.
> >
> > I think that he's trying to avoid the syntactical ugliness of
> > the dereference while calling normal LibGGI api functions.
>
> class GGIExtension : public GGIVisual
> {
> ...
> };
>
> sorry, couldn't resist...
err... I write my 3d-project in C and not in C++
CU,
Christoph Egger
E-Mail: [EMAIL PROTECTED]
- private data storage in visuals possible? Christoph Egger
- Re: private data storage in visuals possible? Brian S. Julin
- Re: private data storage in visuals possible? Christoph Egger
- Re: private data storage in visuals possible? Lee Brown
- Re: private data storage in visuals possible? Brian S. Julin
- Re: private data storage in visuals possible? Stefan Seefeld
- Re: private data storage in visuals possible? Christoph Egger
- Re: private data storage in visuals possible? Christoph Egger
- Re: private data storage in visuals possible? Lee Brown
- Re: private data storage in visuals possible? Andreas Beck
- Re: private data storage in visuals possible? Brian S. Julin
- Re: private data storage in visuals possible? Christoph Egger
