Stats

  • Replies 5
  • Subscribers 159
  • Views 13654
  • Members are here 0
More Content

blocking of Forms

SkilSiao

Hi, I want to create a form (my_form) that after it is displayed, the background functions or other opened forms cannot be activated again until this form (my_form) is closed. (Just like PackStack Editor, once it is opened, the rest of the functions are only available again when PackStack Editor is CLOSED).

my approach (to create) is like this,

my_form = axlFormCreate((gensym) "my_form.form" '("CENTER" "msglines" 1)  'my_form_Action nil nil)

the my_form comes with an "Ok" button to close the form and another action button for some updating tasks, and that is why i need a Callback function 'my_form_Action. The g_nonBlock i leave it as nil as per the description of the function, but this doesnt not seem working... Things are still able to be run with the my_form opened.

How shall go around with this? is there a way to pause everything first until my_form is closed? Thx in advance.

Parents

  • For a blocking form you typically don't need to use  axlFinishEnterFun()

    In your callback handler, _form_file1_action, on a done or cancel event assign a user attribute to the form handler. For example do:

        temp_form->MyFormIsDone = <my_value>

    In your main function (after the axlUIWBlock), you will be able to fetch the the value from temp_form->MyFormIsDone and return it.

    When assigning user attributes to the form handler (temp_form), capitalize the first letter to avoid any conflicts with pre-defined Cadence attributes.

Reply

  • For a blocking form you typically don't need to use  axlFinishEnterFun()

    In your callback handler, _form_file1_action, on a done or cancel event assign a user attribute to the form handler. For example do:

        temp_form->MyFormIsDone = <my_value>

    In your main function (after the axlUIWBlock), you will be able to fetch the the value from temp_form->MyFormIsDone and return it.

    When assigning user attributes to the form handler (temp_form), capitalize the first letter to avoid any conflicts with pre-defined Cadence attributes.

Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.