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
    • Login

    Problems with GetDEnabling and BITMAPBUTTON

    Scheduled Pinned Locked Moved PYTHON Development
    3 Posts 0 Posters 308 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

      On 15/12/2014 at 13:18, xxxxxxxx wrote:

      If I add a BITMAPBUTTON to my container description, I always get an error if I overload the GetDEnabling method.
      It can be something as simple as:

      def GetDEnabling(self, node, id, t_data, flags, itemdesc) :
           return True

      But when I deselect my object (the one with BITMAPBUTTON gadgets in its description), I always get this error in the Console:

      AttributeError: Parameter value not accessible (object unknown in Python)

      Is there any way to prevent this error from happening?

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

        On 16/12/2014 at 06:23, xxxxxxxx wrote:

        Oh, by the way, this only happens in R14, so it is not such a big deal 😉
        At least I have been trying to reproduce this in R15 and R16 and it seems to be working fine.

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

          On 17/12/2014 at 08:25, xxxxxxxx wrote:

          Hello,

          yes, this was a bug in R14 that was fixed with R15.

          Best wishes,
          Sebastian

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