Geraint

OK - can the length query be a separate method (rather than calling stuff with `NULL`)? ```cpp // Expected length of the URI. For compatibility, this should not exceed 2000...

So if the host provides a buffer that's too small, should the plugin return the size we _wants_ the URI, not the actual size it's returning?

OK - and should `uri` be allowed to be null? We could demand that it's always not null, but allow a capacity of 0 for a length query. This would...

OK, got it! A null `uri` is unexpected enough (for me) that I've add a note in the comments, but otherwise the API should match what you were suggesting.

@abique I've added a comment saying that if `get_uri()` returns a `file:` URI, the host is allowed to rewrite the URL to some other scheme/prefix, as long as the filename...

@abique I've added a comment saying that if `get_uri()` returns a `file:` URI, the host is allowed to rewrite the URL to some other scheme/prefix, as long as the filename...

This is awesome, thanks so much. I don't know if you saw, but WCLAPs got a small shout-out in one of the ADC'25 talk proposals (about the future of audio...

Shouldn't this be handled by calling [`set_scale()`](https://github.com/free-audio/clap/blob/69a69252fdd6ac1d06e246d9a04c0a89d9607a17/include/clap/ext/gui.h#L136-L147) again, when the window API changes the underlying resolution of its canvas/whatever? APIs like Cocoa shouldn't use `.set_scale()` anyway (since they work in...

Vote to close, since if hosts aren't calling `.set_scale()`, that's not a CLAP standard issue?

Might be just because of my Stretch stuff (which has separate "input latency" and "output latency"), but I think this could be explained neatly as the latency being equivalent to...