THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 15/10/2004 at 12:48, xxxxxxxx wrote:
User Information:
Cinema 4D Version: 8.5+
Platform: Windows ; Mac ; Mac OSX ;
Language(s) : C++ ;
---------
Howdy,
How do I check if a description element (link) already exists before creating it in GetDDescription()?
Adios,
Cactus Dan
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 16/10/2004 at 00:35, xxxxxxxx wrote:
I'm unclear about what you need to check for. If for a unique ID, then CheckDescID() might do the trick. If for a specific parameter ID, GetParameter() might work. (?)
BTW, thanks for your valuable assistance with creating Groups interactively in the A.M.! This stuff gets complicated with all of the description/basecontainer generalities. It only starts making sense after plugging at it for a while. :)
Robert
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 16/10/2004 at 08:03, xxxxxxxx wrote:
Howdy,
Well, don't worry. I was unclear when I asked the question (I was grasping at straws).
What I'm trying to accomplish is to have a tag create object link elements in the AM when the user clicks an "Add" button and have it subtract them when the user clicks a "Subtract" button. There aren't many specific examples here in the forum (according to the search parameters I was entering) and the only examples in the SDK are the AsyncTest (which is not an AM description) and the MorphMixer (which does not create additional elements via a button)
After going down the wrong track (trying to use a .res file and Show/Hide the elements) and finally figuring out how the MorphMixer actually works in Cinema 4D (no usage docs), I've switched tracks and I'm now creating the description elements in GetDDescription().
The tag has to somehow keep track of the elements that get added and subtracted, and like I said before, I was grasping at straws to solve this. But, as always I seem go down the wrong track until I fall flat on my face and then end up backtracking until I stumble over the answer. What I'm doing now is, using a global counting variable that increases and decreases it's value as the buttons are clicked, and then storing that variable's value in the tag's BaseContainter.
Since I'm only learning as I go and there seems to be no specific examples that do "exactly" what I'm trying to do and there is no one standing over my shoulder telling me, "Don't go down that track!", it seems to take me forever to accomplish something that looks like it should be a simple task.
But hey, whataya gonna' do?
Oh and, thanks for the response. Even though I've switched tracks, you've given me something new to study.
Adios,
Cactus Dan
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 16/10/2004 at 14:07, xxxxxxxx wrote:
That's the same method I'm using for my variable number of morphs - although I don't have an Add/Remove feature. The MorphMixer example uses polygonal objects and goes through them for every action, but in my case, it is easier to set up a group of indices (IDs) starting at a value. In order to know when to stop, I just store the last ID encountered during the GetDDescription process.
The lack of examples and other code makes every step a drudging process. I'm still waiting for an answer to my previous question and have found no solution after a couple of days of t&e.;
Good luck and keep plugin'
RObert