Amazing! Thank you again Andreas!

@mikeudin Thanks for making us aware. We'll change the link with the next docs update.

Hi, this sounds more like a TR issue and not so much an SDK problem. If so, then I suggest to rather use the How Can We Help? form on MAXON's homepage. Cheers, Andreas

Thank you very much for your support !

Working as expected now ... didn't think of playing with the PLUGINTYPE_xxx Thanks for details.

Hi Roger, yes, you are right, this seems a bit strange on first sight. But the entire concept of VideoPostData providing C++ functions to extend the render pipeline does not hold for a GPU renderer nor the viewport display (which in the end is used for the preview renderers). This doesn't make it any better, but may at least explain the current inconsistency on our side. I'm confident at least for ProRender this is being looked into, but I can't say anything nor make any promises about future developments. Cheers, Andreas

@m_adam Thank you for your team's reply. I will share my exploration in this post in the future.

Hi, I'm afraid @Cairyn already contributed everything we could. We need to leave this to the community. Sorry. I have moved this to the General Programming & Plugins Discussions category, as I don't regard it as a very C4D specific question. Please, correct me, if I'm wrong. Cheers, Andreas

Sorry, in contrary to what I had written here before, we will not add RestartApplication() to the documentation. These calls have certain intricacies, so their use will be at own risk. This is now based on an answer from our development. Cheers, Andreas

I forgot to turn this thread into a question. Done now, and as I regard the last post as a "solved" message, I also marked it as solved. Please, don't hesitate to turn back to unresolved, if I was wrong.

Hi @C4DS, thanks a lot for your message. Documentation tag have been added. Drag and Drop Manual, changed to: GeDialog Drag and Drop GeUserArea Drag and Drop GUI Message Drag and Drop Links will work correctly in the next update of the doc. However you are right, the code sample in the old manual was wrong. It should have been if (CheckDropArea(DLG_GROUP, msg, true, true)) {} Note, you could also create your own function as demonstrated in the AsyncTest Example. Cheers, Maxime.

Thanks, @C4DS for pointing out this issue. It will be fixed in the next version. Cheers, Maxime.

Nice, congrats I have to admit, I forgot to turn this thread into a question. I did so now and I also marked it as solved, as your last post seems to imply. Cheers, Andreas

Hi Andreas, Thank you very much! It works like a treat and I appreciate your thorough explanation! Happy Friday! Andre

That's great, Andreas. Thanks! I'll kludge on until then.

Thanks to both of you. I originally thought solution 2 would be the way to go, and have proceeded in that direction ... but the more I look at the result the more I am getting convinced that this wasn't the right approach to deal with the issue. So, I am still open for solution 1. But will try yet another solution, inspired by the reply from WickedP. I intentionally didn't include a solution where I would create iCustomGui / GeUserArea for each separate gadget. As I thought this would result in drag and drop to only work when hovered over the separate gadgets, and failing when mouse would hover over the space between these gadgets. But using a global drag and drop function on the dialog itself (instead of all separate gadgets) will actually provide for a complete solution. EDIT: Set the state of this post to "Solved". In the end I went for a complete different solution. Not using any GeUserArea at all. As such, I could simply position and use EditText the way it was intended.

Hi Steve, having the USE_MAXON_API being defined - actually using C4D=true in projectdefinition.txt - is required in order to be sure that all the cinema.framework classes are properly compiled. Although there could be situations where some cinema.framework classes can work without that define, we highly discourage this approach since you can end up in situations where the code compiles until you include that specific class which indeed needs that define (which it's already happening in that case). If specifying C4D=true actually brings too much pain, please open a new thread and let's proactively discuss the issues your code is facing and let's get rid of them. Best, Riccardo

Hi Florian, sorry, to hear about this issue. To be honest, I can hardly believe that it's those parameters or sliders causing a crash on plugin registration. I'm more thinking of some memory maybe being trashed beforehand. But in the end, it doesn't matter so much, what I do believe or not or what I might suspect, we want to assist you in solving this riddle. As we have no evidence for issues in the described area, nor are we able to reproduce it via a simply example, I'd like to ask you for some more information. Could you maybe provide us with a stack trace, when the crash happened? Either from within Visual Studio or via the crash reporter (in the latter case, please notify me here, I need to look out for the report). I have turned this thread into a question. Cheers, Andreas