Initial Grease Pencil 3.0 stage #106848

Merged
Falk David merged 224 commits from filedescriptor/blender:grease-pencil-v3 into main 2023-05-30 11:14:22 +02:00
1 changed files with 3 additions and 2 deletions
Showing only changes of commit 7c4c8868d1 - Show all commits

View File

@ -39,11 +39,12 @@ class TreeNode : public ::GreasePencilLayerTreeNode {
this->type = type;

Is there a particular reason you remove copy assignment but keep copy construction defined?

Is there a particular reason you remove copy assignment but keep copy construction defined?

Just because copying should be explicit. And removing the copy assignment constructor avoids errors.

Just because copying should be explicit. And removing the copy assignment constructor avoids errors.
this->name = BLI_strdup(name.c_str());
}
TreeNode(const TreeNode &other)
TreeNode(const TreeNode &other) : children_(other.children_)
{
this->type = other.type;
this->name = BLI_strdup(other.name);
}
TreeNode(TreeNode &&other)
TreeNode(TreeNode &&other) : children_(std::move(other.children_))
{
this->name = other.name;
other.name = nullptr;

Is defining these as constexpr helpful? I sort of doubt any real computation is done on these nodes at compile time. But maybe?

Is defining these as `constexpr` helpful? I sort of doubt any real computation is done on these nodes at compile time. But maybe?

The const in the const bool return type means nothing here

The `const` in the `const bool` return type means nothing here