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
    • Unread
    • Recent
    • Tags
    • Users
    • Login

    GeDialog::SetX problems

    SDK Help
    0
    3
    282
    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
      Helper
      last edited by

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

      On 14/03/2004 at 23:14, xxxxxxxx wrote:

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

      ---------
      I've found that GeDialog::SetLong, etc always return FALSE, even when
      they succeed.

      This used to only happen to me under WinXP (which has been C4D v8.5
      for some time), but now happens under MacOSX, too (since upgrading to
      v8.5).

      Has anyone else seen this?

      .angus.
      PS: I've only tried this using GeModalDialog

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

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

        On 15/03/2004 at 17:14, xxxxxxxx wrote:

        Yeah, I verified this. Actually this even turned out to be the cause of some subtle bugs introduced in my MSA plugin for 8.5, since many functions checked those return values. (Note to self: always fail early to avoid such bugs.)

        I've asked the developers if they have any good explanations, but either way the only workaround would seem to be to ignore the value. (Possibly pairing each Set-call with a Get-call to verify the value.)

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

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

          On 16/03/2004 at 02:49, xxxxxxxx wrote:

          As suspected, there is a bug in the current C4D version. So I'd advise everyone to ignore the return value of those functions. Also, please note that one unfortunate side-effect of the bug is that SetVectorReal() will only write the first value so that function can't be used.

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