You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here are the difficulties Dplug users have reported 04/10/2024:
identifier nextBuffer dislike, would expect processBuffer (process? processBlock?)
have never read the code of UIElement, relying on DDoc on arsd instead => now rewritten to be nicer to read
difficulties with struct and the fact they are copied not reference types. eg. in a foreach => that's a dlang issue
believe they can't allocate, or that they can allocate with reallocBuffer in audio thread. In reality we can with Vec since capacity maxing, but not reallocBuffer. Clarify.
doesn't manage to find mouse release, the way to do it is starting a drag operation and catch onStopDrag => DDoc
miss nothrow @nogc in class/struct, then create closures using stdlib => make nothrow @nogc a bit more systematic in examples
do not know about debugLogf
general difficulty to debug or profile => looked at the new user procedure more
do not always know build types of DUB => would need a DUB introduction?
The text was updated successfully, but these errors were encountered:
Here are the difficulties Dplug users have reported 04/10/2024:
UIElement
, relying on DDoc on arsd instead => now rewritten to be nicer to readnothrow @nogc
in class/struct, then create closures using stdlib => make nothrow @nogc a bit more systematic in examplesThe text was updated successfully, but these errors were encountered: