[x3dom-users] Parsing? issues when inlining a x3d file with included shaders

[Michel, F. <fra...@ig...>]

Dear x3dom team,

we found a possible parsing bug when including an external X3D file (including <ComposedShader>) through the <Inline> Tag.

When the "<" or "&&" operator is used in the shader the model will not be loaded (ERROR: No Scene in resource INFO: Inline: downloading not_working1.x3d done).
The same shader works fine when it is directly put in the main x3d scene. Below you can find a code snippet which does not work.

I can also send you an example if you provide me a contact person (or just stop by my office upstairs :))

Best regards,
Frank

The following shader works fine when used in the main <X3D> scene but does not work when included through <Inline> as part of an external x3d file:

<shaderpart type="FRAGMENT">
            #ifdef GL_ES
              precision highp float;
            #endif

            void main(void) {

              //The double ampersand is not parsed correctly and causes the entire visualization to fail
              if(0.0 == 0.0 && 0.1 == 0.1) {
              }

              gl_FragColor=vec4(1.0,0.0,0.0,1.0);
            }
</shaderpart>

Same effect if you use "<"
//The less-than sign is not parsed correctly and causes the entire visualization to fail
              if(0.0 < 0.1) {
              }


-------------------------------------------------------------------------------------
Dr. Frank Michel
'Interactive Engineering Technologies'
Head of Group Real-Time Visualization

Fraunhofer-Institut für Graphische Datenverarbeitung IGD
Fraunhoferstr. 5 | 64283 Darmstadt | Germany
Telefon +49 6151 155-467 | Fax +49 6151 155-139
fra...@ig...<mailto:fra...@ig...> | http://www.igd.fraunhofer.de/iet