THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 15/03/2007 at 11:07, xxxxxxxx wrote:
Cinema 4D Version:
Hallo plugin developers,
I currently collect ideas for additional SDK examples. So please feel free to tell me what areas in your opinion are most lacking.
On 15/03/2007 at 16:03, xxxxxxxx wrote:
Where to begin!
How about a TreeView example that doesn't rely upon the existing object manager structure (would be nice to see how all of the TreeViewFunctions might be employed with your own root and item classes) so as to show how to exploit it for other uses (I currently use four trees of varied purpose-function in my plugin)?
A thorough example of how to limit numeric entry (w/ and wo/ arrows) during user input so that not only are invalid inputs changed back but it is done either w/ or wo/ requiring TAB or ENTER.
More tag plugin examples - there is only one, has ever only been one, and will there ever be just that one? I use plugin tags so extensively, I could probably write the book on them!
***REQUIRED - MUST - PRIORITY - DO IT NOW!!!***
A comprehensive example of a hierarchical deformer plugin! I could almost write the book on that one (as could CactusDan - maybe we should collaborate?). Everything that I know about them was through utter trial and error as there is nigh an example and not much of an explanation in the SDK docs.
***REQUIRED - MUST - PRIORITY - DO IT NOW!!!***
Obviously, some examples of the more esoteric track types (time, PLA, etc.) for R10 when the SDK has fleshed them out.
Working with undos in exceptional circumstances. My plugin suite is so complicated, that undos are a constant nagging problem. I always want to support them, but the various circumstances don't always produce favorable results when a user performs an undo. There are even possible scenarios that will utimately cause a crash and there is no way to avoid it. Without any stack checking or any messaging, there is not a thing that I can do to avoid them (since complete control is now in the hands of C4D - which doesn't appear to check certain conditions before performing the undo).
I'd say that a cursory examination of this forum (All) should provide a wealth of areas that need examples - whether the information is elucidated here or not. Probably a few of the areas could be combined into a single example where relevant.
Just some ideas off the top of my head.
On 16/03/2007 at 12:25, xxxxxxxx wrote:
How to get skeleton-mesh vertex bind information for animation import/export will be very important for game developers specially.
On 17/03/2007 at 08:18, xxxxxxxx wrote:
That sounds good
How about some XPresso and TP examples?
On 17/03/2007 at 14:36, xxxxxxxx wrote:
one more tool plugin example please: One that makes more in the GetCursorInfo function than just set the bubble help.
On 18/03/2007 at 04:16, xxxxxxxx wrote:
I second everything and would like to see added:
- How to successfully use C4D_Falloff
- Mocca3 examples (CAJoingObject etc.)
On 18/03/2007 at 16:56, xxxxxxxx wrote:
My vote for advanced tool plugins which make use of viewport select, and keep data like that in a cache between calls.
If you are going to spend time on the sdk please make the maxon guys think again about a wikified docu, because there are so many undocumented issues.
On 21/03/2007 at 04:54, xxxxxxxx wrote:
What I really would love to see, were some more examples about exporting or even a little how to implement a render to Cinema (a little outline with instructions what you need to do to connect an render to cinema.)
On 23/03/2007 at 00:48, xxxxxxxx wrote:
I agreed with the above and I'd like to express the need for an example showing how to provide undo without polling, which is important when there is a need of knowing when there has been an undo or a redo on a specific object.
On 23/03/2007 at 01:23, xxxxxxxx wrote:
I need XPresso and GraphView examples.
On 23/03/2007 at 04:28, xxxxxxxx wrote:
One more vote for XPresso, GraphView and TP examples.
Thank you very much, frank.
On 26/03/2007 at 01:08, xxxxxxxx wrote:
Thanks for the all ideas. I really like the idea of the wikified SDK docu.
On 03/07/2007 at 07:36, xxxxxxxx wrote:
back to this.
how about some XPresso and TP examples?
Is this still active or not?
On 03/07/2007 at 09:13, xxxxxxxx wrote:
I'm also still interested in XPresso and TP examples.
On 03/07/2007 at 13:14, xxxxxxxx wrote:
I'd like to see more examples of some of the more obscure functions in the SDK, not necessarily as SDK project plugins, but more code snippets in the docs, maybe.
On 05/07/2007 at 08:49, xxxxxxxx wrote:
More code snippets in the docs would be extremely helpful as Dan mentioned...
I'd like to see a newer filter (3D import/export) plugin, showing processing some (more indepth) of the camera, materials and some of the matrix/animation type information that would be helpful for people writing game related (and other) import/export formats.
A wiki would be most welcome as well.
On 30/10/2007 at 09:13, xxxxxxxx wrote:
Hey Matthias, just wanted to know, if you did any kind of progress on your topic? Can we expect something new with the upcoming SDK?
On 31/10/2007 at 10:09, xxxxxxxx wrote:
I would definately have to agree that some Xpresso and TP node examples would be a tremendous help. This was the most confusing and unintuitive part of the SDK for myself. But, I would also like to see some Hierarchy Deformer / Generator exmples as well.
On 31/10/2007 at 11:39, xxxxxxxx wrote:
One thing I forgot to mention is that an example showing how to create a CustomGui would also be extremely helpful.