Hi Pim,

no, I don't think so.
Basically the Selection tag reacts to MSG_POINTS_CHANGED and MSG_POLYGONS_CHANGED, in the end adding or removing the needed amount of points or polygons in the selection array. But there's no information, what to do with for example additional points. And so it heavily depends on where the new points/polygons are added and also which tool does so, what the outcome for those selected entities will be.
Something that will probably be addressed in future with the CustomDataTag introduced in R20.

Cheers,
Andreas

Hi,

yes, this is still the "official" way to add separators to the Plugins menu.

Cheers,
Andreas

Hi,

unfortunately we can't help developing algorithms. So, what has been said here and in the Quaternion Rotation thread, is probably all we can contribute from MAXON's side.

Maybe somebody from our community is willing to step into this and help out?

Cheers,
Andreas

Hi,

please, do not delete discussions threads. The contained information might be valuable for future readers.

Cheers,
Andreas

Regarding the embedded description GUI, I was just thinking loudly. I understand your design decision completely.
And actually I didn't want to imply, you should store the Descriptions (after all these contain no values). I thought more of a combination of the GetParameter() approach (where you were lacking the information, which parameters exist) and the description code I suggested. So you could during your initialization (in your case probably, when the user drags a new tool onto the wheel) find out about all available parameters and with this prepare a BaseContainer to store whatever you need later on.

Cheers,
Andreas

Hi Andre,

by calling GetData() you receive a copy of the InExcludeData. By writing the changed data back via SetData() it should work as expected.

I turned this thread into a question.

Cheers,
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

Hi,

thanks for the insight. Sounds nice!
I wasn't aware you were looking for a C++ solution, as the initial post contained Python code and als the thread's tag said Python... well, now you'll port it yourself. ;)

If I may suggest something, after looking at the video. Why not simply show the description of the tool in your dialog (like the Active Object Manager example does)? Then the user could set all parameters in one step and save them to a preset with a click.

Cheers,
Andreas

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