Maxon Developers Maxon Developers
    • Documentation
      • Cinema 4D Python API
      • Cinema 4D C++ API
      • Cineware API
      • ZBrush Python API
      • ZBrush GoZ API
      • Code Examples on Github
    • Forum
    • Downloads
    • Support
      • Support Procedures
      • Registered Developer Program
      • Plugin IDs
      • Contact Us
    • Categories
      • Overview
      • News & Information
      • Cinema 4D SDK Support
      • Cineware SDK Support
      • ZBrush 4D SDK Support
      • Bugs
      • General Talk
    • Recent
    • Tags
    • Users
    • Register
    • Login

    HowTo: message id -> message name

    Scheduled Pinned Locked Moved SDK Help
    2 Posts 0 Posters 215 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • H Offline
      Helper
      last edited by

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

      On 20/12/2004 at 01:59, xxxxxxxx wrote:

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

      ---------
      I sometimes had the problem, that i knew the id of a message that seemed to be suited for the event I need to detect, but I didn't know the name of the message. Sometimes you get a result if you do a text search with the id on the cinema resource folder. But many messages are not defined with a long value, but by a 4 char value.
      If you need to search them:
      Take the id, convert it to hex, take each byte and convert it to char ( see www.unicode.org ) and search for that string in the resource folder.
      Example: id 1835755116 -> 6D 6B 66 6C -> m k f l -> search for 'mkfl' ->BFM_MARKFORCELAYOUT

      1 Reply Last reply Reply Quote 0
      • H Offline
        Helper
        last edited by

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

        On 20/12/2004 at 07:02, xxxxxxxx wrote:

        I have noticed this as well - just another level of obsfuscation to make our work and debugging all the more arduous. 😕

        Thanks for making this info available for others to decipher!

        Robert

        1 Reply Last reply Reply Quote 0
        • First post
          Last post