[Interest] How to know bindTexture failure

Calogero Mauceri mauceri at actgate.com
Mon Oct 8 12:40:18 CEST 2012


Il 08/10/2012 12.34, Samuel Rødal ha scritto:
> On 10/05/2012 05:21 PM, Calogero Mauceri wrote:
>> Il 05/10/2012 17.04, Samuel Rødal ha scritto:
>>> On 10/05/2012 04:46 PM, Calogero Mauceri wrote:
>>>> Hi,
>>>>
>>>> is there a way to know programmatically whether the
>>>> QGLWidget::bindTexture function fails?
>>>> Sometime my bindTexture fails, I can see in the log file there is a line
>>>> reporting the binding failure:
>>>>
>>>> texture upload failed, error code 0x500, enum: 3553 (de1)
>>> Hmm, looks like the error reporting is a bit lacking. If you have your
>>> own build of Qt you can uncomment the line that says #define
>>> QGL_BIND_TEXTURE_DEBUG in qgl.cpp to get more detailed debug output from
>>> the bind function.
>> Thanks Samuel for your reply.
>> We do have our own build of Qt, but I really would avoid to change them,
>> it would be very difficult for us to keep our changes in sync with the
>> new Qt distributions.
> I didn't mean a permanent change, just a temporary one to help figure
> out what step in the texture upload that goes wrong.
>
> If it only fails in certain circumstances, maybe you could file a bug
> about that.
>

Actually it fails when the texture image is big. How much big is machine 
dependent.
That's why I would like to know whether the texture loading fails in 
order to properly warn the user.

Calogero

-- 
Calogero Mauceri
Software Engineer

Applied Coherent Technology Corporation (ACT)
www.actgate.com





More information about the Interest mailing list