LookandFeel not responding properly to mouse interactions

[Dan Korneff]

@d-healey I haven't tried standalone.

[Dan Korneff]

Standalone is unaffected.

[d.healey]

@Dan-Korneff Which DAWs have you tested? And which OS?

[Dan Korneff]

@d-healey Reaper/Cubase/ProTools pc/mac

[Christoph Hart]

In the interface designer I get glitchy behaviour when scrolling with both knobs.

That's because the scroll bars of the viewport of the interface designer is fighting against the scroll behaviour of the sliders and something we have to live with when putting a usable interface into a scrollable workspace.

Reaper/Cubase/ProTools pc/mac

I just tested your snippet in Cubase / Ableton / REAPER / FL Studio on Windows and it works there perfectly. Does it happen with the snippet too on your end or just with your actual plugin?

Or is there anything else particular to your setup that might cause this - especially something common to both your PC / Mac test systems? It would be a very obvious bug for anybody that uses LAF sliders.

[Dan Korneff]

@Christoph-Hart ugh... your right. The snip works fine. Gonna narrow down the combination now.

[Dan Korneff]

@Christoph-Hart Here's a minimum script:

HiseSnippet 1940.3ocsXrsaabikiSlh0ZWWzVzO.BgV.oTY4YjkcLpQPhutUquID4zKvHHK0LTRrhC4f4hc71lOj1+j8oc+Z1m6eP2C4bQbjjacMZzCRhm67bg7bX+HoGMNVFgrpc4sgTj0eydvshjIGLgvDndGhr9H6ClH8jbRBEeFiOEs+sgj3XpOxx5Q+cEUVq9Xj9yu778IbhviNCDB80RlG8TV.KYFz9u3DFmeLwmdIKvf5tunmmTbfjKSAK5Q1NnPh2TxX54DEYqXi9JR7Dj0SroC6RdZms82ryNa4r4lDGmcb8FRbd5NC21YmNaSF5Mzk10AY8AG4yRjQCRfMPLx5w6K8ucvD4MhLE70rX1PNUsvEM.zbF3ikbe0VTAEcvDF2uegqJFARo+LG2ixbbep8YLeVIbSGnBAdFGlNPqUpZdOph44ZZdNFl2RLIKCS5wYlzGaOvKhElLCixd9q18DIznQDHNYZJYzhVwYMaHHDmfIggeCyOYB9Y3scb1sVIzuhxFOIo.7ARPbhj1AjoziifEkhuQgDZMiql6Vql.hlwPjkhYhvzjKRgutLhErVseXsZqtwFO6O0OZQhO8hKNAu24GhO9niN88iVxUjzivwmt2wvxLOFW5weCmLBbXE9JuHJDu0jdpTNcOg+wTJuQycKECd.m4SihgUE72NhNlEC91iSEdILonQc+HxMuTlPhtMi75sviJPNtEVN76aBBP4UwvmqIQ3SVvJ5SRljo4BZBcuGDEQDio.cfNfP+awqm8OlnfHCZiAKL4hQihoprlNs2xTPjHuKmv7lJfTT.qSa24vVjD511AzRG36mTgoBxKUYnaaONkDU5OWUIIpvuzDV2zh9hbYZB6I5cy0DdJ8bYT.gy9WTeS6BPAxod8J1Zt6f.tLS32bGvijoBekCwDnZmRtZyWa3FWcbavlxNVrQ1OwsuYBCNwHPNkVtKYivMT5INczH1awOCruOudSrJ7aZ2ozKkGxhC4jayMLMPXO6B0ylD6S8XvduOGpU0wFM12go7X58Ur+lBbNqE6uec7ywt3urPUFwuLUPeqJ9cjXLSPa6KSgCGuTNHIhIF2npQzpp1ZBw4Ypa2L2pp9YONarf5qjbiRczBeE4JmW2RGJVmbUG8e6jC.9otGTbDQ8qWVTXFjTJZ33rEkD.okDe+8h7ZbUkb9MvcZgWJjrL+unBx6DAXTqWIGtkpRCNusLMRWaCEx6A4gfSDrmwzj8UIgwMJxOg8XycmOmagsStqSepPnaqRo1BaHm4JSyX7j269.SWv5vwIN6.dhxh+l6BNCvNVh+3j+HtCn3KHaYmE7Hmb+bHXMiF0sSjWSiv+3Op4wiCjQ8apKyVP8IPNZQ7X0hJrGpITTlUTk5whfyOeIwmkFabzUF6Ns6tKFtfZO+uOEtbKYBEtJPSIIFKnTnsoED0ATUKAe6bxZipG7YR52c2jd2AB2lZCa.D28z.vIR7Pn3eZIqif1NOhyYgwzFWU01Vux1t0blyxwl6hdhJUcdHu13fgHop8tFkIgvoKys6ZM+180244Jlg9JarWpRco9uj5k.2Mygc3bxL+NZyXoS2Ez7RnZqpDkw4NsVftNaAEfNZy5cy5kompIObVCd4sDoh25d+TPMZ1.Na3DgbXi5kHgNZbJjYAUf+.ZoMjFkvnwPKmA+iAWbdUdzUM0CX99bZeYLS0QT8uTY1sx8Y0gNoBG.WqqA6VBF5fAfrNbUnAsPCN.P2JrquGAfpu0pDLDHBhgqiB6E.ysnP+J3tRe5HRJOAGOEjdIsbl.pvuTpnZFzaTmqo01LkMQ267b.SjRdBKTwsQwXl2lSulxwikv0hfiFpCTnB4oiW2z.Xw8APLQeRDzRNjnqzPI1vp3Tyfoz0rv4LAkFSekvWdFQ.a5pRIP5qY6P3x3gTdcybixHlJjtP2vE88pndsZuqnwVrTbtLgdgnQyZ+.b946pgmG0nQKEmJ+IRx4znkhVMKZzuEiMDoACoQsxZEojPXdqpCwYe2CwYNioWV5rAgRQOAK4hPp3tl7DkWCnF3K2p.RSzi68g4i6kMJ.h4ql0qzEizFc9r1+yQi9e+Gzq5cHIgTHJPpypp.XGRuFlbOaRxUsOjFOMQFpoMHTJT1f0mduT7aAOhkZ79aK9S05RyWKnnnTA6m+I0m+8yCLeigu6+B0hyV9YuHqNDjrMTGhTYaYlqNaCoKl..efetBxpjLgjWFgr1v9OTYDZgpGkTsxk5RJdTOtxrhGT0ZlJ7VDv6AdxOY16und9kCGzGEVH0d9YiyW3oMZJQortcbccgu5toAFk2YyM2Zqt.TzhuYvGYelzOEzV0mvP8PO4HTQLy2MPMtu.hj2Z9PP+o8tF2WS7is6yR7lrbabkkXiPZ+6CaL+0fVy9nQifKhmYfO193u88yS+ffK9SfLzyHv8NpJgySCF.QZOJncg.FVSU2sh5vir0NE0gCfNRzK9U3SNRW0ZqbjtEHQADuH4a7xNxQ8dS+EMDvlD5T6UsOSsF6V4bFTd0N6MddUE0BL14gx3lOTF69PYbqGJia+PY7oOTF242mQ0qStWZhLHqrAgNq+Q56ErrNRPfLPc1J5+C3jSIoG

[Dan Korneff]

@Christoph-Hart the culprit is "isPluginParameter": 1

[Christoph Hart]

Damn

I hate the day I decided to touch the plugin parameter stuff why are you like this?

[Dan Korneff]

@Christoph-Hart me too
But probably not nearly as much as you.

[Christoph Hart]

@Dan-Korneff Alright, that's fixed now. The culprit was indeed the change gesture callback that I've implemented a few months ago, which I hoped makes the plugin parameter behaviour more smooth but all it did so far was introduce new bugs.

I had to deactivate the change gesture for parameter changes caused by the mouse wheel and now it works pretty well. If I hammer the mouse wheel and look for glitches there is still a little bit left, but I think that is as good as we can get without removing the entire gesture stuff again.

For the double click glitch I had to introduce an artificial delay of 100ms before the default value is send as plugin parameter because the on/off clicking of the mouse sends multiple begin / change gesture callbacks which irritates the host so much that it can't process the incoming default value without taking a break.

100ms is enough for me in my tests without feeling sluggish, but let me know if there are still glitches happening on the double click event.

[Dan Korneff]

@Christoph-Hart Performance is acceptable here. Thanks!