No idea why it does not work out of the box.
But you could implement NodeData::GetDParameter() to see if something weird happens there and to set the value yourself.
Edit: I just tested the scenario in R20 and with RoundedTube and everything seems to work fine.
I still don't get what data would be too complex to write into a BaseContainer.
You can store raw memory in a BaseContainer.
If you only want to read/write to the document's BaseContainer, you could listen to the MSG_DOCUMENTINFO sent when the document is loaded and saved.
@doppelgamer said in Avoiding invalidating saved scenes when implementing Read/Write:
The data that this SceneHook handles cannot be put into a container,
Why?
I guess my implementation of the Write() function is just not quite right.
I think it would make sense if you would show us your code here.
Read()/Write() operates on a HyperFile. You find some examples in the HyperFile Manual and NodeData::Read() / NodeData::Write() Manual
Isoparms are the fancy lines you see when you turn on "Isoparms" in the viewport display options.
I'm only aware of using SetIsoparm() in the context of a generator plugin, see Generating.
Shader creation requires inserting the shader using InsertShader().
MAXON_CREATOR_ID is used to get the ID stored in the internal GeMarker.
From what I can read, it seems that this ID is unique for each element in a given document.
See Unique ID and GeMarker Manual.
The issue is that a Python Generator cannot / does not implement GetContour(), which is supposed to be used to create splines, not GetVirtualObjects().
This was discussed just three months ago: Hide Layers
Like zipit said, SetLayerObject() is from a shared base class but supposed to be used on with thingy (object, tag, material):
op.SetLayerObject(None)
c4d.EventAdd()
actually it is also possible just to edit the "Layer" parameter:
op[c4d.ID_LAYER_LINK] = None
c4d.EventAdd()
Compare Layer Manual.
@C4DS said in Buggy GeDialog Local2Global and Local2Screen:
From this I gather no one ever used these methods.
There is an example of how to use a function in the documentation: GeDialog Manual.
Not sure if it is related to your issue.
What you describe sounds like a job for maxon::RWSpinlock.
But, FindNearest() and FindRange() are not const, these functions may actually mutate the internal data (you can look at the source in kdtree.cpp). So be sure to use the threadIndex arguments.
What do you want to learn by checking dirty?
A Shader Effector could use a "Noise" shader. In that Noise shader, you can enable "Animation Speed".
So the Shader effector will create a different result for every frame, even no parameter values change.
Example 1 is the initialization of a C-array from a brace-enclosed list.
Example 2 is the construction of a std::vector object using an initializer list.
So, does maxon::BaseArray has initializer list constructors or methods?
Looking at the API, it seems it does not have such a constructor, but methods handling std::initializer_list. So you can actually write:
maxon::BaseArray<maxon::Int> testArray;
testArray.Append({ 1,2,3 }) iferr_return;
Instead of using a plane, you could place your sun and moon texture on a Sky object.
Then you can disable "Affect Background" on the environment object.
But how is this a programming related question?
The user area has to be a member variable of the GeDialog class:
class ExampleDialog(c4d.gui.GeDialog):
# The GeUserArea need to be stored somewhere, we will need this instance to be attached to the current Layout
geUserArea = ExampleGeUserArea()
You can simply edit the MATERIAL_TRANSPARENCY_COLOR parameter.
Mat[c4d.MATERIAL_TRANSPARENCY_COLOR]
The parameter stores a c4d.Vector.
You find examples on how to handle materials on GitHub.
Can you access the color using GeUserArea::GetColorRGB()?
All this stuff was changed with R20.
You only have to care about domain spaces if you want to register MAXON API stuff.
For old plugin IDs, you don't have to care about anything. You can enter any label you like. This is just for you.
The line
obj = object()
is useless.
And to handle editor and render visibility, can can use dedicated functions: GetEditorMode(), GetRenderMode(), etc. and the explicit values c4d.MODE_ON, c4d.MODE_OFF, and c4d.MODE_UNDEF.
See also the C++ docs: BaseObject Manual