Dear community,

We recently got a non-public support request about handling drag and drop events for a custom image control in a dialog. And while we have shown this, drag event handling, multiple times before, I thought it does not hurt to answer this publicly, as this very case - an image control - is quite common, and it does not hurt having a bit more verbose public example for it.

edit: I have updated this topic with new code and a new video, to also handle outgoing asset drag events, and talk a bit about the pros and cons of different approaches, and what you could do when not implementing a code example as I did here, and therefore have a bit more leverage room when it comes to complexity.

In general, doing all this is possible. It is just that not everything is a ready-made solution for you, where you just call a function. At some point you have to "swim" here yourself, as we cannot write your code for you, but I hope the example helps shedding some light on the probably uncessarily complicated drag handling in Cinema 4D.

Cheers,
Ferdinand

Result

Code

"""Provides an example for implementing a custom control that can generate and receive drag events.

The example implements a dialog which holds multiple "cards" (BitmapCard) that display an image
and can receive drag events. The user can drag images from the file system into these cards (file
paths) or drag texture assets from the Asset Browser into these cards. The cards can also generate
drag events themselves, e.g., when the user drags from a card, it will generate a drag event. 
Showcased (selectable via the combo box in the menu of the dialog) are three drag types:

1. File paths: Dragging a card will generate an image file path drag event, which for example could 
   be dragged into a file path field of a shader, onto an object in the viewport, or onto other 
   BitmapCard controls. The advantage of this approach is that we do not have to create
   materials or assets, but can just use the file path directly.

2. Materials: Dragging a card will generate an atom drag event, here populated with a Redshift
   material that has the texture of the card as an input. This material can then be dragged onto
   anything that accepts materials, like objects in the viewport. The disadvantage of this
   approach is that we have to create a material, and that we have to exactly define how the 
   material is constructed.

3. Assets: Dragging a card will generate an asset drag event, here populated with a texture asset
   that has the texture of the card as an input. This asset can then be dragged onto anything that
   texture accepts assets, such as an object in the viewport. The disadvantage of this
   approach is that we have to create an asset.

   - The example also showcases a variation oof this approach, where we exploit a bit how the
     texture asset drag handling works, to avoid having to create an asset.


Overview:

- BitmapCard: A user area control that can receive drag events and generate drag events itself. Here
              you will find almost all the relevant code for drag and drop handling
- BitmapStackDialog: A dialog that holds multiple BitmapCard controls and allows the user to select
                the drag type via a combo box. This dialog is the main entry point of the example
                but does not contain much relevant code itself.
"""
__author__ = "Ferdinand Hoppe"
__copyright__ = "Copyright 2025 Maxon Computer GmbH"

import os
import re

import c4d
import maxon
import mxutils

# The file types that are supported to be dragged into a BitmapCard control.
DRAG_IN_FILE_TYPES: list[str] = [".png", ".jpg", ".jpeg", ".tif"]

# A regex to check of a string (which is meant to be a path/url) already as a scheme (like file:///
# or http:///). The protocol we are mostly checking for is "asset:///", but we keep this regex generic
# to allow for other schemes as well.
RE_URL_HAS_SCHEME = re.compile("^[a-zA-Z][a-zA-Z\d+\-.]*:\/\/\/")

# A non-public core message which need when we want to properly generate asset drag events.
COREMSG_SETCOMMANDEDITMODE: int = 300001000


class BitmapCard(c4d.gui.GeUserArea):
    """Implements a control that can receive bitmap path drag events and generates drag events itself.
    """

    def __init__(self, host: "BitmapStackDialog") -> None:
        """Constructs a new BitmapCard object.
        """
        # The host dialog that holds this card. This is used to access the drag type selected in the
        # combo box of the dialog.
        self._host: BitmapStackDialog = host

        # The image file path and the bitmap that is displayed in this card.
        self._path: str | None = ""
        self._bitmap: c4d.bitmaps.BaseBitmap | None = None

    def GetMinSize(self) -> tuple[int, int]:
        """Called by Cinema 4d to evaluate the minimum size of the user area.
        """
        return 250, 100

    def DrawMsg(self, x1, y1, x2, y2, msg_ref):
        """Called by Cinema 4D to let the user area draw itself.
        """
        self.OffScreenOn()
        self.SetClippingRegion(x1, y1, x2, y2)

        # Draw the background and then the bitmap if it exists. In the real world, we would have to
        # either adapt #GetMinSize to the size of the bitmap, or draw the bitmap in a way that it
        # fits into the user area, e.g., by scaling it down. Here we just draw it at a fixed size.
        self.DrawSetPen(c4d.gui.GetGuiWorldColor(c4d.COLOR_BGGADGET))
        self.DrawRectangle(x1, y1, x2, y2)
        if self._bitmap:
            w, h = self._bitmap.GetSize()
            self.DrawBitmap(self._bitmap, 5, 5, 240, 90, 0,
                            0, w, h, c4d.BMP_NORMALSCALED)

    def Message(self, msg: c4d.BaseContainer, result: c4d.BaseContainer) -> int:
        """Called by Cinema 4D to handle messages sent to the user area.

        Here we implement receiving drag events when the user drags something onto this user area.
        """
        # A drag event is coming in.
        if msg.GetId() == c4d.BFM_DRAGRECEIVE:
            # Get out when the drag event has been discarded.
            if msg.GetInt32(c4d.BFM_DRAG_LOST) or msg.GetInt32(c4d.BFM_DRAG_ESC):
                return self.SetDragDestination(c4d.MOUSE_FORBIDDEN)

            # Get out when this is not a drag type we support (we just support images). Note that we
            # cannot make up drag types ourselves, so when we want to send/receive complex data, we
            # must use the DRAGTYPE_ATOMARRAY type and pack our data into a BaseContainer attached
            # to the nodes we drag/send.
            data: dict = self.GetDragObject(msg)
            dragType: int = data.get("type", 0)
            if dragType not in [c4d.DRAGTYPE_FILENAME_IMAGE, maxon.DRAGTYPE_ASSET]:
                return self.SetDragDestination(c4d.MOUSE_FORBIDDEN)

            # Here we could optionally check the drag event hitting some target area.
            # yPos: float = self.GetDragPosition(msg).get('y', 0.0)
            # if not 0 < yPos < 50 or not self.CheckDropArea(msg, True, True):
            #     return self.SetDragDestination(c4d.MOUSE_FORBIDDEN)

            # After this point, we are dealing with a valid drag event.

            # The drag is still going on, we just set the mouse cursor to indicate that we are
            # ready to receive the drag event.
            if msg.GetInt32(c4d.BFM_DRAG_FINISHED) == 0:
                return self.SetDragDestination(c4d.MOUSE_MOVE)
            # The drag event is finished, we can now process the data.
            else:
                # Unpack a file being dragged directly.
                path: str | None = None
                if dragType == c4d.DRAGTYPE_FILENAME_IMAGE:
                    path = data.get("object", None)
                # Unpack an asset being dragged.
                elif dragType == maxon.DRAGTYPE_ASSET:
                    array: maxon.DragAndDropDataAssetArray = data.get(
                        "object", None)
                    descriptions: tuple[tuple[maxon.AssetDescription, maxon.Url, maxon.String]] = (
                        array.GetAssetDescriptions())
                    if not descriptions:
                        # Invalid asset but we are not in an error state.
                        return True

                    # Check that we are dealing with an image asset.
                    asset: maxon.AssetDescription = descriptions[0][0]
                    metadata: maxon.BaseContainer = asset.GetMetaData()
                    subType: maxon.Id = metadata.Get(
                        maxon.ASSETMETADATA.SubType, maxon.Id())
                    if (subType != maxon.ASSETMETADATA.SubType_ENUM_MediaImage):
                        # Invalid asset but we are not in an error state.
                        return True

                    path = str(maxon.AssetInterface.GetAssetUrl(asset, True))

                if not isinstance(path, str):
                    return False  # Critical failure.

                if (dragType == c4d.DRAGTYPE_FILENAME_IMAGE and
                    (not os.path.exists(path) or
                     os.path.splitext(path)[1].lower() not in DRAG_IN_FILE_TYPES)):
                    # Invalid file type but we are not in an error state.
                    return True

                self._path = path
                self._bitmap = c4d.bitmaps.BaseBitmap()
                if self._bitmap.InitWith(path)[0] != c4d.IMAGERESULT_OK:
                    return False  # Critical failure.

                self.Redraw()  # Redraw the user area to show the new bitmap.

                return True

        # Process other messages, doing this is very important, as we otherwise break the
        # message chain.
        return c4d.gui.GeUserArea.Message(self, msg, result)

    def InputEvent(self, msg: c4d.BaseContainer) -> bool:
        """Called by Cinema 4D when the user area receives input events.

        Here we implement creating drag events when the user drags from this user area. The type of
        drag event which is initiated is determined by the drag type selected in the combo box
        of the dialog.
        """
        # When this is not a left mouse button event on this user area, we just get out without
        # consuming the event (by returning False).
        if (msg.GetInt32(c4d.BFM_INPUT_DEVICE) != c4d.BFM_INPUT_MOUSE or
                msg.GetInt32(c4d.BFM_INPUT_CHANNEL) != c4d.BFM_INPUT_MOUSELEFT):
            return False

        # Get the type of drag event that should be generated, and handle it.
        dragType: int = self._host.GetInt32(self._host.ID_DRAG_TYPE)
        return self.HandleDragEvent(msg, dragType)
    
    # --- Custom drag handling methods -------------------------------------------------------------

    # I have split up thing into three methods for readability, this all could also be done directly
    # in the InputEvent method.

    def HandleDragEvent(self, event: c4d.BaseContainer, dragType: int) -> bool:
        """Handles starting a drag event by generating the drag data and sending it to the system.

        This is called when the user starts dragging from this user area.
        """
        # This requires us to modify the document, so we must be on the main thread (technically
        # not true when the type is DRAGTYPE_FILENAME_IMAGE, but that would be for you to optimize).
        if not c4d.threading.GeIsMainThread():
            raise False

        # Generate our drag data, either a file path, a material, or an asset.
        doc: c4d.documents.BaseDocument = c4d.documents.GetActiveDocument()
        data: object = self.GenerateDragData(doc, dragType)

        # Now we set off the drag event. When we are dragging assets, we have to sandwich the event
        # in these core message calls, as otherwise the palette edit mode toggling will not work
        # correctly.
        if dragType == maxon.DRAGTYPE_ASSET:
            bc: c4d.BaseContainer = c4d.BaseContainer(
                COREMSG_SETCOMMANDEDITMODE)
            bc.SetInt32(1, True)
            c4d.SendCoreMessage(c4d.COREMSG_CINEMA, bc, 0)

        # When #HandleMouseDrag returns #False, this means that the user has cancelled the drag
        # event, one case could be that the user actually did not intend to drag, but just
        # clicked on the user area.
        #
        # In this case we remove the drag data we generated, as it is not needed anymore. Note that
        # this will NOT catch the case that the drag event is cancelled by the recipient, e.g., the
        # user drags a material onto something that does not accept materials.
        if not self.HandleMouseDrag(event, dragType, data, 0):
            self.RemoveDragData(doc, data)
            return True

        # Other half of the sandwich, we toggle the palette edit mode back to normal.
        if dragType == maxon.DRAGTYPE_ASSET:
            bc: c4d.BaseContainer = c4d.BaseContainer(
                COREMSG_SETCOMMANDEDITMODE)
            bc.SetInt32(1, False)
            c4d.SendCoreMessage(c4d.COREMSG_CINEMA, bc, 0)

        return True

    def GenerateDragData(self, doc: c4d.documents.BaseDocument, dragType
                         ) -> str | c4d.BaseMaterial | maxon.DragAndDropDataAssetArray:
        """Generates the drag data for the given drag type.

        Each tile just encapsulates a file path, but we realize dragging them as file paths,
        materials, or assets. So, when the type is material or asset, the drag data must be
        generated from the file path. Which is why we have this method here.
        """
        if not c4d.threading.GeIsMainThread():
            raise RuntimeError(
                "GenerateDragData must be called from the main thread.")

        # The user has selected "File" as the drag type, we just return the file path.
        if dragType == c4d.DRAGTYPE_FILENAME_IMAGE:
            return self._path
        # The user has selected "Material" as the drag type, we create a Redshift material with the
        # texture as input and return that material.
        elif dragType == c4d.DRAGTYPE_ATOMARRAY:
            material: c4d.BaseMaterial = mxutils.CheckType(
                c4d.BaseMaterial(c4d.Mmaterial))

            # Create a simple graph using that texture, and insert the material into the
            # active document.
            maxon.GraphDescription.ApplyDescription(
                maxon.GraphDescription.GetGraph(
                    material, maxon.NodeSpaceIdentifiers.RedshiftMaterial),
                {
                    "$type": "Output",
                    "Surface": {
                        "$type": "Standard Material",
                        "Base/Color": {
                            "$type": "Texture",
                            # Set the texture. When our source is a file we will just have a plain
                            # path, e.g. "C:/path/to/file.png" and we have to prefix with a scheme
                            # (file) to make it a valid URL. When we are dealing with an asset, the
                            # texture path will already be a valid URL in the "asset:///" scheme.
                            "Image/Filename/Path": (maxon.Url(f"{self._path}")
                                                    if RE_URL_HAS_SCHEME.match(self._path) else
                                                    maxon.Url(f"file:///{self._path}"))
                        }
                    }
                })
            doc.InsertMaterial(material)
            return [material]
        # The user has selected "Asset" as the drag type, we create a texture asset and return that.
        elif dragType == maxon.DRAGTYPE_ASSET:
            # So we have to cases here, either that we want truly want to generate an asset drag
            # event or that we just want to piggy-back onto the texture asset drag and drop
            # mechanism of Cinema 4D, which is what we do here.

            # Code for truly generating an asset drag event, where we would store the asset in the
            # scene repository.
            generateAssets: bool = False
            if generateAssets:
                # Get the scene repository and create an asset storage structure for the asset.
                repo: maxon.AssetRepository = doc.GetSceneRepository(True)
                store: maxon.StoreAssetStruct = maxon.StoreAssetStruct(
                    maxon.Id(), repo, repo)

                # Now save the texture asset to the repository.
                url: maxon.Url = maxon.Url(self._path)
                name: str = url.GetName()
                asset, _ = maxon.AssetCreationInterface.SaveTextureAsset(
                    url, name, store, (), True)

                # Create a drag array for that asset. It is important that we use the URL of the
                # asset (maxon.AssetInterface.GetAssetUrl) and not #url or asset.GetUrl(), as both
                # are physical file paths, and will then cause the drag and drop handling to use
                # these physical files, including the popup asking for wether the file should be
                # copied. We will exploit exactly this behavior in the second case.
                dragArray: maxon.DragAndDropDataAssetArray = maxon.DragAndDropDataAssetArray()
                dragArray.SetLookupRepository(repo)
                dragArray.SetAssetDescriptions((
                    (asset, maxon.AssetInterface.GetAssetUrl(asset, True), maxon.String(name)),
                ))

                return dragArray
            # With this case we can piggy-back onto the existing drag and drop texture asset
            # handling of Cinema 4D, without actually having to create an asset. THIS IS A
            # WORKAROUND, we could decide at any moment to change how the drag and drop
            # handling of assets works, possibly rendering this approach obsolete.
            else:
                # The slight disadvantage of this approach (besides it being a hack and us possibly
                # removing it at some point) is that we have to pay the download cost of
                # #self._host._dummyAssetId once. I.e., the user has to download that texture once
                # either by using it in the Asset Browser or by running this code. Once the asset has
                # been cached, this will not happen again.
                #
                # But since we search below in a 'whoever comes first' manner, what is the first
                # texture asset could change, and this could then be an asset which has not been
                # downloaded yet. So, in a more robust world we would pick a fixed asset below. But
                # this comes then with the burden of maintenance, as we could remove one of the
                # builtin texture assets at any time. So, the super advanced solution would be to
                # ship the plugin with its own asset database, and mount and use that. Here we could
                # use a hard-coded asset ID, and would have to have never pay download costs, as
                # the repository would be local.

                # Find the asset by its Id, which we have stored in the dialog.
                repo: maxon.AssetRepositoryInterface = maxon.AssetInterface.GetUserPrefsRepository()
                dummy: maxon.AssetDescription = repo.FindLatestAsset(
                    maxon.AssetTypes.File().GetId(), self._host._dummyAssetId, maxon.Id(),
                    maxon.ASSET_FIND_MODE.LATEST)

                # Setup the drag array with the asset. Note that #asset must be a valid texture
                # asset, so just passing maxon.AssetDescription() will not work. But the backend
                # for drag and drop handling will actually ignore the asset except for type checking
                # it, and use the URL we provided instead.
                dragArray: maxon.DragAndDropDataAssetArray = maxon.DragAndDropDataAssetArray()
                dragArray.SetLookupRepository(repo)
                dragArray.SetAssetDescriptions((
                    (dummy, maxon.Url(self._path), maxon.String(os.path.basename(self._path))),
                ))
            return dragArray
        else:
            raise ValueError(f"Unsupported drag type: {dragType}")

    def RemoveDragData(self, doc: c4d.documents.BaseDocument,
                       data: str | list[c4d.BaseMaterial] | maxon.DragAndDropDataAssetArray) -> bool:
        """Removes generated content when the user cancels a drag event.

        Sometimes the user starts a drag event, but then cancels it, e.g., by pressing the
        escape key. In this case, we have to remove the generated content, e.g., the material or
        asset that we created for the drag event.
        """
        if not c4d.threading.GeIsMainThread():
            return False

        if isinstance(data, list):
            # Remove the dragged materials from the document. Since we are always generating a new
            # material, we can just remove them. That is in general probably not the best design,
            # and a real world application should avoid duplicating materials.
            for item in data:
                if isinstance(item, c4d.BaseList2D):
                    item.Remove()
        elif isinstance(data, str):
            # Here we could technically remove a file.
            pass
        elif isinstance(data, maxon.DragAndDropDataAssetArray):
            # We could remove the asset, but other than for the material, there is no guarantee
            # that we are the only user of it, as the Asset API has a duplicate preventing
            # mechanism. So, the #SaveTextureAsset call above could have returned an already
            # existing asset. Since we could operate with a document bound repository, we could
            # search the whole document for asset references and only when we find none, remove
            # the asset.
            #
            # We use here the little hack that we actually do not create an asset, to just to piggy-
            # back onto the material drag and drop mechanism of assets, so we can just ignore
            # this case.
            pass

        return True


class BitmapStackDialog(c4d.gui.GeDialog):
    """Implements a a simple dialog that stacks multiple BitmapCard controls.
    """
    ID_DRAG_TYPE: int = 1002

    def __init__(self):
        """Constructs a new ExampleDialog object.
        """
        # The user area controls that will generate and receive drag events.
        self._cards: list[BitmapCard] = [
            BitmapCard(host=self) for _ in range(4)]

        # The id for the dummy asset that used to generate 'fake' texture asset drag events. We
        # search for it here once, so that we do not have to do it in the __init__ of each
        # BitmapCard, or even worse, in the HandleDragEvent of each BitmapCard.

        # We could technically also store here the AssetDescription instead of the Id, but that
        # reference can go stale, so we just store the Id and then grab with it the asset when we
        # need it. Which is much faster than searching asset broadly as we do here. In the end, we
        # could probably also do all this in the drag handling of the BitmapCard, but a little bit
        # of optimization does not hurt.
        self._dummyAssetId: maxon.Id | None = None
        if not maxon.AssetDataBasesInterface.WaitForDatabaseLoading():
            raise RuntimeError("Could not initialize the asset databases.")

        def findTexture(asset: maxon.AssetDescription) -> bool:
            """Finds the first texture asset in the user preferences repository.
            """
            # When this is not a texture asset, we just continue searching.
            meta: maxon.AssetMetaData = asset.GetMetaData()
            if (meta.Get(maxon.ASSETMETADATA.SubType, maxon.Id()) !=
                    maxon.ASSETMETADATA.SubType_ENUM_MediaImage):
                return True

            # When it is a texture asset, we store it as the dummy asset and stop searching.
            self._dummyAssetId = asset.GetId()
            return False

        # Search for our dummy asset in the user preferences repository.
        repo: maxon.AssetRepositoryInterface = maxon.AssetInterface.GetUserPrefsRepository()
        repo.FindAssets(maxon.AssetTypes.File().GetId(), maxon.Id(), maxon.Id(),
                        maxon.ASSET_FIND_MODE.LATEST, findTexture)

    def CreateLayout(self):
        """Called by Cinema 4D to populate the dialog with controls.
        """
        self.SetTitle("Drag and Drop Example")
        self.GroupSpace(5, 5)
        self.GroupBorderSpace(5, 5, 5, 5)

        # Build the combo box in the menu bar of the dialog.
        self.GroupBeginInMenuLine()
        self.GroupBegin(1000, c4d.BFH_LEFT | c4d.BFV_TOP, cols=2)
        self.GroupBorderSpace(5, 5, 5, 5)
        self.GroupSpace(5, 5)
        self.AddStaticText(1001, c4d.BFH_LEFT |
                           c4d.BFV_CENTER, name="Drag Events as:")
        self.AddComboBox(1002, c4d.BFH_RIGHT | c4d.BFV_TOP)
        self.GroupEnd()
        self.GroupEnd()

        # Add the BitmapCard controls to the dialog.
        for i, card in enumerate(self._cards):
            self.AddUserArea(2000 + i, c4d.BFH_LEFT | c4d.BFV_TOP)
            self.AttachUserArea(card, 2000 + i)

        # Add items to the combo box to select the drag type.
        self.AddChild(self.ID_DRAG_TYPE, c4d.DRAGTYPE_FILENAME_IMAGE, "Files")
        self.AddChild(self.ID_DRAG_TYPE, c4d.DRAGTYPE_ATOMARRAY, "Materials")
        self.AddChild(self.ID_DRAG_TYPE, maxon.DRAGTYPE_ASSET, "Assets")
        self.SetInt32(self.ID_DRAG_TYPE, c4d.DRAGTYPE_FILENAME_IMAGE)

        return True


# Define a global variable of the dialog to keep it alive in a Script Manager script. ASYNC dialogs
# should not be opened in production code from a Script Manager script, as this results in a
# dangling dialog. Implement a command plugin when you need async dialogs in production.
dlg: BitmapStackDialog = BitmapStackDialog()
if __name__ == "__main__":
    dlg.Open(dlgtype=c4d.DLG_TYPE_ASYNC, defaultw=150, defaulth=250)

Hi,

thanks for the kind words both from Maxon and the community. I am looking forward to my upcoming adventures with the SDK Team and Cinema community.

Cheers,
Ferdinand

Hello @holgerbiebrach,

please excuse the wait. So, this is possible in Python and quite easy to do. This new behavior is just the old dialog folding which has been reworked a little bit. I have provided a simple example at the end of the posting. There is one problem regarding title bars which is sort of an obstacle for plugin developers which want to distribute their plugins, it is explained in the example below.

I hope this helps and cheers,
Ferdinand

The result:

The code:

"""Example for a command plugin with a foldable dialog as provided with the
Asset Browser or Coordinate Manger in Cinema 4D R25.

The core of this is just the old GeDialog folding mechanic which has been
changed slightly with R25 as it will now also hide the title bar of a folded
dialog, i.e., the dialog will be hidden completely.

The structure shown here mimics relatively closely what the Coordinate Manger
does. There is however one caveat: Even our internal implementations do not
hide the title bar of a dialog when unfolded. Instead, this is done via 
layouts, i.e., by clicking onto the ≡ icon of the dialog and unchecking the
"Show Window Title" option and then saving such layout. If you would want
to provide a plugin which exactly mimics one of the folding managers, you
would have to either ask your users to take these steps or provide a layout.

Which is not ideal, but I currently do not see a sane way to hide the title
bar of a dialog. What you could do, is open the dialog as an async popup which 
would hide the title bar. But that would also remove the ability to dock the 
dialog. You could then invoke `GeDialog.AddGadegt(c4d.DIALOG_PIN, SOME_ID)`to 
manually add a pin back to your dialog, so that you can dock it. But that is 
not how it is done internally by us, as we simply rely on layouts for that.
"""

import c4d


class ExampleDialog (c4d.gui.GeDialog):
    """Example dialog that does nothing.

    The dialog itself has nothing to do with the implementation of the
    folding.
    """
    ID_GADGETS_START = 1000
    ID_GADGET_GROUP = 0
    ID_GADGET_LABEL = 1
    ID_GADGET_TEXT = 2

    GADGET_STRIDE = 10
    GADEGT_COUNT = 5

    def CreateLayout(self) -> bool:
        """Creates dummy gadgets.
        """
        self.SetTitle("ExampleDialog")
        flags = c4d.BFH_SCALEFIT

        for i in range(self.GADEGT_COUNT):
            gid = self.ID_GADGETS_START + i * self.GADGET_STRIDE
            name = f"Item {i}"

            self.GroupBegin(gid + self.ID_GADGET_GROUP, flags, cols=2)
            self.GroupBorderSpace(5, 5, 5, 5)
            self.GroupSpace(2, 2)
            self.AddStaticText(gid + self.ID_GADGET_LABEL, flags, name=name)
            self.AddEditText(gid + self.ID_GADGET_TEXT, flags)
            self.GroupEnd()
        return True


class FoldingManagerCommand (c4d.plugins.CommandData):
    """Provides the implementation for a command with a foldable dialog.
    """
    ID_PLUGIN = 1058525
    REF_DIALOG = None

    @property
    def Dialog(self) -> ExampleDialog:
        """Returns a class bound ExampleDialog instance.
        """
        if FoldingManagerCommand.REF_DIALOG is None:
            FoldingManagerCommand.REF_DIALOG = ExampleDialog()

        return FoldingManagerCommand.REF_DIALOG

    def Execute(self, doc: c4d.documents.BaseDocument) -> bool:
        """Folds or unfolds the dialog.

        The core of the folding logic as employed by the Asset Browser
        or the Coordinate manager in R25.
        """
        # Get the class bound dialog reference.
        dlg = self.Dialog
        # Fold the dialog, i.e., hide it if it is open and unfolded. In C++
        # you would also want to test for the dialog being visible with
        # GeDialog::IsVisible, but we cannot do that in Python.
        if dlg.IsOpen() and not dlg.GetFolding():
            dlg.SetFolding(True)
        # Open or unfold the dialog. The trick here is that calling
        # GeDialog::Open will also unfold the dialog.
        else:
            dlg.Open(c4d.DLG_TYPE_ASYNC, FoldingManagerCommand.ID_PLUGIN)

        return True

    def RestoreLayout(self, secret: any) -> bool:
        """Restores the dialog on layout changes.
        """
        return self.Dialog.Restore(FoldingManagerCommand.ID_PLUGIN, secret)

    def GetState(self, doc: c4d.documents.BaseDocument) -> int:
        """Sets the command icon state of the plugin.

        This is not required, but makes it a bit nicer, as it will indicate
        in the command icon when the dialog is folded and when not.
        """
        dlg = self.Dialog
        result = c4d.CMD_ENABLED
        if dlg.IsOpen() and not dlg.GetFolding():
            result |= c4d.CMD_VALUE

        return result


def RegisterFoldingManagerCommand() -> bool:
    """Registers the example.
    """
    return c4d.plugins.RegisterCommandPlugin(
        id=FoldingManagerCommand.ID_PLUGIN,
        str="FoldingManagerCommand",
        info=c4d.PLUGINFLAG_SMALLNODE,
        icon=None,
        help="FoldingManagerCommand",
        dat=FoldingManagerCommand())


if __name__ == '__main__':
    if not RegisterFoldingManagerCommand():
        raise RuntimeError(
            f"Failed to register {FoldingManagerCommand} plugin.")

Dear Community,

this question reached us via email-support in the context of C++, but I thought the answer might be interesting for other users too.

The underlying question in this case was how to project points from object or world space into the texture space of an object with UV data. I am showing here deliberately an approach that can be followed both in C++ and Python, so that all users can benefit from this. In C++ one has also the option of using VolumeData and its methods VolumeData::GetUvw or VolumeData::ProjectPoint but must then either implement a volume shader (as otherwise the volume data attached to the ChannelData passed to ShaderData::Output will be nullptr), or use VolumeData:: AttachVolumeDataFake to access ::ProjectPoint. There is however no inherent necessity to take this shader bound route as shown by the example.

Cheers,
Ferdinand

Result

The script has created a texture with red pixels for the intersection points of the rays cast from each vertex of the spline towards the origin of the polygon object. The script also created the null object rays to visualize the rays which have been cast.

raycast_texture.c4d : The scene file.

Code

You must save the script to disk before running it, as the script infers from the script location the place to save the generated texture to.

"""Demonstrates how to project points from world or object space to UV space.

This script assumes that the user has selected a polygon object and a spline object in the order
mentioned. The script projects the points of the spline object onto the polygon object and creates
a texture from the UV coordinates of the projected points. The texture is then applied to the
polygon object.

The script uses the `GeRayCollider` class to find the intersection of rays cast from the points of
the spline object to the polygon object. The UV coordinates of the intersection points are then
calculated using the `HairLibrary` class. In the C++ API, one should use maxon::
GeometryUtilsInterface::CalculatePolygonPointST() instead.

Finally, using GeRayCollider is only an example for projecting points onto the mesh. In practice,
any other method can be used as long as it provides points that lie in the plane(s) of a polygon.

The meat of the example is in the `main()` function. The other functions are just fluff.
"""

import os
import c4d
import mxutils
import uuid

from mxutils import CheckType

doc: c4d.documents.BaseDocument  # The currently active document.
op: c4d.BaseObject | None  # The primary selected object in `doc`. Can be `None`.

def CreateTexture(points: list[c4d.Vector], path: str, resolution: int = 1000) -> None:
    """Creates a texture from the given `points` and saves it to the given `path`.

    Parameters:
        path (str): The path to save the texture to.
        points (list[c4d.Vector]): The points to create the texture from.
    """
    # Check the input values for validity.
    if os.path.exists(path):
        raise FileExistsError(f"File already exists at path: {path}")
    if not path.endswith(".png"):
        raise ValueError("The path must end with '.png'.")

    # Create a drawing canvas to draw the points on.
    canvas: c4d.bitmaps.GeClipMap = CheckType(c4d.bitmaps.GeClipMap())
    if not canvas.Init(resolution, resolution, 24):
        raise MemoryError("Failed to initialize GeClipMap.")

    # Fill the canvas with white.
    canvas.BeginDraw()
    canvas.SetColor(255, 255, 255)
    canvas.FillRect(0, 0, resolution, resolution)

    # Draw the points on the canvas.
    canvas.SetColor(255, 0, 0)
    for p in points:
        x: int = int(p.x * resolution)
        y: int = int(p.y * resolution)
        x0: int = max(0, x - 1)
        y0: int = max(0, y - 1)
        x1: int = min(resolution, x + 1)
        y1: int = min(resolution, y + 1)
        canvas.FillRect(x0, y0, x1, y1)

    canvas.EndDraw()

    # Save the canvas to the given path.
    bitmap: c4d.bitmaps.BaseBitmap = CheckType(canvas.GetBitmap())
    bitmap.Save(path, c4d.FILTER_PNG)

    c4d.bitmaps.ShowBitmap(bitmap)

def ApplyTexture(obj: c4d.BaseObject, path: str) -> None:
    """Applies the texture at the given `path` to the given `obj`.
    """
    CheckType(obj, c4d.BaseObject)

    # Check the input values for validity.
    if not os.path.exists(path):
        raise FileNotFoundError(f"File does not exist at path: {path}")

    # Create a material and apply the texture to it.
    material: c4d.BaseMaterial = CheckType(c4d.BaseMaterial(c4d.Mmaterial), c4d.BaseMaterial)
    obj.GetDocument().InsertMaterial(material)

    shader: c4d.BaseShader = CheckType(c4d.BaseShader(c4d.Xbitmap), c4d.BaseShader)
    shader[c4d.BITMAPSHADER_FILENAME] = path
    material.InsertShader(shader)
    material[c4d.MATERIAL_COLOR_SHADER] = shader
    material[c4d.MATERIAL_PREVIEWSIZE] = c4d.MATERIAL_PREVIEWSIZE_1024

    # Apply the material to the object.
    tag: c4d.TextureTag = CheckType(obj.MakeTag(c4d.Ttexture))
    tag[c4d.TEXTURETAG_PROJECTION] = c4d.TEXTURETAG_PROJECTION_UVW
    tag[c4d.TEXTURETAG_MATERIAL] = material

def CreateDebugRays(spline: c4d.SplineObject, p: c4d.Vector) -> None:
    """Adds spline objects to the document to visualize the rays from the given `p` to the points of
    the given `spline`.
    """
    doc: c4d.documents.BaseDocument = CheckType(spline.GetDocument(), c4d.documents.BaseDocument)
    rays: c4d.BaseObject = c4d.BaseObject(c4d.Onull)
    rays.SetName("Rays")
    doc.InsertObject(rays)

    for q in spline.GetAllPoints():
        ray: c4d.SplineObject = c4d.SplineObject(2, c4d.SPLINETYPE_LINEAR)
        ray.SetPoint(0, p)
        ray.SetPoint(1, q * spline.GetMg())
        ray.Message(c4d.MSG_UPDATE)
        ray.InsertUnder(rays)

def main() -> None:
    """Carries out the main logic of the script.
    """
    # Check the object selection for being meaningful input.
    selected: list[c4d.BaseObject] = doc.GetActiveObjects(c4d.GETACTIVEOBJECTFLAGS_SELECTIONORDER)
    if (len(selected) != 2 or not selected[0].CheckType(c4d.Opolygon) or
        not selected[1].CheckType(c4d.Ospline)):
        raise ValueError("Please select a polygon object and a spline object.")

    polygonObject, splineObject = selected

    # Get the uvw tag, the points, and the polygons of the polygon object.
    uvwTag: c4d.UvwTag = mxutils.CheckType(polygonObject.GetTag(c4d.Tuvw))
    points: list[c4d.Vector] = [polygonObject.GetMg() * p for p in polygonObject.GetAllPoints()]
    polys: list[c4d.CPolygon] = polygonObject.GetAllPolygons()

    # We are casting here in a dumb manner towards the center of the polygon object. In practice,
    # one should cast rays towards the plane of the polygon object. Or even better, use another
    # method to project the points onto the polygon object, as GeRayCollider is not the most 
    # efficient thing in the world.
    rayTarget: c4d.Vector = polygonObject.GetMg().off
    CreateDebugRays(splineObject, rayTarget)

    # Initialize the GeRayCollider to find the intersection of rays cast from the points of the
    # spline object to the polygon object.
    collider: c4d.utils.GeRayCollider = c4d.utils.GeRayCollider()
    if not collider.Init(polygonObject):
        raise MemoryError("Failed to initialize GeRayCollider.")


    # Init our output list and iterate over the points of the spline object.
    uvPoints: list[c4d.Vector] = []
    for p in splineObject.GetAllPoints():

        # Transform the point from object to world space (q) and then to the polygon object's space
        # (ro). Our ray direction always points towards the center of the polygon object.
        q: c4d.Vector = splineObject.GetMg() * p
        ro: c4d.Vector = ~polygonObject.GetMg() * q
        rd: c4d.Vector = rayTarget - ro

        # Cast the ray and check if it intersects with the polygon object.
        if not collider.Intersect(ro, rd, 1E6) or collider.GetIntersectionCount() < 1:
            continue
        
        # Get the hit position and the polygon ID of the intersection.
        hit: dict = collider.GetNearestIntersection()
        pos: c4d.Vector = mxutils.CheckType(hit.get("hitpos", None), c4d.Vector)
        pid: int = mxutils.CheckType(hit.get("face_id", None), int)

        # One mistake would be now to use the barycentric coordinates that are in the intersection
        # data, as Cinema uses an optimized algorithm to interpolate in a quad and not the standard
        # cartesian-barycentric conversion. In Python these polygon weights are only exposed in a 
        # bit weird place, the hair library. In C++ these barycentric coordinates make sense because
        # there exist methods to convert them to weights. In Python the barycentric coordinates are
        # pretty much useless as we do not have such a conversion function here.

        # Compute the weights s, t for the intersection point in the polygon.
        s, t = c4d.modules.hair.HairLibrary().GetPolyPointST(
            pos, points[polys[pid].a], points[polys[pid].b],
                 points[polys[pid].c], points[polys[pid].d], True)

        # Get the uv polygon and bilinearly interpolate the coordinates using the weights. It would
        # be better to use the more low-level variable tag data access functions in VariableTag 
        # than UvwTag.GetSlow() in a real-world scenario.
        uvw: list[c4d.Vector] = list(uvwTag.GetSlow(pid).values())
        t0: c4d.Vector = c4d.utils.MixVec(uvw[0], uvw[1], s)
        t1: c4d.Vector = c4d.utils.MixVec(uvw[3], uvw[2], s)
        uv: c4d.Vector = c4d.utils.MixVec(t0, t1, t)

        # Append the UV coordinates to the output list.
        uvPoints.append(uv)

    # Write the UV coordinates to a texture and apply it to the polygon object.
    path: str = os.path.join(os.path.dirname(__file__), f"image-{uuid.uuid4()}.png")
    CreateTexture(uvPoints, path, resolution=1024)
    ApplyTexture(polygonObject, path)

    c4d.EventAdd()


if __name__ == '__main__':
    main()

Hi,

that your script is not working has not anything to do with pseudo decimals, but the fact that you are treating numbers as strings (which is generally a bad idea) in a not very careful manner. When you truncate the string representation of a number which is represented in scientific notation (with an exponent), then you also truncate that exponent and therefor change the value of the number.

To truncate a float you can either take the floor of my_float * 10 ** digits and then divide by 10 ** digits again or use the keyword round.

data = [0.03659665587738824,
        0.00018878623163019122,
        1.1076812650509394e-03,
        1.3882258325566638e-06]

for n in data:
    rounded = round(n, 4)
    floored = int(n * 10000) / 10000
    print(n, rounded, floored)

0.03659665587738824 0.0366 0.0365
0.00018878623163019122 0.0002 0.0001
0.0011076812650509394 0.0011 0.0011
1.3882258325566637e-06 0.0 0.0
[Finished in 0.1s]

Cheers
zipit

Dear community,

We will have to touch multiple parts of developers.maxon.net on the 18.01.2024 and 19.01.2024 22.01.2024. This will result in outages of our documentation and the forum these days. I will try to keep the outage times to a minimum and it will certainly not span the whole two days. But especially one task I will do on Friday might take hours to complete and I can only do that on a forum which is in maintenance mode.

Please make sure to download a recent offline documentation in case you plan to do extended development work the next two days. As a result, forum support might also be delayed on these days.

Cheers,
Ferdinand

Hi,

as @Cairyn said the problem is unreachable code. I also just saw now that you did assign the same ID to all your buttons in your CreateLayout(). Ressource and dialog element IDs should be unique. I would generally recommend to define your dialogs using a resource, but here is an example on how to do it in code.

BUTTON_BASE_ID = 1000
BUTTON_NAMES = ["Button1", "Button2", "Button3", "Button4", "Button5"]
BUTTON_DATA = {BUTTON_BASE_ID + i: name for i, name in enumerate(BUTTON_NAMES)}

class MyDialog(gui.GeDialog):

    def CreateLayout(self):
        """
        """
        self.GroupBegin(id=1013, flags=c4d.BFH_SCALEFIT, cols=5, rows=4)
        for element_id, element_name in BUTTON_DATA.items():
            self.AddButton(element_id, c4d.BFV_MASK, initw=100, 
                           name=element_name)
        self.GroupEnd()
        return True

    def Command(self, id, msg):
        """
        """
        if id == BUTTON_BASE_ID:
            print "First button has been clicked"
        elif id == BUTTON_BASE_ID + 1:
            print "Second button has been clicked"
        # ...
        if id in BUTTON_DATA.keys(): # or just if id in BUTTON_DATA
            self.Close()
        return True

Dear development community,

On September the 10th, 2024, Maxon Computer released Cinema 4D 2025.0.0. For an overview of the new features of Cinema 4D 2025.0, please refer to the release announcement. Alongside this release, a new Cinema 4D SDK and SDK documentation have been released, reflecting the API changes for 2025.0.0. The major changes are:

C++ API

• What was formerly has been know as the Classic API has been deprecated in favour of the Cinema API. Alongside this a new cinema namespace has been introduced which contains all the entities which were formerly in the anonymous global namespace known as the Classic API. Plugin authors must adopt their code to this new API, although the changes are not nearly as extensive as for 2024. See the 2025 migration guide for details. Code examples and documentation have been updated to now refer to a Cinema API.
• 2025 uses OCIO as the default color management mode, brings an improved color picker, and made general improvements to the consistency of the OCIO implementation. This had some effects on the underlying OCIO API which are reflected in two new code examples in the OCIO Manual and a new plugin in the SDK.

Python API

• Python also received the update from Classic to Cinema API. But here the change was more of a cosmetic nature confined to the documentation. The c4d package remains the home for all formerly Classic and now Cinema API entities.
• The mxutils package received updates around standardized scene traversal, random number generation, and more.
• Graph descriptions now support variadic ports of arbitrary complexity and explicit port references.

Head to our download section for the newest SDK downloads, or the C++ and Python API change notes for an in detail overview of the changes.

We discovered late in the cycle bugs in the Asset API code examples and OCIO code in the Python SDK. Which is why the publication of the Python SDK and GitHub code examples has been postponed until these bugs are fixed. They should be ready latest by Friday the 13th of September. But the Python online documentation is accessible and error free (to our knowledge).

We had to make some last minute changes to the C++ SDK regarding OCIO code examples. Only the extended C++ SDK contains these changes. The application provided sdk.zip will catch up with the next release of Cinema 4D.

Happy rendering and coding,
the Maxon SDK Team

Cloudflare unfortunately still does interfere with our server cache. And you might have to refresh your cache manually.

When you are not automatically redirected to the new versions, and also do not see 2024.5 in the version selector, please press CTRL + F5 or press CTRL and click on the reload icon of your browser anywhere on developers.maxon.net/docs/ to refresh your cache. You only have to do this once and it will apply to all documentations at once. Otherwise your cache will automatically update latest by 19/07/2024 00:00.

Hi,

sorry for all the confusion. You have to pass actual instances of objects. The following code does what you want (and this time I actually tried it myself ;)).

import c4d

def main():
    """
    """
    bc = doc.GetAllTextures(ar=doc.GetMaterials())
    for cid, value in bc:
        print cid, value

if __name__=='__main__':
   main()

Cheers,
zipit

Dear development community,

On June the 18th, 2025, Maxon Computer released Cinema 4D 2025.3.0. For an overview of the new features of Cinema 4D 2025.3.0, please refer to the 2025.3.0 release notes. Alongside this release, a new Cinema 4D SDK and SDK documentation have been released, reflecting the API changes for 2025.3.0. The major changes are:

C++ API

• After the introduction of the CMake build system generator in Cinema 4D 2025.2.0, the C++ SDK now only supports CMake as its build system generator. The Legacy Build System is no longer supported. When you have not yet switched to CMake, please refer to our Build Systems manual for more information on how to switch to CMake.
• Updated the required Windows SDK version to Windows 10 SDK 10.0.20348.0. You might have to update Visual Studio and install the SDK via the Visual Studio installer app.

Python API

In 2025.3.0, there is a critical issue with c4dpy that will cause it to halt indefinitely when run for the first time. See the c4dpy manual for an explanation and workaround. This issue will be fixed with a hotfix for 2025.3.0.

• Added features to c4d.documents.BatchRender class, to have more control over render settings, cameras, and takes for a given job.
• Added a suite of new code examples around the subject of dialogs, including both simple beginner examples, as well as more complex examples covering subjects such as dynamic GUIs, value and layout persistence, and using resources to define dialogs and string translations. The new examples all begin with the prefix py-cmd_gui_, see our plugin examples overview for details.

Head to our download section to grab the newest SDK downloads, or read the C++ or Python API change notes for an in detail overview of the changes.

Happy rendering and coding,
the Maxon SDK Team

Cloudflare unfortunately still does interfere with our server cache. You might have to refresh your cache manually to see new data when you read this posting within 24 hours of its release.

Hey @SteveHill3D,

it's okay, the start is always a bit chaotic. That snippet alone would have told me some things.

Yes, sorry, MSG_DESCRIPTION_POSTSETPARAMETER is fired within the drag event (the parameter has still to be set). The final description event is MSG_DESCRIPTION_USERINTERACTION_END. But I still do not really understand what you are doing. What is triggering the updates? Just dragging one of the sliders will not update the tool in our edge cutter tool example (because it does not really implement the interactive mode that comes with description tools).

So, the tool should either fire when you have keyboard or viewport inputs and implemented MouseInput or KeyboardInput. When you click Apply, it should call DoCommand. You can of course hook into Message to react to all sorts of things (and that is indeed how you implement the interactive mode), but you message implies that your tool fires on your own. Which it should not.

Cheers,
Ferdinand

Hey @SteveHill3D,

Storing a tool state in a tag is possible, but a bit unusual. But generally you are on the right track. Tags are also internally often used as hidden data containers. When you write a modelling tool, you probably already found out that points and polygons are are actually stored in hidden tags on objects.

I am not sure though if using tags in tools is a good advice, as injecting all that data all the time into the scene graph is probably not the fastest. It depends a bit on what you are doing, but in general the solution is a bit unusual.

Cheers,
Ferdinand

Hey @SteveHill3D,

Thank you for reaching out to us. It depends a bit on what is your 'tool'. When it is a 'classic' tool, i.e., implemented as a ToolData with a GeDialog, then BFM_DRAGEND would be the way to sort out BFM_ACTION events for a slider that are the final action of a drag event. When you search for the message symbol BFM_DRAGEND and its sibling symbols BFM_DRAGSTART and BFM_ACTION_INDRAG here on the forum, you will find multiple code examples around the topic of sliders. I think there are also some examples in the C++ SDK.

When your tool is a DescriptionToolData, i.e., a node in disguise, then you cannot handle drag events yourself. Your tool should fire on its own only after MSG_DESCRIPTION_POSTSETPARAMETER has fired for your node, i.e., after the final value of a drag event for some slider has been set.

Please have a look at our Support Procedures, we require users to post code for pretty much all questions, as it minimizes the guess work on our side. As for example me here writing about two cases.

Cheers,
Ferdinand

@karthikbp

As far as I can see this at a glance, this seems to be correct. You already did the most important thing by using RDATA_RENDERREGION and not some camera cropping tricks, so it renders with the full scene data for each tile.

There is however one issue, and it depends on the render engine how it is handled. At verbatim, kernels applied to your rendering (e.g., a box filter) will be slightly wrong, because for the the seams of a tile, there is data missing (the seam pixels of the neighboring tile) which would exist in a full rendering. E.g., when you have this,

--------------- ----------------
              x y
    Tile A    x y    Tile B
              x y
--------------- ----------------

a rendering split into two tiles Tile A and Tile B, where x are the 'seam pixels' of Tile A and y are the seam pixels of Tile B. If you would have rendered the whole image in one go, processing one of the xs with a kernel would have included neighboring pixels, i.e., also what is now the seam pixels y of the other tile. So, at the borders of the tile, any filter kernels you will apply will not be quite the same.

To prevent that issue, Redshift does render region tiles with an extra border of the maximum size of the kernels used for that rendering. But the standard renderer does not do that. Other render engines which might support our render region setting might not do that either. In such cases, you would have to either live with the small error or render with an extra border yourself, depending on the kernels that will be used., and then crop the final result back.

Cheers,
Ferdinand

Hello @atg,

Welcome to the Maxon developers forum and its community, it is great to have you with us!

Getting Started

Before creating your next postings, we would recommend making yourself accustomed with our forum and support procedures. You did not do anything wrong, we point all new users to these rules.

• Forum Overview: Provides a broad overview of the fundamental structure and rules of this forum, such as the purpose of the different sub-forums or the fact that we will ban users who engage in hate speech or harassment.
• Support Procedures: Provides a more in detail overview of how we provide technical support for APIs here. This topic will tell you how to ask good questions and limits of our technical support.
• Forum Features: Provides an overview of the technical features of this forum, such as Markdown markup or file uploads.

It is strongly recommended to read the first two topics carefully, especially the section Support Procedures: How to Ask Questions.

About your First Question

I can see why would think that, but you mixed things there a bit up. The CMake SDK build system was introduced with 2025.2.0 and became the standard with 2026.0.0. Between 2025.2 and 2025.3 we supported both build systems as a grace period for developers to get accustomed.

Chances are very good, that you can just copy the CMake setup, i.e., the cmake folder and files such as CMakeLists.txt, CMakePresets.json, and sdk_modules.txt to a 2025.0 folder and it will generate a correct build system for you.

But the supported range is only 2025.2+. For older projects you would have to use the old project tool based build system. Since I know what you are trying to do, I would recommend trying copying before you get into the old build system of ours.

• 2025.2 Release Notes
• 2025.2 Build System Docs (which covered both the old Project Tool and CMake)

Cheers,
Ferdinand

edit: You will only find the old project tool tooling in old extended SDKs which supported it, such as 2025.2 or 2025.0.1

hey @Gene,

So, you were just trying to add information for future readers? That is of course very welcome and explains my inability to extract a question from your posting.

I would not have been that generous with the word bug either. Since this has never been fixed, chances are high that we came to the same conclusion internally.

In general, you should not expect Command calling patterns to make perfect sense in every case. There are multiple cases where Command is triggered more often than one would think at first glance. I would also not try to interpret some deeper sense into all that.

Cheers,
Ferdinand

Hey @Gene,

Thread-necromancy is often not so good, because it almost always derails the original topic and often also lacks in clarity. I also here do not understand what your concrete question is?

When I click on the Quicktab, the first event returns True, while the second returns False.

What do you mean by "the event returns true"? It is you, the developer, who returns the result for an event (or you do not handle it at all). Are you talking about something like BFM_ACTION_VALUE?

If I drag over two entries on the Quicktab gadget (click on one entry, then drag to the next entry and let go of the mouse,) Command triggers three times, msg[c4d.BFM_ACTION_INDRAG] returns True the first two times and False for the last one. Also, the first entry returns True for its IsSelected() check on mouse down. After dragging, the the second entry's IsSelected() is True. Second entry's IsSelected() is also true when I let go of the mouse.

I do not see any question here, so what is the goal?

Regarding Command triggering twice, is it because of the mouse events?

GeDialog.Command is just a convenience wrapper for GeDialog.Message events (most from the BFM_ACTION family). If you want the full picture, use Message. I struggle to see a tangible question which I could answer, what do you want to achieve?

Yes, some controls fire multiple times in Command, it is impossible (and also somewhat futile) to reconstruct the reason for each of them. Someone thought at some point it would be convenient to forward this kind of event to Command for some feature in Cinema 4D.

I am not familiar with the exact issue discussed in this topic, but at a glance, what Maxime wrote then looks a bit overkill with the hashing, I would just store the last selected element and be done with it. Alternatively you could design your code so that you do not tie any heavy logic to a tab being activated (which is IMHO not a great idea in general), so that you do not mind when such code runs multiple times.

Cheers,
Ferdinand

class MyDialog (c4d.gui.GeDialog):
    ID_TAB_1: int = 10000
    ID_TAB_2: int = 10001

    IDS_TABS: tuple[int, ...] = (ID_TAB_1, ID_TAB_2)

    def __init__(self) -> None:
        self._activeTab: int = MyDialog.ID_TAB_1

    def Command(self, cid: int, msg: c4d.BaseContainer) -> bool:
        """
        """
        if cid == self._activeTab:
            return True
        elif cid in MyDialog.IDS_TABS:
            self._activeTab = cid

        if cid is MyDialog.ID_TAB_1:
            foo()
        elif cid is MyDialog.ID_TAB_2:
            bar()

        return True

Hey @mfersaoui,

Thank you for reaching out to us. The question is a bit ambiguous. What it entails when 'Global Illumination is enabled' (or not), differs from render engine to render engine. There is neither an abstracted switch to toggle GI in all render engines, nor a flag which would signal of GI is enabled or not.

So, the first thing you would have to do, is read RDATA_RENDERENGINE and then branch of based on that. For the standard renderer, you would then check if the GI post effect is loaded and enabled. For Redshift you would get the RS post effect and then check there if has GI enabled.

You can find the post effect symbols here: VideoPost Types

Cheers,
Ferdinand

Some example code for searching the post effects in some render data.

# Get the active render data of the document.
renderData: c4d.documents.RenderData = doc.GetActiveRenderData()

# Set the active render engine to Redshift.
renderData[c4d.RDATA_RENDERENGINE] = c4d.VPrsrenderer

# Iterate over all video post effects and remove any effect not compatible with the Redshift 
# render engine and finally make sure the Redshift video post effect itself is present. We do 
# not remove the effects in place in the loop, as that would mess up the iteration because nodes
# effectively work as a linked list.
removeEffects: list[c4d.documents.BaseVideoPost] = []
foundRedshiftEffect: bool = False
for effect in mxutils.IterateTree(renderData.GetFirstVideoPost(), True):
    # This is the Redshift video post effect.
    if effect.GetType() == c4d.VPrsrenderer:
        foundRedshiftEffect = True
        continue
    # This is some effect not compatible with Redshift.
    elif not effect.RenderEngineCheck(c4d.VPrsrenderer):
        removeEffects.append(effect)

# Remove all the video post effects we marked for removal.
for effect in removeEffects:
    effect.Remove()

# And add the Redshift video post effect if it was not found yet. Note that there is no hard
# guarantee that a render engine uses the same ID for its video post effect as the render 
# engine ID (VPrsrenderer in this case). But it is a very common convention, check with your
# render engine vendor for details.
if not foundRedshiftEffect:
    redshiftEffect: c4d.documents.BaseVideoPost = mxutils.CheckType(
        c4d.documents.BaseVideoPost(c4d.VPrsrenderer))
    renderData.InsertVideoPost(redshiftEffect)

Hey @SteveHill3D,

Welcome to the Maxon developers forum and its community, it is great to have you with us!

Getting Started

Before creating your next postings, we would recommend making yourself accustomed with our forum and support procedures. You did not do anything wrong, we point all new users to these rules.

• Forum Overview: Provides a broad overview of the fundamental structure and rules of this forum, such as the purpose of the different sub-forums or the fact that we will ban users who engage in hate speech or harassment.
• Support Procedures: Provides a more in detail overview of how we provide technical support for APIs here. This topic will tell you how to ask good questions and limits of our technical support.
• Forum Features: Provides an overview of the technical features of this forum, such as Markdown markup or file uploads.

It is strongly recommended to read the first two topics carefully, especially the section Support Procedures: How to Ask Questions.

About your First Question

You could look at our edgecuttool.cpp C++ SDK example, it demonstrates both the usage of undos and cinema::InteractiveModeling_Restart, i.e., rolling updates. In some cases InteractiveModeling_Restart will not cut it you have to un-roll your undos yourself or even not use undos at all for rolling updates and instead work with a tool finalization logic.

By chance I just wrote an example for the latter for the upcoming Python SDK. You will not be able to run it, as the customer release version is missing the Python API to deal with SDS weights, but you can have a look at its code. The idea is simple: Establish a ground truth and operate based on that. But for modelling tools and especially tools that add or remove geometry using undos and InteractiveModeling_Restart should be preferred when possible, as it will be usually faster, as the cinema core can pull some tricks you cannot as a third party.

Cheers,
Ferdinand

Please understand that this example is a preview and might be subject to change.
py-cmd_tool_finalization_2026_2.zip

Hey @karthikbp,

Thank you for reaching out to us. And sorry, I somehow overlooked your topic. Yes, that is how I would have done it too, via RDATA_RENDERREGION_LEFT, etc. The 2026.2 Python SDK will contain new rendering examples, that could be something I could add, as tile rendering is something that comes up from time to time.

As a fair warning: Your code will not respect OCIO, i.e., the images will have the wrong colors. Since you marked this as 2026, where OCIO is the color management standard, this would apply to all documents. See open_color_io_2025_2.py for an example how to do it correctly. The next release will streamline things there quite a bit.

Cheers,
Ferdinand