MULTISTRING syntax highlighting



  • On 10/08/2016 at 05:58, xxxxxxxx wrote:

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

    ---------
    Hi,

    I can set the PYTHON flag in a STRING element with a MULTISTRING customgui to get python code highlighting etc.

    Now I am wondering is there a flag for COFFEE highlighting as well? (The obvious answer would be the flags exhibited here: https://developers.maxon.net/docs/Cinema4DCPPSDK/html/gui_8h.html#a4ed4d0913429a6359403e7559cf4f115a71ec143d98d660d498b343ccbb5004d8 but these don't work)
    Also is there a flag to get rid of the status bar introduced by PYTHON (displaying line, pos info)?

    What other flags can be set for that matter? Unfortunately C4D Developer Help reference page is offline so I cannot look it up there.

    Thanks!



  • On 11/08/2016 at 01:18, xxxxxxxx wrote:

    Btw this is all concerning the resource file definition (not in code).



  • On 11/08/2016 at 02:15, xxxxxxxx wrote:

    Hi Samir,

    there's a difference for descriptions and dialogs.
    In a description a STRING gadget with CUSTOMGUI MULTILINE provides highlighting only for Python. And there are no means to switch of the status bar. Other supported flags: READONLY, WORDWRAP and SCALE_V.

    For dialogs there's the CustomGUI MULTILINEEDIT, which supports highlighting for Python and COFFEE (SYNTAXCOLOR). It's status bar can be switched on and off (STATUSBAR).



  • On 11/08/2016 at 04:42, xxxxxxxx wrote:

    Thanks for clearing this up Andreas. That solves it then.

    As a side note: I always wondered why there was this difference between description and dialog elements when it's basically all based on the same customgui (as this is not the only gui element with such differing options). Never understood that.



  • On 15/08/2016 at 08:11, xxxxxxxx wrote:

    Hi Samir,

    unfortunately I have no satisfying explanation for the differences between descriptions and dialogs. Probably historic reasons...


Log in to reply