SetDefaultColor, list of id's GUI elements use

On 15/01/2016 at 05:18, xxxxxxxx wrote:

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

---------
Hi guys,

Is there a document that lists the interface colors that Dialog elements use? e.g. Button uses COLOR_TEXT_BUTTON and COLOR_TEXT_BUTTON_DISABLED, EditText has COLOR_TEXT_EDIT, etc.

I want to colorize some elements on a dialog I'm working on, but it's tedious doing trial and error to figure out which color id to swap out.

regards,
-gene

On 15/01/2016 at 08:12, xxxxxxxx wrote:

Something like that?  https://developers.maxon.net/docs/Cinema4DCPPSDK/html/c4d\__colors_8h.html

Never mind, misunderstood your question. Yes, a document that describes which widget uses which
color IDs would be useful indeed.

On 15/01/2016 at 08:42, xxxxxxxx wrote:

These values are not strict.  The actual colors are determined by the user (or defaults) under Preferences:Scheme Colors.

On 15/01/2016 at 10:14, xxxxxxxx wrote:

I mean the second argument in SetDefaultColor( ELEMENT_ID, COLOR_TEXT_EDIT , Vector(1.0) );

Those IDs do read the corresponding scheme colors. The thing is, each type of dialog element uses certain IDs, and I don't know if there's any documentation that lists those.

On 15/01/2016 at 10:38, xxxxxxxx wrote:

Unfortunately, not only is the API documentation lacking 'definitions' of what these actually represent beyond the naming convention, the Cinema 4D Help under Preferences:Scheme Color lacks descriptions as well.  There doesn't appear to be a correlative index between the two.  For instance, while it seems that 'General - Text - Edit' is probably COLOR_TEXT_EDIT, your guess is as good as mine.  Such a correlative index reference would be nice though.

On 18/01/2016 at 10:04, xxxxxxxx wrote:

Hi,

we are aware that the documentation is bad on this topic, nevertheless good to point it out. We have it on our list, unfortunately way down, as we currently deem other parts of documentation more important.

On 18/01/2016 at 23:31, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Hi,

we are aware that the documentation is bad on this topic, nevertheless good to point it out. We have it on our list, unfortunately way down, as we currently deem other parts of documentation more important.

Thanks Andreas. It's great to know it's on the to-do list.