https://linen.dev logo
Join DiscordCommunities
Powered by
# openfl
  • a
    you should ask your flixel questions in #165234904815239168 redacted
  • f
    Txt*
  • a
    i'm not sure how text is displayed in openfl
  • a
    but essentially what you'd want to do is the following:
  • a
    1) Create the text object in your class to reference 2) Initialise that text object in your constructor 3) create a function in your class with:
    Copy code
    hx
inline function formatTime() {
  return DateTools.format(Date.now(), '%r');
}
    4) In your update loop do something like
    Copy code
    hx
this.text_label.text = formatTime();
  • t
    hey, i didnt see thies message, so sorry - here's the output https://pastebin.com/0qQs5qqp
  • h
    no worries. Ok this all looks standard and there doesn't appear to be any other error as you said. So I forget the original question. Was it just about the output or is something also not working ?
  • t
    Nope, its just the output
  • t
    Code works all well afaik
  • h
    I vaguely remember someone reporting an issue with debug being printed when it wasn't needed but I never saw it myself and never tracked down when it happened
  • t
    ah
  • t
    assuming its coming from this function
    Copy code
    hx
    // }
    @:noCompletion private function __createGLShader(source:String, type:Int):GLShader
    {
        var gl = __context.gl;

        var shader = gl.createShader(type);
        gl.shaderSource(shader, source);
        gl.compileShader(shader);
        var shaderInfoLog = gl.getShaderInfoLog(shader);
        var hasInfoLog = shaderInfoLog != null && StringTools.trim(shaderInfoLog) != "";
        var compileStatus = gl.getShaderParameter(shader, gl.COMPILE_STATUS);

        if (hasInfoLog || compileStatus == 0)
        {
            var message = (compileStatus == 0) ? "Error" : "Info";
            message += (type == gl.VERTEX_SHADER) ? " compiling vertex shader" : " compiling fragment shader";
            message += "\n" + shaderInfoLog;
            message += "\n" + source;
            if (compileStatus == 0) Log.error(message);
            else if (hasInfoLog) Log.debug(message);
        }

        return shader;
    }
  • h
    ok so in there is a print of debug info. In your case you see "info"
  • h
    yeah that
  • t
    how would i disable it though?
  • h
    not sure exactly - I'm not sure why it's printing
  • r
    there was a commit recently to disable debug shader info in JS: https://github.com/openfl/openfl/commit/5dbaefa7d4d89eff9870f05b72f0494d571c2507
  • h
    that's the thing
  • r
    it hasn't been included in a release yet
  • t
    Oh thats interesting - the issue seems to also occur on native builds too
  • t
    Should I use the github version then?
  • t
    will test it out
  • h
    oh that's it - it was dumping debug even though the shaderlog was empty
  • h
    the fix looks general not just js
  • r
    right now, the develop branch on Github contains only bug fixes since the last release, so it should be very stable
  • t
    For some reason it's still printing out all the debug stuff...
  • t
    even though the haxelib git updated the Shader.hx file
  • t
    Copy code
    hx
    @:noCompletion private function __createGLShader(source:String, type:Int):GLShader
    {
        var gl = __context.gl;

        var shader = gl.createShader(type);
        gl.shaderSource(shader, source);
        gl.compileShader(shader);
        var shaderInfoLog = gl.getShaderInfoLog(shader);
        var hasInfoLog = shaderInfoLog != null && StringTools.trim(shaderInfoLog) != "";
        var compileStatus = gl.getShaderParameter(shader, gl.COMPILE_STATUS);

        if (hasInfoLog || compileStatus == 0)
        {
            var message = (compileStatus == 0) ? "Error" : "Info";
            message += (type == gl.VERTEX_SHADER) ? " compiling vertex shader" : " compiling fragment shader";
            message += "\n" + shaderInfoLog;
            message += "\n" + source;
            if (compileStatus == 0) Log.error(message);
            else if (hasInfoLog) Log.debug(message);
        }

        return shader;
    }
  • h
    so I would add some debug prints for hasInfoLog and compileStatus and see what they are
  • h
    @thousands-state-46635 thinking more on this I wonder now if the warning about the version is ending up in the shaderInfoLog and then causing everything else to be dumped. If it is then this fix above won't help because the shaderInfoLog is not empty. Actually that seems likely given what is being printed. You could prove it with debug prints but what is there basically proves that anyway. So if that's true then the next question is, how are you creating the shader ?
1...202122...57Latest