Open WLCIssuesBot opened 7 years ago
Comment by Drakulix
Friday Nov 25, 2016 at 09:36 GMT
Another inconvenience: output_context_destroyed
might be called after output_destroyed
.
Comment by Enerccio
Friday Apr 07, 2017 at 18:41 GMT
I can confirm first bug.
Second one is correct behavior, I think?
At least when running wlc with the x11-backend
output_resolution_cb
gets called before theoutput_created_cb
for the new output.This is not only highly confusing, but may cause crashes if the
output_resolution_cb
might depend on someuserdata
being initialized. For easy use of userdata pointersoutput_created
should be the first emited callback andoutput_destroyed
the very last. (view_created
andview_destroyed
alike.) This is the only exception to this unwritten rule I have encounted so far and would like to know, if this is expected.