Custom look and feel component ID

d.healey

@DanH Latest scriptnode

d.healey

@ustk said in Custom look and feel component ID:

Speaking of the slider custom laf, why the heck are the sliders disappearing as soon as you touch them?

Do you have any ideas what's causing it?

ustk

@d-healey Unfortunately no...
Or maybe it is related to the refreshing time of the interface since custom LAF functions are constantly refreshing? It is so annoying that I can't even touch a slider without seeing all of them instantly disappearing. So again, we need to deactivate the custom LAF until export...
@Christoph-Hart do you have any input on this issue?

d.healey

@ustk The refresh thing sounds possible. I noticed the knob LAF function triggers while the mouse is over the knob, even when you haven't clicked the mouse. Is it possible to disable this "hover" callback?

ustk

@d-healey Without being actually sure, I don't think we could deactivate it since it is part of the Juce slider behavior. But I might have wrong

ustk

@d-healey And moreover I think the problem would still the same when you click a slider...

ustk

@d-healey It appears that the issue is only slider related, I just tested with 70 toggle buttons with no issue, knowing that toggle buttons also have a hover reaction...

ustk

@d-healey @Christoph-Hart I think I have narrowed down what the problem is.
As soon as you create a path, whether you use it or not, it seems that sliders are disappearing after the same number of function call, like if something is not cleaning properly and error builds up.
Note that the issue is not related to the number of sliders unlike what I said above.

Try this snippet by just commenting the path line:

HiseSnippet 1062.3ocsV8uaaaCDlxIpa1conEXO.D4uTJ7jkS+wFPPQciicmVi+AhbJJPQQ.sDsManHMnnSl2PA1ixdT1ywdJ1av1QIKakDuzTOLgfXbe22Q9wSGuS8UxPZRhTgrJOX9TJx5arClKzSZNgvDH+iPVOvtCIQSU3LnCmOkjjPiPVVa8ZCfU4sQoO+0KOjvIhP5JHD5sRVH8XVLSuBsei2v371jH5.VbA1OsgenTzTxky.8rksGZJI7bxXZWhgVIaj08ZEwzRUflnoIHqsOTFMOXh7RQF+2xRXC4TiQcT.rPYvsk7HihMnnlSX7n94m6DDrJ8WkE1JKK7s1cXQrk3qxFOL0AdUDEyGVktM4U+yKOu0IOqBxa6L48H6fPEapdkGi1tusu.dQMh.uBJJqLtnRy2xtoDXHztwjyosUfwxHbdtmWU7y7716.LvJQxotgbJQ4..0pwDg7YQTmcccqA+cVPyS76OHn1DJeJU49wjc26fJUp.u+Rz3KHJLmLB+BbKwXl.VHEExHulKGR3Yp4Xo77WIhZSobGSj.cWEcLyTo0dlHTyjBmciTjKOQpIp4AbVDUsaU7nbmiqhkC+3dU90JX3YraBUmU53j8Sh6P9L5EL3fn26fcRYk9Oi5lRzS.4kmNxzWe.L6zh+oSCFfa1qSmVcGf6c5.7fezO.ere2V3A8vs8eG.zB6GDbZqBqbsZl0cYZamhfIvoP2kdYvrgo6iWUuqwfCYpARm5Uw+6dpudOd2zSHWlPy2rbe6rHWojlJTmNFh88e79OFxjtWPf7UWoJlvY+BMpJ98FTBjZd+9en19UWZ8Dv5CWcIqUar6H3Rc5tY1+zWNozyIlQ3DZn145tp7ozhm+yO40FXonqTS6IbLkGkq7oJ3q6Zzn05yTPnjbNUsV2l9UpaKPGwr3gTUUbZxbIQ3h6U6Lb+6Vmgvr5yBDkBeAS2aJcgcwVa4m5budnkG1hPqNiEQSOZqg1Jna1ZBs39ioI0B5.UcZKpGrnEU1EWDCz3WY+FgbXcTZtYQa+ee5K9yWhN0+HhljuLvJB6BzVQyL4JqifawgzrNeksOhlbtVNMka7Tovr+V26yto+7x4L+Fqw7kF+wYMtjEomrZJDqwDJa7DcQDzMaACCBjQy3D8UmNXFItvATXbk1vlVshDlddwQleAiL7tySztqx8Q18Y5vIqWukVidg2P+eq2ECf2wt0nQPuhUhca61uaSm19EHkSjyzLwXn0nhA0L1cmEG.SSBofRDBJG1HaqRlZ+LaOisIyDPEQoF+M7rvYcis0Bm0ychhIgJ4YgY2XLi3+5TDPShzuzoL7IWfMd4UEaaOWOTL7kGmEFZREeGn80Gy9aPLOYCh4oaPLOaCh44aPLe+FDyObqwX9nuWMSKiytl..8ak1xxxpkf.UYoUjn+w0ZFfA

d.healey

@ustk Yeah I had the issue with a single slider.

ustk

And then confirmed with buttons too

HiseSnippet 933.3ocsVstaaaCElxIpnVaoXEnO.D4WN.YJ1a8FZvPSiibm1hufHmf9u.ZIZI1PSJPQkLig7zrWr9Hz2fsCE8sr4FD3gPXXfy8OdtQMPIioEERExo9vo4Tjy26FMUnyZmQXBT3IHmm41kTnoJrk0wSyIEEzDjiyVezvvo91npyWe+wDNQDSWxBgtPxhomxlvzK4N3nemw4cHIzgrIqn8KOJLVJZK4xR.Oa41DkShuhjR6QLpUyE47jfDlVphzDMs.4r8wxjoQYxaDV8ufUvFwoFhVnHvQV1cj7DChMbQsyX7jAyu2EHvKCVlE1xlEdgaWVBaA+kYienR.doEqlObpcevq0pvq4CGdNq.ussv64tQwJVtdoDC19N2PATnFSfRvpvxpKp1zZtskfFBs+DxUzNJfXgEMdcyl6ieUyl6cHFzpPxo9wbJQ0.XbvALQLuLg1XWe+CfeWF09rvACiNHixyoJ+OWr6dG544A0uBM9ZhByIiw+BNPjxDfiTTHi7QtbDgaQyoR4UePjzgR4P.71wyCLvWQSYldsNkhXMSJZrahhbyPYZJmdboVKE6tOd7bgo6iki97dd+oGFNlflSzYPTmeKsgc.vzdIv+14QCws62saPug39mODO7WCivmF1K.OrOtS3m.FA3vnnyC1oxoU+k5WP011xFP.8ulvKo32isrJ7GAjWyfDlF+tELkJhHkpnI6cn0U6LyWigd+ynw5JWQ.DBW+aqRd+uOyyLXonmTS6KZXRN08t0C+uEMd7ZkYxbJImSUqUrYdUceF1PTNYDUsOtJGsPQnw8tSFte6IiUGbisExUTTJBELc+bp3aMuflU8MSNyPEnptZt4Yylar8RHFLdT20RzBUA4UWmgNO7DhlL2QfOg3.c6Zl4J3bBTzio1Ax5tmPKtRKyqzcRtTXPfySd.g8OVDxuvNZ5x3ewQ2vRzYPtx4u.xLJKMSantsZG5+Ym.rYRlTxI56ttxridl.nRcm8BlYeQASOc0K8ixNrGJbet6.lNNa83s1ZvKTadrw6rWD1wMX7XXrcIX21symd7W+iNSVpYhztDshA8Jt8JmDAaXho.RDBJ2LM4Tyz2aoaZnMYlHpHoh3ugyLgsLzNyD1ZtPzDRrRdYrcZw7lySq3.XRT8zac3a..Z7hgDW2l9MQSfmBuLN1jJ9Q.6q2leZCr4m2.ad4FXyq1.ad8FXya1.ad68Zi4qP9PoVNwNl.LFDTsrxwIPPftrpNRz+.pw+4R

d.healey

@ustk said in Custom look and feel component ID:

And then confirmed with buttons too

HiseSnippet 933.3ocsVstaaaCElxIpnVaoXEnO.D4WN.YJ1a8FZvPSiibm1hufHmf9u.ZIZI1PSJPQkLig7zrWr9Hz2fsCE8sr4FD3gPXXfy8OdtQMPIioEERExo9vo4Tjy26FMUnyZmQXBT3IHmm41kTnoJrk0wSyIEEzDjiyVezvvo91npyWe+wDNQDSWxBgtPxhomxlvzK4N3nemw4cHIzgrIqn8KOJLVJZK4xR.Oa41DkShuhjR6QLpUyE47jfDlVphzDMs.4r8wxjoQYxaDV8ufUvFwoFhVnHvQV1cj7DChMbQsyX7jAyu2EHvKCVlE1xlEdgaWVBaA+kYienR.doEqlObpcevq0pvq4CGdNq.ussv64tQwJVtdoDC19N2PATnFSfRvpvxpKp1zZtskfFBs+DxUzNJfXgEMdcyl6ieUyl6cHFzpPxo9wbJQ0.XbvALQLuLg1XWe+CfeWF09rvACiNHixyoJ+OWr6dG544A0uBM9ZhByIiw+BNPjxDfiTTHi7QtbDgaQyoR4UePjzgR4P.71wyCLvWQSYldsNkhXMSJZrahhbyPYZJmdboVKE6tOd7bgo6iki97dd+oGFNlflSzYPTmeKsgc.vzdIv+14QCws62saPug39mODO7WCivmF1K.OrOtS3m.FA3vnnyC1oxoU+k5WP011xFP.8ulvKo32isrJ7GAjWyfDlF+tELkJhHkpnI6cn0U6LyWigd+ynw5JWQ.DBW+aqRd+uOyyLXonmTS6KZXRN08t0C+uEMd7ZkYxbJImSUqUrYdUceF1PTNYDUsOtJGsPQnw8tSFte6IiUGbisExUTTJBELc+bp3aMuflU8MSNyPEnptZt4Yylar8RHFLdT20RzBUA4UWmgNO7DhlL2QfOg3.c6Zl4J3bBTzio1Ax5tmPKtRKyqzcRtTXPfySd.g8OVDxuvNZ5x3ewQ2vRzYPtx4u.xLJKMSantsZG5+Ym.rYRlTxI56ttxridl.nRcm8BlYeQASOc0K8ixNrGJbet6.lNNa83s1ZvKTadrw6rWD1wMX7XXrcIX21symd7W+iNSVpYhztDshA8Jt8JmDAaXho.RDBJ2LM4Tyz2aoaZnMYlHpHoh3ugyLgsLzNyD1ZtPzDRrRdYrcZw7lySq3.XRT8zac3a..Z7hgDW2l9MQSfmBuLN1jJ9Q.6q2leZCr4m2.ad4FXyq1.ad8FXya1.ad68Zi4qP9PoVNwNl.LFDTsrxwIPPftrpNRz+.pw+4R

That's concerning, even though it doesn't show in the compiled plugin does it have an effect on CPU usage or cause other issues?

d.healey

I wonder if the issue is something to do with this loop in the drawWithGraphics function?

    g->getDrawHandler().flush();

    DrawActions::Handler::Iterator iter(&g->getDrawHandler());

    while (auto action = iter.getNextAction())
    {
	action->perform(g_);
    }

d.healey

@Christoph-Hart Any ideas? Is it safe to use LAF in a project?

Christoph Hart

Wow that was an easy one - I just forgot to initialise the timeout logic correctly when calling scripted LAF functions so it threw a timeout as soon as the execution time was bigger than ~0...

Natan

@Christoph-Hart I reported This Execution Time Out Before
So It Was LAF Mistake?

d.healey

@Christoph-Hart said in Custom look and feel component ID:

Wow that was an easy one - I just forgot to initialise the timeout logic correctly when calling scripted LAF functions so it threw a timeout as soon as the execution time was bigger than ~0...

You're on fire today!

Natan

@d-healey So is there Any Quick Fix?
I'm On Bed!!!
Do i Need To Get Up?
Another Sleepless Night? or What?

d.healey

@Natan Check github, Christoph has made a load of updates the last couple of days and just fixed the LAF issue.

Natan

@d-healey ‍️‍️‍️‍️‍️‍️‍️️‍️️‍️️‍️️‍️️️‍️️‍️️‍️️‍️️️‍️️‍️️‍️️‍️To The Github No Sleep Nothing, Like My 17 Past Years

Natan

@d-healey said in Custom look and feel component ID:

I wonder if the issue is something to do with this loop in the drawWithGraphics function?
    g->getDrawHandler().flush();

    DrawActions::Handler::Iterator iter(&g->getDrawHandler());

    while (auto action = iter.getNextAction())
    {
	action->perform(g_);
    }

Thank You Sir David, For Investigating This :)

I Made This Thread, Reporting This Back In December
https://forum.hise.audio/topic/3375/execution-timed-out

Custom look and feel component ID

14

1.9k

10.7k

93.0k