Hello,

the selection order is internally stored in the Object Manager. If you add an object to the selection you have to update an internal cache with GetActiveObject().

See C++ documentation: Selections

and this thread: Adding to document selection issue

best wishes,
Sebastian

Hello,

the "checked" state does not have any functionality. It is just a visual marker for your user.

Or to put it differently: you don't need to read if an element is "checked" since you yourself set this "checked" state in the first place when you create the menu with ShowPopupDialog().

best wishes,
Sebastian

Hello and welcome to the PluginCafe.

ShowPopupDialog() returns the ID of the selected item. With that ID you can decide what to do next.

What do you mean with "solo in viewport"?

Do you mean the Viewport Solo Mode or the layer solo mode?

You can switch the viewport solo mode using the associated commands. You can call a command using CallCommand() and the associated ID. The ID can be found in the "Customize Commands" manager.

# check if object is selected
if op is None:
    return

# menu
IDM_MENU1 = c4d.FIRST_POPUP_ID
IDM_MENU2 = c4d.FIRST_POPUP_ID+1

menu = c4d.BaseContainer()
menu.InsData(IDM_MENU1, 'Solo')
menu.InsData(IDM_MENU2, 'Non-Solo')


# show and get result
result = gui.ShowPopupDialog(cd=None, bc=menu, x=300, y=300)

if result == IDM_MENU1:
    # set solo
    c4d.CallCommand(431000059)

else:
    # set non-solo
    c4d.CallCommand(431000058)

c4d.EventAdd()

Also, please use the Q&A system.

best wishes,
Sebastian

Hello,

this code seems to work perfectly fine from a script:

c4d.documents.KillDocument(doc)
c4d.EventAdd()

A new document can be created and inserted like this:

newDocument = c4d.documents.BaseDocument()
if newDocument is None:
    return

c4d.documents.InsertBaseDocument(newDocument)
c4d.documents.SetActiveDocument(newDocument)

newDocument.SetDocumentName("new_document.c4d")

c4d.EventAdd()

Could you please share your code? How do you execute your code?

best wishes,
Sebastian

Hello,

the Source Processor only checks for coding style violations and creates auxiliary code. It cannot check for valid C++ syntax (because C++ is quite an complex language).

Coming back to the issue of return values, only the compiler can check that at compile time. And, yes, unfortunately Visual Studio and Xcode behave differently.

best wishes,
Sebastian

Hello,

I just want to add that an example on how check a spline can be found in the BaseObject Manual.

best wishes,
Sebastian

Hello,

there is not much to add here. Visual Studio and Xcode are just two different programs. They use two different C++ compilers. Each compiler interprets (and supports) the C++ standard a little bit differently.

So Visual Studio 2015 does not pay attention to warn_unused_result while Xcode does. If in doubt, always compile on both platforms and make sure there are no warnings on any of these platforms.

You don't need to write different code for different platforms. You just have to write correct code and Xcode simply performs better checks.

General information on error handling can be found in the documentation: Error Handling.

best wishes,
Sebastian

Hello,

you have to add

if __name__=='__main__':
    main()

as usual to execute the script.

best wishes,
Sebastian

Hello,

you cannot create a Material in the main() function of a Python Generator object.

The main() function of the Python Generator object defines a cache of "virtual" BaseObjects which will appear in the scene.

Materials cannot be created this way. A material must be inserted into the BaseDocument. This must only happen from the main thread, typically in reaction to some user interaction.

One way of doing this would be to add a user data button to your Generator. Then your user could simply press that button to create the needed materials. Pressing the button can be detected by implementing the message() function.

This could look like this:

def main():

    # search for material
    mat = doc.SearchMaterial("Generator Material")

    if mat is None:
        return None

    # create object
    cube = c4d.BaseObject(c4d.Ocube)
    
    # apply material
    ttag =  cube.MakeTag(c4d.Ttexture)
    ttag[c4d.TEXTURETAG_MATERIAL] = mat

    return cube

def message(id, data):
    if id == c4d.MSG_DESCRIPTION_COMMAND:
        buttonId = data['id']

        # check button ID
        if buttonId[1].id == 1:
            
            # create material and insert it into the host document
            c4d.StopAllThreads()

            material = c4d.Material()
            material.SetName("Generator Material")
            material[c4d.MATERIAL_COLOR_COLOR] = c4d.Vector(1,0,0)

            doc.InsertMaterial(material, None)

            c4d.EventAdd()

Also, please use the Q&A system.

best wishes,
Sebastian

Hello,

as always, please post questions regarding the Cinema 4D APIs in the "Cinema 4D Development" subforum. Please also use the Q&A system.

Do you mean with 'str' value the label of the option?

GetUserDataContainer() allows to browse through all user data description containers. These contains contain information on the settings of the user data parameters. Information on the cycle interface is stored under c4d.DESC_CYCLE which returns a BaseContainer with the information. This can look like this:

# user data parameter with the ID 1
ID = c4d.DescID(c4d.DescLevel(c4d.ID_USERDATA, c4d.DTYPE_SUBCONTAINER,0), c4d.DescLevel(1))

# get all user data parameter descriptions
for id, bc in op.GetUserDataContainer():
    
    # check for ID 1
    if id == ID:
        
        # print parameter name
        print("Parameter Name: " + bc.GetString(c4d.DESC_NAME))
        
        # get cycle settings
        cycleBC = bc.GetContainer(c4d.DESC_CYCLE)

        # print cycle data
        for element in cycleBC:
            print("Option: " + str(element[0]))
            print("Label: " + str(element[1]))

best wishes,
Sebastian