That is what I was looking for. Thanks Manuel!

@cairyn Thank you again. I will check your patreon

Hello @Boony2000,

thank you for reaching out to us. There is unfortunately no guarantee that everything that should have an id symbol has an id symbol. Or more directly, there are other cases where one most use integer instead of symbols. This mostly happens for message symbols, but there are also a few cases for NodeData types, e.g., there is no Omgcloner. These mostly did happen as an oversight of the person who did implement these functionalities, there is no higher meaning behind it.

As a developer one must define such symbol locally or hardcode it. We are currently not planning to update the symbols in this regard.

Thank you for your understanding,
Ferdinand

Thanks for the info!

Hello @AiMiDi,

it would really help if you could clarify/confirm the context. I am still assuming that you are writing a SceneLoaderData, namely for your MikuMikuDance project.

We have an example on GitHub for how to implement an im- and exporter plugin, the STL-example. Invoking the status bar indicators, i.e., StatusSetSpin. StatusSetBar and StatusSetText, for a computational process, e.g., loading a file, are a bit of a special case regarding the UI-restrictions. I always also struggle with them and what is allowed where. In general, you can get away with a bit more with them, as they do not check immediately for being on the main thread and do not refuse execution if they are not. But you can also run into problems with them outside of the main thread. With that being said, our STL example also makes use of StatusSetBar, which sort of indicates that it is safe to use within SceneLoaderData::Load (more on that later).

Regarding providing a custom progress dialogs for the import process: Most importers of Cinema do not do that. There are exceptions like the FBX importer which spawns its own dialog to give feedback for the importing process.

When you invoke GeIsMainThread() in SceneLoaderData::Load, you will see that you are in almost all cases in the main thread (at least the ones where I did try). But in the end, there is no guarantee that this will always hold true. What I would do is safeguard all GUI operations with GeIsMainThread(), including status-bar operations, i.e., only carry them out when Load is being called from the main thread and otherwise just skip them. Then you can also open as many dialogs as you want from there.

Our FBX importer plugin for example instantiates an interface for handling importing FBX within Load. Cascading out from that interfac instantiation, also a ProgressDialog will be being instantiated and opened (there are some types involved in between). But frankly, I would not bother with all that complexity and just use the status bar of the main app, i.e., StatusSetBar. Checking for the main thread seems advisable though.

Cheers,
Ferdinand

Hello @blastframe,

thank you for closing your topics.

Cheers,
Ferdinand

Hello @César-Vonc,

without any further questions or replies, we will consider this topic as solved by Wednesday and flag it accordingly.

Thank you for your understanding,
Ferdinand

Hello @Rox,

without any further questions or replies, we will consider this topic as solved by Wednesday and flag it accordingly.

Thank you for your understanding,
Ferdinand

Hello @Motion4D,

without any further questions or replies, we will consider this topic as solved by Wednesday and flag it accordingly.

Thank you for your understanding,
Ferdinand

I see, thank you for the answer.

Cheers,
Ogers.

Hello Dan,

I know that the situation is a bit unsatisfying, but that is unfortunately mostly a design problem you have there and not an API one. Which are often questions that are hard to answer "in a good way" and technically also out of scope of support.

In case you encounter any problems further down the road, please do not hesitate to revisit us.

Cheers,
Ferdinand

blush... not remembering my own threads, ouch! .-)
thanks Maxime !

Hi,

you can create those preset with a commandData sure.

When you add the graph to your node material it will call the function you defined in maxon::nodes::NODESPACE::CREATEMATERIALGRAPHFUNC See Proving Default Graph Setup for more information. So be sure to remove the nodes added by this function if they are not needed.

You must create a NodeMaterial, insert it in the document, add the graph for the right nodespace and retrieve the graph itself (by first retrieving the nimbusref). We got an example on this page: Reading and Modifying Node
This page also contains an introduction to Transaction. maxon::GraphModelInterface::BeginTransaction must be used if you want to modify the graph. You can than Commit your changes, which will ensure the graph is in a correct state. You can have a look a nodespace_impl.cpp, you will find the function CreateMaterialGraphDefaultSetup. remarque: this function doesn't need transactions to modify the graph.
In this handbook, we are using transaction to modify some port's value inside a graph. With both examples, you will understand how to add nodes, connect them, and sets values.

Cheers,
Manuel.

Hi,

This have been fixe and will be available in a futur update.

Cheers,
Manuel

Hello @nicholas_yue,

thank you for reaching out to us. You can find the crash reports of Cinema in its preference folder. The preference folder should be located in \{​​​​​​​USER}​​​​​​​\AppData\Roaming\MAXON\{​​​​​​​​​​​​​​VERSION}​​​​​​​​​​​​​​\. It can also be opened via a button at the bottom of the preferences menu.

4f6efb26-a940-40f4-ba2e-235d991e14e4-image.png

However, this will lead you to the preference folder of the Cinema 4D app, not the one for commandline.exe. The last element in the path will be a folder with a name like S24_XXX_YYYYYYY where the XXX part is the minor revision and the YYYYYYY part a hash with no higher meaning for the user. So, the path is then for example {USER}\AppData\Roaming\MAXON\S24_037_DFA0E3FB. When you have run the command line app at least once, then there will also be a folder with almost the same path, but only that an _x has been appended, e.g., {USER}\AppData\Roaming\MAXON\S24_037_DFA0E3FB_x. This path then contains all the commandline.exe data, including the bug reports, which should be visible to you under {USER}\AppData\Roaming\MAXON\{VERSION}_x\_bugreports. For testing purposes, you can always invoke a crash on Cinema 4D by using the argument -crashtest. So, .\Commandline.exe -crashtest will force a crash which should pop up in your {USER}\AppData\Roaming\MAXON\{VERSION}_x\_bugreports.

Cheers,
Ferdinand

Thank you Andreas for closing it.

Cheers,
Ferdinand

Hi,
Thank you so much for your suggestion. I changed my code to iterate each surface. It works very well. Thank you for your help, which solved my problem.
6ecf2fc3-56cc-4834-9632-0b815d3a5f39-image.png
Thanks,
Manuel

Below gets the focus back on the first tab of the pyTag (after other objects have been selected), but it only works with/after a button click..
Perhaps this might be of use.

def message(id, data): if id == c4d.MSG_DESCRIPTION_COMMAND: id2 = data['id'][0].id if id2 == c4d.ID_USERDATA: userDataId = data['id'][1].id if userDataId == 1: # << just a button on the pyTag with ID 1 ### do some function... # GET FOCUS BACK on the pyTags's 1st Tab: op.GetObject().SetBit(c4d.BIT_ACTIVE) op.SetBit(c4d.BIT_ACTIVE) c4d.gui.ActiveObjectManager_SetObject(c4d.ACTIVEOBJECTMODE_TAG, op.GetObject(), c4d.ACTIVEOBJECTMANAGER_SETOBJECTS_OPEN, c4d.DescID(c4d.DescLevel(1))) op.GetObject().DelBit(c4d.BIT_ACTIVE) c4d.EventAdd()

Thanks for the response, that seems to have solved the issue.

John Terenece

Hi, @Boony2000 you are right, the documentation will be fixed.

Cheers,
Maxime.