Dialogs, a beginner's problems



  • On 01/07/2013 at 23:51, xxxxxxxx wrote:

    Couldn't read the whole thread so sorry if this has been claryfied before.

    You have to distinguish between descriptions and dialogs! Both (can) use resource files, but they
    look completely different! GetDDescription(), GetDEnabling(), etc. are methods that can be overwritten
    by a NodeData plugin. And NodeData plugins use descriptions.

    Originally posted by xxxxxxxx

    if(modeReadOnly)
    {
       AddStaticText(DLG_TEXT_SELECTED_FILE, BFH_LEFT, 400, 0, "", BORDER_THIN_IN);
    }
    else
    {
        AddEditText(DLG_TEXT_SELECTED_FILE, BFH_SCALEFIT, 0, 0);
    }
    

    If you want to disable dialogs elements, you can use the Enable() method of the GeDialog class.

    If you want a specific region in your dialog to be dynamic, you can use LayoutFlushGroup() to
    remove all the elements in a specific group and move the widget-insertion-pointer directly into
    this group.

    I almost always use resource files.

    -Niklas



  • On 02/07/2013 at 00:04, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    If you want to disable dialogs elements, you can use the Enable() method of the GeDialog class.
    If you want a specific region in your dialog to be dynamic, you can use LayoutFlushGroup() to
    remove all the elements in a specific group and move the widget-insertion-pointer directly into
    this group.
    I almost always use resource files.

    Great, I was not aware of this.
    I also use resource files for tags, but for this modal dialog, I found dynamic creation of elements to be perfect.


Log in to reply