Thanks! I'll try that.

Thanks @s_bach This is very helpful. Best wishes.

I'm just going to go ahead and mark this as solved. Either using an empty Basecontainer or the set function solve the problem. Thank you for explaining!

@zipit said in How to handle C4D Unicode in Python scripting?: well, that API object names thing is a flaw of Python 2. So working as expected or not as expected is a bit a question of the point of view. If you got the string passed from any other source the problem would be the same. Right. The main thing is to understand the issue, and then to write the chapter in a way that explains what to watch out for. (I do wonder how third-party modules would do with a name string passed to them from a script that reads them from the API... well, another bridge to cross another day.) Python 3 clearly is superior in that respect, as there is no unicode class and all str objects are unicode (what they appear to be already in C4D, but with matching len, index, and slice capabilities). On a more productive note: I think that focusing in Unicode strings isn't really that important for Python stuff in c4d, since object names should be something you largely ignore as they are a unreliable source of identification and only are rarely important in other contexts. Hmm, I am not sure whether I would agree to that. Good naming is essential to find your way through complex scenes, and a good naming schema can be built in a way that is friendly to string search and comparison criteria, esp. if you can build your own scripts to perform the search and selection. I just point at the _L _R naming schema for joints that is common in C4D's docs. Of course, if your objects are all named Cube, Cube.1, Cube.2, Cube.3, then name-based identification may be unhelpful Anyway, I am not the person to judge that, as I am only teaching Python to interested users. What they do with it is their own decision; I just have to point out the crucial points so they can apply the code to their own concepts.

Thanks for the input! It's a shame you can't fiddle with the palettes. I think I'll just do it like x-particles and have a command that loads the palette and the user can dock it himself. Not the most elegant, but gets the job done. Cheers

Thanks for your advice. The build is complete. It was because VS2017 when Unity was installed was old. Now you can build other plugins. Thank you very much.

Hey zipit, thanks for the answer! Exactly what I needed! Best Regards, Florian

Hello Sebastian, thanks for this quick response! I dind't know about this. But this solved my issue! Best Regards, Florian

hello, We need to ask if you are compiling the SDK, your own project, etc. Different question, you should open a different thread :) It will help other people to find the thread. Cheers, Manuel

Hi, thank you for the clarification. Cheers zipit

Thank you for the help @m_magalhaes

Hi Riccardo, Thank you for the detailed answer. With the many options available, I chose one that fits best with our installer. Again, thanks for the help! Maxime

Hi Root Star, thanks for reaching out us. With regard to the IDE version, we highly suggest sticking the compatibility table reported in our documentation. Visual Studio 2019 is not supported by R20 and it's likely not to be officially supported also on R21. With regard to .hxx files, these are generated by our source processor when the building process is initiated and it's highly discouraged to change or get rid of them during the building process. The issues you're facing are highly related to the fact that the solution/project file(s) built by the projecttool (when kernel_app_64bit.exe g_updateProject=<your path to Cinema SDK> is executed) are not 100% compatible with VS2019 resulting in building tool-chain flaws. Best, Riccardo

hello, this thread will be considered as Solved tomorrow is you have nothing to add. Cheers Manuel

hello, we are sorry to hear that. Unfortunately this forum is for maxon API support and for every thirds party developers. Your issue look like a bug or something, you have to use this platform instead side remark : As this is your first post i would also like to point you to this topic I've set this up this time but it is important, that will help us and the community. Cheers Manuel

@mp5gosu I have one last question. on the thread for custom nodes that you mentioned above there was a file which was posted from Niklas. https://raw2.github.com/PluginCafe/examples/master/treeview/custom-nodes/custom-nodes.cpp Since this file was not there anymore and most probably it was a full code of what I am asking for, can it be that you or someone else might have that file somehow? That would be a great help. Thank you.

hello @HectorSmallwood @HectorSmallwood said in Change LONG_CYCLE selected Item.: Assume that I have the following code, the Item with id 0 will be selected by default. Is there any way that I can change this? Like after a specific action the Item 1 will be selected? That's exactly what the code is doing in the Init() function using SetParameter(). You change the value of the parameter, the UI show the item with that value in the list. So by default the parameter value is 1 so the UI show the item with the value 1 "Item 1" If you want to change the item somewhere else, same thing just change the value of the parameter, the ui will follow. node->SetParameter(DescID(MY_CYCLE_ID), GeData(1), DESCFLAGS_SET::NONE); I'am adding an answer here as it is a related. But for your second question if the answer doesn't fit your need, please open a new thread and post your question in a new thread. That will help us to keep things organized. @HectorSmallwood said in Change LONG_CYCLE selected Item.: event to determine when the selected item in the ListBox is changed. If i understand the question, you have to check for MSG_DESCRIPTION_CHECKUPDATE message type in the Message() function as follow. virtual Bool Message(GeListNode* node, Int32 type, void* data) override { switch (type) { case MSG_DESCRIPTION_CHECKUPDATE : { DescriptionCheckUpdate* dcu = static_cast<DescriptionCheckUpdate*>(data); if (dcu == nullptr) return true; maxon::Int32 id = (*(dcu->descid))[0].id; if (id == MY_CYCLE_ID) { DiagnosticOutput("Cycle have been changed"); // ... do Something } break; } } return true; }; Cheers Manuel

Again sorry, I've tested with the Studio version. Using C4DPL_PROGRAM_STARTED case I can confirm this "bug" with a Educational version and a Demo version. Not with the Studio version. Maybe something with that extra "popup" windows on those both versions. Cheers Manuel.

Hello @m_adam I see, I will have to use one of the other alternatives then. Thank you.