That kind of refactoring should be done for the file as a whole, doing it for individual places just makes things more messy.
This is existing code that was moved, not the place here to start refactoring that.
This is existing code that was moved, not the place here to start refactoring that.
It should be kept, it's part of previously uncommented code that may still get used again.
I don't see this in our C/C++ guidelines, does not make sense to me either.
I would not expect changes like this to an existing file to start using newer conventions. That kind of refactoring can be done separately.
I would not expect changes like this to an existing file to start using newer conventions. That kind of refactoring can be done separately.
No, I think it's better to keep the API consistent and always put ParamHandle first.
If it's considered ready, I'll remove the WIP prefix.
For live unwrap there is a trade-off. If it starts from scratch after every mouse motion, it will give the same results as regular unwrap,…
@lichtwerk is actually responsible for LTS maintenance. I guess he can decide if it's worth backporting, or get advice from another dev.
I'm on sabbatical at the moment, I'll CC @bartvdbraak @ThomasDinges @lichtwerk for devops/release related things instead.
Maybe something else needed in the yaml config file, maybe something…
I think most users downloading zip files are not doing it to get a portable Blender in this sense. On macOS and Linux there also is no clear distinction between installer and zip, so it would be a…
BF_DIST_BIN to be a symlink
This looks good to me, but please ask someone else to review as I'm on sabbatical until the end of the year.