Hello,

as I said above: you rebuild your UI after each EVMSG_CHANGE. Thus, you loose the focus of your UI elements (since they are destroyed and rebuilt).

You have to find a way to avoid that unnecessary rebuild of your layout after user interaction in your dialog.

best wishes,
Sebastian

Hello,

I tested it with the Gradient Shader example from the cinema4dsdk and it works fine as far as I can tell.

I just removed the check for ASSETDATA_FLAG::TEXTURESONLY:

Bool SDKGradientClass::Message(GeListNode* node, Int32 type, void* data)
{
  switch (type)
  {
  case MSG_GETALLASSETS:
  {
    AssetData* const assetData = static_cast<AssetData*>(data);
    // checks if only texture assets should be added
    if (assetData == nullptr)
      return true;
      
    BaseList2D* const baseList2D = static_cast<BaseList2D*>(node);
    if (baseList2D != nullptr)
    {
      // get the file name
      const Filename path = baseList2D->GetData().GetFilename(GRAD_FILE);
      // check if the file name is set
      if (path.IsPopulated())
      {
        // add the file name
        assetData->Add(path, nullptr);
      }
    }
    break;
  }
  }

  return SUPER::Message(node, type, data);
};

Regarding Shader hierarchies: I guess you can send the message to your child-shaders yourself, to make sure they receives the message.

best wishes,
Sebastian

Alternatively, you can check if the ENTER key way pressed and only update when this is the case (the user finished entering the string, see Interaction with Gadgets).

# get state of the "Enter" key.
state = c4d.BaseContainer()
res = c4d.gui.GetInputState(c4d.BFM_INPUT_KEYBOARD, c4d.KEY_ENTER, state)

if res:
  if state[c4d.BFM_INPUT_VALUE] != 1:
    return False

  idx = id - 100000

  newString = self.GetString(id)

  obj = self.objectsList[idx]
  if obj is not None:
      c4d.StopAllThreads()
      obj.SetName(newString)
      c4d.EventAdd()

This way, the dialog would behave similiar to the Attribute Manager.

best wishes,
Sebastian

Hello,

you have to call EventAdd() to inform Cinema that you have changed something.

But in your code, you call your Update() function after a EVMSG_CHANGE message. In your Update() function, you delete and rebuild your UI, thus you loose the focus on the current UI gadget.

You must find a way to either not call Update() after you edit the name of the object or to restore the focus on the newly created UI.

best wishes,
Sebastian

Hello,

any chance you could provide some example code to reproduce the issue? Without that, one can only guess what is wrong.

best wishes,
Sebastian

Hello,

as I said above, you have to handle user interaction in the dialog's Command() function. The function if called when the user interacts with the dialog's gadgets. Something like this:

def Command(self, id, msg):

    if id >= 100000 and id < 200000:
        idx = id - 100000

        newString = self.GetString(id)

        obj = self.objectsList[idx]
        if obj is not None:
            c4d.StopAllThreads()
            obj.SetName(newString)
            c4d.EventAdd()

        

    return c4d.gui.GeDialog.Command(self, id, msg)
    

best wishes,
Sebastian

Also, if you want to move a tag, you first have to remove it from the original object. So you don't insert, you change the position of the tag in the scene graph.

doc.StartUndo()

doc.AddUndo(c4d.UNDOTYPE_CHANGE, tag)

tag.Remove()
op.InsertTag(tag)

doc.EndUndo() 

Hello,

c4d.EventAdd() is always needed when one changes the active document in the context of some user interaction. This includes user interaction in a GeDialog (Core Messages Manual).

Also, don't forget to call c4d.StopAllThreads() when you edit the document asynchronously (BaseDocument Manual).

You should react to user interaction in your GeDialog's Command() function. Can you share the complete code of your Command() function?

best wishes,
Sebastian

Hello,

an undo-step has to start with StartUndo() and must end with EndUndo(). In between, you can add operations to that undo-step withAddUndo(). As @zipit has shown, the undo-operation for adding something to the document is c4d.UNDOTYPE_NEW.

doc.StartUndo()

ttag = c4d.TextureTag()
op.InsertTag(ttag)

doc.AddUndo(c4d.UNDOTYPE_NEW, ttag)
doc.EndUndo() 

See also Undo System Manual.

best wishes,
Sebastian

Hello,

without seeing your code or any error message it is impossible to give any advice.

But "works in viewport but not in rendering" sounds like you are using c4d.documents.GetActiveDocument() somewhere. See also BaseDocument Manual.

best wishes,
Sebastian