WebGL state Diagram

[letochagone]

I added examples of the state diagram.
If I add examples it is so that I have a clear understanding of the fundamentals of webgl.
Here is my little problem. I added two examples that display the contents of a texture. The code is the same, except for loading the image: there are 2 syntaxes of Teximage2D.

first example:

well, it was a bit complicated to integrate the base64 character string. But the result is good. some pixels are a bit transparent, and it looks good

second release:

then it's strange, the texture display is different (the final display is ok).
In short, I wonder then if it is a bug, or if it is me who did not understand something

[greggman]

The state diagram is not a generic debugger, it is not designed to handle any sample. It is designed only the handle the samples that are in it. If you add your own samples you'll have to modify the state diagram code to handle them.

[letochagone]

I added other examples that worked well. I just added the source code of these examples :

these examples have been interpreted. I didn't have to change anything else.
that's why I thought that if this last example gave a curious result it was due to my misunderstanding of WebGL.

Besides, the example that worked well (i.e. the result corresponded to what I think I understood) is the example where the image is loaded (without using the ..onload() )
Which made me believe that the interpretation was powerful.

I was not using adding examples for the purpose of debugging, but for the purpose of understanding