THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 08/11/2006 at 05:11, xxxxxxxx wrote:
Cinema 4D Version: 9.6
Platform: Windows ;
Language(s) : C++ ;
Months after the release of my Riptide plugin update to support ngons, it has just now come to my attention that apparently ngon support was broken (in my plugin) back when 9.6 was released (I hate it when users don't report bugs!).
Anyway, I noticed that my plugin was broken when I tried it with R10 demo and then finally had a similar report from a R9.6 user (I'm still on 9.1 here). I went looking through the R9.6 SDK docs to see what changed and noticed the "GetNgon() renamed to GetAndBuildNgon()".
Apparently, this also means that a R9.102 SDK compiled plugin using op->GetNgon() no longer functions (? why no backward compatibility?).
I'm not sure if anything else about ngons changed between 9.1 and 9.6 (I didn't se any mentions of ngons in the 9.5 docs), so I thought I'd check here first to see if anyone has insight on this.
* was this a simple name change?
* did any of the underlying ngon structures/calls/formats change as well?
* any reason why a R9.102 SDK compiled plugin using op->GetNgon() no longer functions? (was there some other reason for removing that code entry point?)
On 08/11/2006 at 05:35, xxxxxxxx wrote:
...just for reference, this thread here: http://www.plugincafe.com/forum/display_topic_threads.asp?ForumID=4&TopicID=2248 is a refresher on the various things I'm doing with ngons in my code... which is why I'm asking up front whether anything else about ngon handling changed.
On 08/11/2006 at 05:56, xxxxxxxx wrote:
yes, I think this was the only change. At least I didn´t encounter anything else from simply changing the name in my code.
On 08/11/2006 at 09:22, xxxxxxxx wrote:
Damn. I hate having to compile and maintain yet another (9.6 specific) version of my plugin because of a simple function name change. I wonder if they changed anything else between R9.6 and R10...
I was just thinking that maybe I could change my 9.1 code to use NgonBase->GetNgon(), instead of op->GetNgon(), but the problem is that apparently (from my previous discussions), you have to call op->GetNgon() (or now op->GetAndBuildNgon()) to ensure that NgonBase is created/valid - which I guess explains the name change of the op call... sigh.