delete in link desc



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 12/12/2002 at 11:24, xxxxxxxx wrote:

    User Information:
    Cinema 4D Version:   8.012 
    Platform:   Windows  ;   
    Language(s) :     C++  ;

    ---------
    How can I retrieve the info if the object in a LINK description was deleted from the popupbutton (that belongs to the LINK description)? I couldn´t find out yet. :\ dcu->result or dcu->element isn´t NULL when I use the delete entry. So how can I check if there is a deletion?
    Thanks
    Samir



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 13/12/2002 at 05:30, xxxxxxxx wrote:

    What "delete" entry? If you mean the "Clear" entry in the triangle menu of the LINK field, do you get a MSG_DESCRIPTION_CHECKDRAGANDDROP message when you choose it? I don't, so I cannot reproduce your problem.



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 13/12/2002 at 05:45, xxxxxxxx wrote:

    What "delete" entry? If you mean the "Clear" entry in the triangle menu of the LINK field, do you get a MSG_DESCRIPTION_CHECKDRAGANDDROP message when you choose it? I don't, so I cannot reproduce your problem.

    yes, I mean the clear entry (sorry, german gui active). And yes I do receive a message when choosing it.
    if (type == MSG_DESCRIPTION_CHECKDRAGANDDROP)
        {
      
          DescriptionCheckDragAndDrop *dcu = static_cast<DescriptionCheckDragAndDrop*>(data);
          switch (dcu->id[0].id)
          {
       
             case DPT_BASE_FOUND: //LINK field ID
             if(!dcu->element) GePrint("NULL");
             GePrint("test ");
             return TRUE;
          }
        }
    Prints out a "test" when choosing the clear entry the first time but it never prints "NULL".



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 13/12/2002 at 05:58, xxxxxxxx wrote:

    ok, don´t know why but suddenly I don´t receive any messages anymore. But the link is still there. It isn´t cleared. So when and where do I have to set the link in the vdata BaseContainer to NULL?

        
        
        BaseTag    *tag  = (BaseTag* )node;  
         BaseContainer *vdata = tag->GetDataInstance();
        
        
        
        
         if (type == MSG_DESCRIPTION_CHECKDRAGANDDROP)  
            {  
            
              DescriptionCheckDragAndDrop *dcu = static_cast<DescriptionCheckDragAndDrop*>(data);  
              switch (dcu->id[0].id)   
              {  
              
            case DPT_BASE_FOUND:  
          
            if(!dcu->element) GePrint("NULL");  
                  vdata->SetLink(DPT_DRAG_OBJECT,(BaseObject* )dcu->element);  
             
            break;  
             
                return TRUE;  
              }  
            }
    

    Thanks
    Samir



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 13/12/2002 at 06:01, xxxxxxxx wrote:

    Arghh, ok got it. I used another ID for the container. Now I use the LINK id and it works. Thanks!



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 13/12/2002 at 06:04, xxxxxxxx wrote:

    This is very strange. I only get this message during drag and drop. Where is this description used? (I used the Atom object for my tests, with this function:

        
        
        Bool AtomObject::Message(GeListNode *node, LONG type, void *t_data)  
        {  
         if (type == MSG_DESCRIPTION_CHECKDRAGANDDROP)  
         {  
          DescriptionCheckDragAndDrop *dcu = (DescriptionCheckDragAndDrop* )t_data;  
          GePrint(LongToString(GeGetTimer()) + "  dcu->id[0].id: " + LongToString(dcu->id[0].id) +   
           "  dcu->element: " + LongToString((LONG) dcu->element));  
         }  
         return TRUE;  
        }
    

    )



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 13/12/2002 at 06:04, xxxxxxxx wrote:

    I knew I should have waited longer before opening this thread... ;-)



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 13/12/2002 at 06:07, xxxxxxxx wrote:

    I knew I should have waited longer before opening this thread... ;-)

    *g..ashamed* sorry. :)


Log in to reply