Stats

  • Locked Locked
  • Replies 6
  • Subscribers 144
  • Views 14438
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Preventing a form from unmapping till the user wishes

mana

 Hi

Iam designing a GUI for an application. I have used the hiCreateAppForm function in it to create a  form. By default, the form gets unmapped once the user presses OK. In case the user again wants to give inputs with minor changes in the fields, he has to fill the entire form all over again. So i wanted to keep some option to keep the form mapped on screen with all the fields having previous values filled in them, till the user himself gives instruction to fill a fresh form. I was looking for some argument in the hicreateAppForm function or a seperate function to enable such a thing. 

So if I may get some suggestions on the same.

 

Parents
  • mana
     @derek

    I have incorporated apply button in my form, m getting the same error as mentioned in the previous post, on pressing the apply button.

    *Error* get/getq: first arg must be either symbol, list, defstruct or user type - 2

     The above error is flashed whenever any of the field is changed and apply button is pressed after the code has been executed once. The apply button works fine when the code is executed for the first time.

    Thanks alot for ur inputs! :)

     
Reply
  • mana
     @derek

    I have incorporated apply button in my form, m getting the same error as mentioned in the previous post, on pressing the apply button.

    *Error* get/getq: first arg must be either symbol, list, defstruct or user type - 2

     The above error is flashed whenever any of the field is changed and apply button is pressed after the code has been executed once. The apply button works fine when the code is executed for the first time.

    Thanks alot for ur inputs! :)

     
Children
No Data

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.