how to set the "dontBlock" attribute value of a LayoutForm

You do not need to set this. Layout forms are always non-blocking (i.e. hiDisplayForm returns immediately), whereas App forms were blocking by default and ?dontBlock t made them non-blocking. I can't see why you would use ?dialogStyle 'modal on just the layout form - that makes it modal which means that that everything is held until the form is OK'd and is effectively a way of making it block - which is the opposite of what ?dontBlock t does.

So in other words, Layout forms are already like creating an App form with ?dontBlock t without you needing to do anything.

Andrew

Thanks Andrew, Actually I want to set the layoutFrom like "?dontBlock nil", sorry for that unclear describtion.

If I set the LayoutForm to block  that I don't need to modify the "clear work code"

There's no supported mechanism to make layout forms blocking. In general, forms (even app forms) should be implemented to do any subsequent work in the ?callback function of the form rather than relying on the blocking nature of the form. For a start, this is needed for the Apply button to work on the form.

Why do you need the form to be blocking? There might be an alternative solution depending on the reason...

Andrew

Thanks for your replying, Andrew.

In a history project, the history code is trying to release some ipc process, reset some filed to default value and reset some global variable to nil,and also delete some forms that include "hiDeleteFrom(this_main_form)", those important actions relys on "?dontBlock t" currently.

But the code about those actions are too much that need to much effort to make sure that the behvaior keep same as I modified before.

Thanks,

James 

You could easily convert the cleanup work into a callback without having to restructure the code too much:

; this macro creates a callback for a form (which doesn't have one) which 
; only gets called on OK and Cancel (not Apply). It works by creating a 
; temporary function, which is used for both the OK and Cancel callbacks
defmacro(CCFcreateOKandCancelCB (form @rest body)
  let(((formVar gensym('formVar)) (cbVar gensym('cbVar)))
    `hiChangeFormCallback(
      ,form
      let(((,cbVar lambda((,formVar) unless(hiIsFormDisplayed(,formVar) ,@body))))
        list(,cbVar ,cbVar)
      )
    )
  )
)
    
procedure(test2()
  let((lb2 bt2)
    lb2 = hiCreateLabel(
      ?name 'lb2
      ?labelText "<b style='color:#cc0000;'>labelText2</b>"
    )
   
    bt2 = hiCreateButton(
      ?name 'bt2
      ?buttonText "bt2"
    )
    form2 = hiCreateLayoutForm(
      'form2
      "Test LayoutForm"
      hiCreateVerticalBoxLayout(
        'form2VBox
        ?items list(
          lb2
          bt2
        )
      )
      ?dialogStyle 'modal

    )

    ;clean work
    CCFcreateOKandCancelCB(form2 
      printf("Here: do some clear work and release some resources\n")
      ; can't delete the same form within it's own callback, so enqueue
      ; instead
      hiEnqueueCmd("hiDeleteForm(form2)")
    )

    hiDisplayForm(form2)
  )
)

I have a macro created to simply the creation of the anonymous function, and also to include the checks so that it only gets called when the form is no longer displayed (to prevent the Apply button from doing anything). I also use hiEnqueueCmd to delete the form because you can't delete a form within its own callback.

Might help...

Andrew

You could easily convert the cleanup work into a callback without having to restructure the code too much:

; this macro creates a callback for a form (which doesn't have one) which 
; only gets called on OK and Cancel (not Apply). It works by creating a 
; temporary function, which is used for both the OK and Cancel callbacks
defmacro(CCFcreateOKandCancelCB (form @rest body)
  let(((formVar gensym('formVar)) (cbVar gensym('cbVar)))
    `hiChangeFormCallback(
      ,form
      let(((,cbVar lambda((,formVar) unless(hiIsFormDisplayed(,formVar) ,@body))))
        list(,cbVar ,cbVar)
      )
    )
  )
)
    
procedure(test2()
  let((lb2 bt2)
    lb2 = hiCreateLabel(
      ?name 'lb2
      ?labelText "<b style='color:#cc0000;'>labelText2</b>"
    )
   
    bt2 = hiCreateButton(
      ?name 'bt2
      ?buttonText "bt2"
    )
    form2 = hiCreateLayoutForm(
      'form2
      "Test LayoutForm"
      hiCreateVerticalBoxLayout(
        'form2VBox
        ?items list(
          lb2
          bt2
        )
      )
      ?dialogStyle 'modal

    )

    ;clean work
    CCFcreateOKandCancelCB(form2 
      printf("Here: do some clear work and release some resources\n")
      ; can't delete the same form within it's own callback, so enqueue
      ; instead
      hiEnqueueCmd("hiDeleteForm(form2)")
    )

    hiDisplayForm(form2)
  )
)

I have a macro created to simply the creation of the anonymous function, and also to include the checks so that it only gets called when the form is no longer displayed (to prevent the Apply button from doing anything). I also use hiEnqueueCmd to delete the form because you can't delete a form within its own callback.

Might help...

Andrew

If the code that was following the hiDisplayForm needs to access local variables within the same function, you might want to consider moving the code to a file with a .ils suffix so that that the lambda that's created can see the variables in the same lexical scope.

Andrew

If the code that was following the hiDisplayForm needs to access local variables within the same function, you might want to consider moving the code to a file with a .ils suffix so that that the lambda that's created can see the variables in the same lexical scope.

Andrew