THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 29/04/2006 at 10:53, xxxxxxxx wrote:
It is his own PluginTag as is mentioned, so why is it not working (unless there is something not being shown which may be a contributing factor)? Of course, it is COFFEE, so I'm slightly out of my element.
Just to get a further clarification: You cannot declare a sub-BaseContainer in the .res file for a plugin resource, but you can store a sub-BaseContainer within your own PluginTag's BaseContainer as long as it has a unique ID (above 1000, 2000 for Shaders)?
From the docs, Description Resource:
Note: Generally it is safe to use IDs above 1000 in a local context like this one. However, for shaders you have to use IDs above 2000 to make room for the common radiosity IDs.
and from BaseContainer:
It is recommended that you use the available containers to store your own values as well. That way they will be automatically saved. However, if you want to store values in the top level of for example an object container, you'll have to use a unique id. You can use a plugin id from http://www.plugincafe.com for this. A good way is to store a sub-container with this id. Inside this sub-container you can use whatever ids you want.
I can tell you, this works - with my own PluginTags, of course. Or is it that for your own Plugins, you can just describe a unique ID in the .h enum for the to-be-added sub-BaseContainer, unmentioned in the .res, without requiring a unique 'plugin' ID acquired here?
Again, just looking for clarification on this.