Topics created by ello

Hi ello,

no, you don't need to worry, the compiler won't check the remaining lines. It is a warning, we use internally to make people write better code. Usually smaller functions are easier to maintain and thinking about how to properly split and slice your code leads to better better results. By the way, compilers nowadays do quite a good job on inlining functions, so one does not need to be afraid of performance issues. But in the end this is probably also a matter of personal taste and so you can configure this in your projectdefinition.txt. See the Stylecheck options in our Project Tool documentation, there you have the option to set the maximum line count for functions (stylecheck.max-linecount=number).

Please consider the use of tags and of our Q&A system.

Cheers,
Andreas

@ello said in debugging question:

when i hover for example RNDOFFSET in visual studio i get enum <unnamed>::RNDOFFSET = 1029

does this unnamed part cause something?

No, it doesn't cause anything. It just means the symbol is defined in an unnamed enum. We avoid such nowadays (improved error checking, easier to debug), but they don't do any harm.

furthermore, since this is a plugin collection the name RNDOFFSET is indeed used with another id in another plugin. does this play a role? i thought that only included files are taken into account?

Well, I doubt so, but it may. The point is using unique IDs per BaseContainer. And to access a certain ID always with the same type (you could change the type, but let's leave this aside for now). So for a single BaseContainer Is try to make sure and check, that one ID (I mean the symbol or name like RNDOFFSET) is always accessed with the same type, and that no two symbols have identical ID values, so you do not access the same BaseContainer entry with two different names (lets say RNDOFFSET_INT and RNDOFFSET_VEC) but maybe different types.

here is a screenshot for the actual issue

From briefly looking at the screenshot on my mobile, it does not give me an additional clue. I recommend to add the debugger console to your layout. Usually we print some extra info there, when we run into a Critical Stop.

Bye,
Andreas

@s_bach thank you. i still am on my road... at least it solves the compiler error. i get quite some crashes after updating. guess this will take some time

thank you. i got this working. maybe there are even other places in my code where i can use this knowledge 🙂

thank you.

Hi,

while @mp5gosu already provided the answer, I'm just chiming in to mention, that I converted your thread into a question, see Q&A Functionality and also added a tag to this thread, see Read Before Posting.

Cheers,
Andreas

hm, in the sdk help it is mentioned under "api change list in r20"... scrolling down to lib_description.h

i installed VS2015 just for seeing if it works better with c4d. however, in 2017 i had a nice built output where i could sort errors and warnings. this isn't there in the 2015 version, or do i need to toggle it somewhere. cannot find

nevermind, found it 🙂