I see. As long as it is an acknowledged behavior. Because on surface it looks like a bug of the sneaky variety.
I tried the exact same code in 4.2.2 LTS, and got only one printout per operator call. This would mean the second printout in 4.4 is related to new changes to how how overriding __init__ now…
i tried the suggested __init__ in the form of
def __init__(self, *args, **kwargs):
super().__init__(*args, **kwargs)
print('creating operator')```
and is…i see. will the error and it's cause at least be acknowledged in docs?
Aaaaah my bad, I did not update the documentation (and release notes) yet :(
Will do tomorrow, but in a nutshell, Blender now requires that you call the parent class'
__init__and/or…
Confirmed - the file above doesn't have the script but you can recreate it using the "Operator Simple" template and add your own
__init__method. This worked until relatively recently.
that'…
I'm not sure why the second example throws (note that it doesn't in 3.6).
The second example now throwing is the reason for this report. I just wasn't unclear which blender version does it…
My understanding is the property
obj.propnameuses the custom propobj['propname']as the low-level store for its data. The custom prop does not know about the higher-level property;…
The first access exception is both expected and not. The syntax for defining properties has an optional argument of default.
If it's not set, then yes, an exception when property is access…
Outside of python scripts that process object transforms before depsgraph update, the part of blender that relies on those matrices not being degenerate is bpy.ops.object.add_named() used to…
@HooglyBoogly This may have caused this error (pic below), I fixed it in
39f3ea4ab0
[c0f374ec3e3](https…
while that does address issue for new objects. it doesn't address issue of objects loaded from blend files via python to have default matrices prior update (reported by first comment), which…
I can confirm that git bisect shows that 1c0f374ec3e3 is the first bad commit.
so what I understood from commit's description is that blender no longer updates object matrices outside of…
here is a video of the crash using daily 4.0.3. the crash happens on second redo, when the panel is brought up via hotkey (F9).