[Cogl] [PATCH] Allow lazy texture storage allocation

Neil Roberts neil at linux.intel.com
Mon Dec 10 04:44:33 PST 2012


Robert Bragg <robert at sixbynine.org> writes:

> Right, I'm fairly sure we discussed this in meat space at the time I
> was doing this since it's not entirely clear which way is better.

Ah right, sorry.

> Potentially we could get rid of the CoglError args as you say, though
> I can still see some value in being able to catch hardware limitations
> early before allocating the textures.

It seems like if you wanted to check the hardware limitations then
constructing a temporary texture in order to catch the error would be
quite an awkward way to go about it. Maybe it would be better to have a
separate function to do that? We could leave the constructors without
the error argument for now and then at least we always have the option
to add a separate function later.

Regards,
- Neil
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.



More information about the Cogl mailing list