Wow, I never thought of that.
Very good to know, thank you for asking! :-)

Cheers & have a nice weekend,
Frank

Thanks! Yeah, that would’ve been my solution, too. I just wonder why the error occurs in the first place. In the project where the error doesn’t come up, I didn’t set that option, so there has to be a difference somewhere, and I wanted to know why.

Anyway, I’ll just suppress it ;-) thank you.

Cheers,
Frank

Oh, ok

I didn’t know if it’s ok to migrate, and simple didn’t try... the whole time I was looking for a way to suppress the warnings

Erm, thanks!

Of course, I’d have to do it one by one.
But I don’t know what to do. How do I make it go away?

I also thought about this. But it doesn’t change the errors. Neither do normal or doxy comments.

At the bottom of the second screenshot you can see that the next function also gets the error, and so does everything in the namespace scope.

Thanks, that's nice to know!

So, if it can be fixed in the Project Tool, it can also be fixed in the project files I already have. Do you know what I'd have to change?

Cheers,
Frank

Hello,

I use namespaces a lot, and I indent the code within the namespace scope. That also how Xcode auto-formats it.

In one of my projects, this works fine:

In another one, it throws errors that can only be "fixed" by not indenting the code. That really annoys me.

Both projects were created with the R23 Project Tool, and both projectdefinition.txt look like this (except for the ModuleId, of course):

// Supported platforms - can be [Win64;OSX]
Platform=Win64;OSX

// Type of project - can be [Lib;DLL;App]
Type=DLL

// API dependencies
APIS=core.framework;cinema.framework;mesh_misc.framework;math.framework;

// C4D component
C4D=true

stylecheck.level=3 // must be set after c4d=true
stylecheck.aswarnings=false
stylecheck.max-linecount=300

// Custom ID
ModuleId=de.frankwilleke.dim4nsions

Why do these projects behave different?
Thanks in advance!

Cheers,
Frank

Ah, ok, yes that sounds reasonable. When would I do that? In Read(), Write(), and CopyTo()? And what exactly would I do? Simple getting the value and immediately setting it again probably wouldn’t change anything.

@m_adam said in Dynamic elements in a CYCLE, CYCLE empty after loading document?:

Within the GetDDescription, once you populated the cycle, be sure also to call SetParameter to actually set the value (be sure to store the currently active value by overriding NodeData::Write/NodeDataRead)

What exactly do you mean? Why should I do that?

Do be clear: Just because the user links an object that adds extra items to the CYCLE doesn't mean any of those extra items should be automatically selected. They should just be available in the CYCLE.