fadeComponent

[d.healey]

Thank you! Good bye to extra timers :)

[Dan Korneff]

fadeComponent only seems to work 60% of the time for me. Anyone else notice this?

[Dan Korneff]

I've actually found a strange pattern. It works 5 times in a row, then fails 4 times, then works 3 times in a row, then fails 2 times, then fails on first try. then back to 5 times in a row

[d.healey]

@Dan-Korneff Got a snippet that demonstrates the issue?

[Dan Korneff]

@d-healey of course a minimal example works just fine. Lemme dig a bit deeper.

[Dan Korneff]

HiseSnippet 1145.3ocsV8uSabCG2GfqZtQmVk1CfE+0gDKMGPYfllVf.zgVAhVXcSBUgbtyIwBe1m74.MpBoo8jr2g8BzGo8Fr80muK2kQfVEsdRIRe+8mu+ves6pUQrrLkF403hIoLj2p3dSjlQcFQ4RzIGZYjRkLAwvxLnCljRyxXwHOukekUCuFqfx+96e3.pfJiXUrPn2n3QrWyS3lJtca+Sbg3XZL6BdRMs2t8IQJYGkPMFPyx3VnTZz0zgrynV0VBi7dxQwbiR2yPAvf7V4.U7jdiT2Jc5+FdFuufYIBQ8.G4XerRDaQrkKpyHtHtaYVmg.uzspFrrqF703S4w7o7qpEeUt.RkE0qGdKMK7VdF3EVGdspAu4.IuZPZEGjdNtWjlmZpjXwyWfOQZX5ATnrWGJNcQK8WKi6n.MjllIzqYGqAhoVDrSqVaPf+V+678gRelgbCUS5Z61gjumTZ4PloiJIUIAhf0bhWCroxjDn9bkaJ4gLqRkYM8fwFiR9vgqPt0HeWnalwLcAuY9Y0XCWxBFLVFY3JYvv0eOA97aLr4.XDaegHvMNk0ruXLCbgU7PqCdklFyg.bLnWvkkZc6HtgsAApJaB+J4pzT4PG6vce6TuDqo2tufOTxhuf8N.pcD7nqIFEIRnxXqsA4xvV4VYFwyro0uxiMiBVuhwOx3CGYBV+saPVSvFXfrj397uylvu3EpTljjW174RAjsjxrknjE0FagSqDAQkUsMfJqMe8eueC9ffBhF.Uip1PyAvIvpBcHjb4SBMty+NHzejtgsFVD2NTgnObRM3+BHaF.oPd0nHGp5fmpFmwlZ5zVH6FHNk.OmnYjsrxhcI.35Lkf0LUys340BQ97jeQYi7f4GzFdoaR2lfPctVc7LkgctLHOr924eOQCFLWYEoofomqX61M8iYXfbbReltd2xpHbje18H3GdOR80bQtNVMEUxSjby4vHzCs7CUzls6bJPEnpIeiyWVrww0TQbXwRCbQGFkC45a5Q+xIGRMzRGA9DhSJSa31Tv6P1MvMAtUYMvGxxt1nRgk5SaP.aWXeV4hNaSLOpqhq5pn2UOnSpSbq8z0TFe3OZOJ+zUcNv3l51xgtLarxOylQNWJlffy9IkW+rJdqvcC2q0V6DtC5l5Kts42GGyOE6F0qg2OzucEd+8KaOKdI56gWQ6YQz1at2160B.0dnGOQRoZ.c0f4LUPTMAO4SnUWqhKqkA+4j17rSUIfen5ItALCrGDbJNejCc+KwfqOUwiETyr2oZeHQg.3.xLWjYurRlwMSp+Pi+2tn8SEhOG2kahFMeLtzbvHbL3yAFKddxyvGMX.KxTAvUvG+aeddKBxcK6vSoFMGFEvmMNoGLPFwfnKg4I6BJukrqRbzsrz1JPOlLNm3efuBggVZuBggkBQIzHs5pH2BH6CfdZNG.Sx7290.epklLcuCF2pYKTB7Vrqhhro+2.a2luMat.1r0BXy1KfMubArYmEvlucArY2G0F6yf2erQk3NN.L5dT99eOuijTXxJeJD8u7NGwYN

Sometimes it works for a few minutes, sometimes it fails almost immediately. If I hammer the fade like in the above gif, the panel becomes unresponsive. If I wait for the fade to complete before changing it's state, the show/hide will still work, just without the fade.

[d.healey]

Yeah I'm seeing weird behavior too when using consecutive calls.

[HISEnberg]

@d-healey @Dan-Korneff I am noticing this issue till this day! Was this ever resolved? Does it carry over to the exported plugin or is it just while working within HISE?

[d.healey]

@HISEnberg said in fadeComponent:

Does it carry over to the exported plugin or is it just while working within HISE?

Not sure, I haven't used it much.

[Dan Korneff]

@HISEnberg I haven't used it since.

[aaronventure]

@HISEnberg Unfortunately it does.

Issue on Github since last year

[Engine] fadeComponent method is inconsistent, sometimes instantly changing visibility · Issue #481 · christophhart/HISE

fadeComponent has been demonstrating inconsistent behavior for a while now, with no apparent trigger. Assigning components to two panels and then triggering fadeComponent on these panels back and forth results in the panel (and as such, ...

GitHub (github.com)

My workaround is to use a custom timer per fade group and refer to it in LAFs as color alpha, but of course it would be great to not have to do that.

[rglides]

Weird, it works perfectly in your snippet every time for me, multiple attempts. I'm using version 4.0.0 build 60, if that might help identify the issue

[HISEnberg]

@aaronventure Okay thanks for confirming everyone. I figured a timer would work just as well but I was hoping to avoid having one run in the background waiting for a fade event. I suppose a combination of a broadcaster and timer would work but not fun to implement.