Functions are displayed as variables about dox HOT 7 CLOSED

I'm sure it's from this change: 2935767

I have to get the get/set properties under control. Is there something special about this method? Could you post its XML?

from dox.

Why are we doing so much work in the template? I'd rather do it when processing and pass the needed info to the template.

from dox.

@Simn Nothing special at all, in fact, it seems to happen for all methods.

<replaceColor public="1" set="method" line="1010">
            <f a="Color:NewColor:?FetchPositions" v="::false">
                <x path="Int"/>
                <x path="Int"/>
                <x path="Bool"/>
                <c path="Array"><c path="flixel.util.FlxPoint"/></c>
            </f>
            <haxe_doc>* Replaces all pixels with specified Color with NewColor pixels
     * @param   Color               Color to replace
     * @param   NewColor            New color
     * @param   FetchPositions      Whether we need to store positions of pixels which colors were replaced
     * @return  Array replaced pixels positions</haxe_doc>
        </replaceColor>

I did generate the docs + the xml with haxe 3.1.3 though, does that matter?

from dox.

@dpeek: That's not so easy because we're working with the CType data, which we can't extend in a trivial way. I have a Haxe issue open to address this problem: HaxeFoundation/haxe#3471

Of course we could instead have some API method for this. In fact, I'm not sure what/if I was thinking when I made that template. :)

@Gama11: Can you try updating hxtemplo? There was some weird issue related to order of switch cases.

from dox.

@Simn That fixed it - mostly. Still seems to fail for inlined functions:

Previously:

Now:

<resetFrameBitmapDatas public="1" get="inline" set="null" line="1265">
            <f a=""><x path="Void"/></f>
            <haxe_doc>* Helper function for reseting precalculated FlxFrame bitmapdatas.
     * Useful when _pixels bitmapdata changes (e.g. after stamp(), FlxSpriteUtil.drawLine() and other similar method calls).</haxe_doc>
        </resetFrameBitmapDatas>

from dox.

I'd expect the same get/set combination from an inline variable, which would make this indistinguishable. I guess we can rely on the type in this case because there's no such thing as an inline function variable, but it's still a bit bad...

from dox.

I've "fixed" it.

from dox.