COFFEE html sdk? Where

Helper

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

On 30/11/2002 at 07:04, xxxxxxxx wrote:

It is in the C++ Downloads Section. Here is the direct link to the HTML Files:
<[URL-REMOVED]>
And the WIn Help Files (which I prefer for you can find easier what you are searching for) :
<[URL-REMOVED]>
Best
Samir

[URL-REMOVED] @maxon: This section contained a non-resolving link which has been removed.

Helper

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

On 30/11/2002 at 07:10, xxxxxxxx wrote:

Is the COFFEESDK6302.zip the latest sdk documentation? I mean, does it contain the updates to release 8?
And you should already know I use Mac, Samir... what is that Win Help Files sujestion about?
Thank you for the response

Rui Batista

Helper

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

On 30/11/2002 at 07:16, xxxxxxxx wrote:

Is the COFFEESDK6302.zip the latest sdk documentation? I mean, does it contain the updates to release 8?
----------------------------------
Hi,
yes this is the latest documentation. Thought some things have changed (emulation purposes) there is no COFFEE Update for R8 yet.
Sorry, for the MAC thing. Forgot about it.
Best
Samir

Helper

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

On 30/11/2002 at 07:28, xxxxxxxx wrote:

yes this is the latest documentation. Thought some things have changed (emulation purposes) there is no COFFEE Update for R8 yet.
-----------------

There must be an update. For intance, the Display tag has new options. I want to know how to set them. This has changed in r8.

-----------------

Sorry, for the MAC thing. Forgot about it.

-----------------

No problem. Common mistake

Rui Batista

Helper

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

On 30/11/2002 at 07:38, xxxxxxxx wrote:

There must be an update. For intance, the Display tag has new options. I want to know how to set them. This has changed in r8.
_______________________
There is Definetely no update for COFFEE. And for COFFEE doesn´t support BaseLinks yet, it seems that it is impossible for now to set the display options, for you can´t access them through the basecontainer system with COFFEE anymore.
Same for some (any?) other basecontainer values. I.e. the source object for an instance object can´t be set anymore. (I do have this problem with my latest plugin too $:\$ ) and others.
Sorry.
Samir

Helper

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

On 30/11/2002 at 07:43, xxxxxxxx wrote:

That's just simply stupid!!
Lots of nice COFFEE tools will not be able to be updated
What was nice about C4D was that it allowed people with basic knowledge of programming (me!! and with a simple word processor to be able to create fine tools.
This is, somehow, closing the doors
And the removal of the "Reload Plug-ins" option is one of things that annoyed me the most

Rui Batista

Helper

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

On 30/11/2002 at 07:45, xxxxxxxx wrote:

Yes, I know. But there will be a COFFEE update in the future for sure. So it is not gone.
But the removal of the Reload Plug-Ins option is one thing I miss too.
Best
Samir

Helper

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

On 30/11/2002 at 07:48, xxxxxxxx wrote:

Now that I finaly succeeded in updating SpeeDisplay, I found that I also need to update the way the Display tags are set. Everything else is working fine. Now that I was so close I will have to wait for a COFFEE update Darn!!!

Rui Batista

Helper

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

On 01/12/2002 at 02:49, xxxxxxxx wrote:

There are still some things you can do with C.O.F.F.E.E. if you're willing to look up the IDs yourself. For example, consider Tdisplay.res:

    
    
    CONTAINER Tdisplay  
    {  
     NAME Tdisplay;  
     INCLUDE Tbase;
    
    
    
    
     GROUP ID_TAGPROPERTIES  
     {  
      COLUMNS 2;  
      BOOL DISPLAYTAG_AFFECT_DISPLAYMODE { }  
      LONG DISPLAYTAG_DISPLAYMODE  
      {  
       CYCLE  
       {  
        DISPLAYTAG_DISPLAYMODE_GOURAUDSHADING;  
        DISPLAYTAG_DISPLAYMODE_QUICKSHADING;  
        DISPLAYTAG_DISPLAYMODE_WIREFRAME;  
        DISPLAYTAG_DISPLAYMODE_ISOPARMS;  
        DISPLAYTAG_DISPLAYMODE_SHADEDBOX;  
        DISPLAYTAG_DISPLAYMODE_BOX;  
        DISPLAYTAG_DISPLAYMODE_SKELETON;  
       }  
      }  
      BOOL DISPLAYTAG_AFFECT_LEVELOFDETAIL { }  
      REAL DISPLAYTAG_LEVELOFDETAIL { UNIT PERCENT; MIN 0.0; MAX 1000; }  
      BOOL DISPLAYTAG_AFFECT_VISIBILITY { }  
      REAL DISPLAYTAG_VISIBILITY { UNIT PERCENT; MIN 0.0; MAX 100.0; }  
      BOOL DISPLAYTAG_AFFECT_BACKFACECULLING { }  
      BOOL DISPLAYTAG_BACKFACECULLING { }  
      BOOL DISPLAYTAG_AFFECT_TEXTURES { }  
      BOOL DISPLAYTAG_TEXTURES { }  
     }  
    }

And the corresponding Tdisplay.h:

    
    
    #ifndef _Tdisplay_H_  
    #define _Tdisplay_H_
    
    
    
    
    enum  
    {  
     DISPLAYTAG_DISPLAYMODE     = 1000, // LONG  
      DISPLAYTAG_DISPLAYMODE_GOURAUDSHADING = 0,  
      DISPLAYTAG_DISPLAYMODE_QUICKSHADING  = 1,  
      DISPLAYTAG_DISPLAYMODE_WIREFRAME   = 2,  
      DISPLAYTAG_DISPLAYMODE_ISOPARMS    = 3,  
      DISPLAYTAG_DISPLAYMODE_SHADEDBOX   = 4,  
      DISPLAYTAG_DISPLAYMODE_BOX      = 5,  
      DISPLAYTAG_DISPLAYMODE_SKELETON    = 6,  
     DISPLAYTAG_BACKFACECULLING   = 1001, // BOOL  
     DISPLAYTAG_TEXTURES       = 1002, // BOOL  
     DISPLAYTAG_LEVELOFDETAIL    = 1004, // REAL  
     DISPLAYTAG_VISIBILITY      = 1006, // REAL
    
    
    
    
     DISPLAYTAG_AFFECT_DISPLAYMODE   = 1007, // BOOL  
     DISPLAYTAG_AFFECT_BACKFACECULLING = 1008, // BOOL  
     DISPLAYTAG_AFFECT_TEXTURES    = 1009, // BOOL  
     DISPLAYTAG_AFFECT_LEVELOFDETAIL  = 1010, // BOOL  
     DISPLAYTAG_AFFECT_VISIBILITY   = 1012  // BOOL  
    };
    
    
    
    
    #endif

So by pasting the above you can still do things like:

    
    
    enum  
    {  
     DISPLAYTAG_DISPLAYMODE     = 1000, // LONG  
      DISPLAYTAG_DISPLAYMODE_GOURAUDSHADING = 0,  
      DISPLAYTAG_DISPLAYMODE_QUICKSHADING  = 1,  
      DISPLAYTAG_DISPLAYMODE_WIREFRAME   = 2,  
      DISPLAYTAG_DISPLAYMODE_ISOPARMS    = 3,  
      DISPLAYTAG_DISPLAYMODE_SHADEDBOX   = 4,  
      DISPLAYTAG_DISPLAYMODE_BOX      = 5,  
      DISPLAYTAG_DISPLAYMODE_SKELETON    = 6,  
     DISPLAYTAG_BACKFACECULLING   = 1001, // BOOL  
     DISPLAYTAG_TEXTURES       = 1002, // BOOL  
     DISPLAYTAG_LEVELOFDETAIL    = 1004, // REAL  
     DISPLAYTAG_VISIBILITY      = 1006, // REAL
    
    
    
    
     DISPLAYTAG_AFFECT_DISPLAYMODE   = 1007, // BOOL  
     DISPLAYTAG_AFFECT_BACKFACECULLING = 1008, // BOOL  
     DISPLAYTAG_AFFECT_TEXTURES    = 1009, // BOOL  
     DISPLAYTAG_AFFECT_LEVELOFDETAIL  = 1010, // BOOL  
     DISPLAYTAG_AFFECT_VISIBILITY   = 1012  // BOOL  
    };
    
    
    
    
    main(doc,op)  
    {  
      var tag = op->GetFirstTag();
    
    
    
    
     var bc = tag->GetContainer();  
      bc->SetData(DISPLAYTAG_DISPLAYMODE, DISPLAYTAG_DISPLAYMODE_ISOPARMS);  
      tag->SetContainer(bc);
    
    
    
    
     tag->Message(MSG_UPDATE);  
    }

The only time you're out of luck is when a type like BASELINK is used.

Helper

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

On 01/12/2002 at 03:33, xxxxxxxx wrote:

way cool! Didn´t know about that too. Thanks for clearing. So Rui, time to work
Samir

Helper

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

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

Already did it. I found out yesterday all that. Well, Paul Everett pointed me in the right direction. It is already working
Thank you all

Rui Batista