Resource Conflict



  • On 30/08/2017 at 02:07, xxxxxxxx wrote:

    User Information:
    Cinema 4D Version:   R15-R18 
    Platform:   Windows  ;   Mac OSX  ; 
    Language(s) :     C++  ;

    ---------
    Hi,

    two plugins providing an object generator with the same type name (Ovolume) get into conflict. Only the plugin that is loaded first, is shown properly in the attribute manager. The other one only shows the basis properties. I have tested with R15 to R18 under MacOS and Windows.

    Is this a C4D bug, or is it a known issue, or do I miss s.th.?

    Thank you for any hints.



  • On 30/08/2017 at 03:38, xxxxxxxx wrote:

    The object type name is actually the plugin id. You cannot have the same plugin id twice - there's your error.



  • On 30/08/2017 at 04:16, xxxxxxxx wrote:

    No, that's not the point. The Plugin-IDs are different. I think the problem is the 5th parameter when registering, since it is defined as string.

    RegisterObjectPlugin(ID_VOLUME, name, PLUGINFLAG_HIDEPLUGINMENU, Volume::Alloc, "Ovolume", AutoBitmap("volume.tif"), 0);
    

    The plugins come from different developers using unique IDs. The only thing that both plugins have in common, is the name "Ovolume".



  • On 30/08/2017 at 05:34, xxxxxxxx wrote:

    It's a know limitation.

    Tdisplay"  cannot be used for 2 different descriptions. See Description Resource for more information.

    The best workaround is a bit borring but I really suggest you to do it.
    Is to prefix all your ressources and external variables that will be included into c4d.

    Personnaly I do graph_Opluginname



  • On 31/08/2017 at 02:24, xxxxxxxx wrote:

    gr4ph0s is right. A description name needs to be unique. We will try to make this fact more obvious in the documentation.
    Regarding the naming scheme, maybe it's worth sticking to the one provided in docs and then adding on top (so maybe rather Ographos_pluginname). But in the end, you are of course free to name your resources as you want to (with the exception of name conflicts that is).



  • On 31/08/2017 at 02:33, xxxxxxxx wrote:

    Thanks. Yes you're right, this issue needs to be more clearly in the docs.


Log in to reply