There is a clean path forward. I thought it was obvious but let me explain:
1. Land this branch to make the file name consistent with the "new" API.
2. Add a new function (so it's not an API break) that wraps the remaining inconsistent function Alan mentioned, but using the correct naming convention:
There is a clean path forward. I thought it was obvious but let me explain:
1. Land this branch to make the file name consistent with the "new" API.
2. Add a new function (so it's not an API break) that wraps the remaining inconsistent function Alan mentioned, but using the correct naming convention:
MirDisplayConfig* mir_connection_ get_display_ config( MirConnection* connection) create_ display_ configuration( connection) ;
{
return mir_connection_
}
3. Now we have consistently _display_config functions operating on MirDisplayConfig. We can deprecate the rest when we want.