Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 10017
  • 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

How to use ddsSyncWithForm and procedure in call back function

saurabh96

Hello everyone,

i have made library string field and browse button through cell user can selects library and cell name.

as user clicks browse option library window opens , user selects lib and cell and close the window ...now i want as soon user press close button on lib window then procedure starts to run.

lib_view_Label=hiCreateLabel(
?name 'lib_view_Label
?labelText "Library Name*"
?justification 'left
)
lib_view_Entry=hiCreateStringField(
?name 'lib_view_Entry
?enabled nil
)

cellLabel=hiCreateLabel(
?name 'cellLabel ?labelText "Cell Name*"
?justification 'left
)
Topcell=hiCreateStringField(
?name 'Topcell
?value ""
)

browse=hiCreateButton(
?name 'browse
?buttonText "Browse..."
?enabled nil
?callback "(ddsSyncWithForm (hiGetCurrentForm) 'browse 'lib_view_Entry 'Topcell )"             ;;;;;;;;;;;;;;;i want that when user selects lib and cell and as closes the lib window runout procedure gets start
"runout(hiGetCurrentForm())"
)

how to sync both above?

thanks in advance

  • Normally you'd trigger some action on the form by having a callback on the form itself (i.e. the hiCreateAppForm/hiCreateLayoutForm) and then the OK/Apply button would trigger the action.

    There isn't a specific callback for when the library browser has been closed, but you could (if you really wanted it to work this way) use a callback on the lib_view_Entry and Topcell fields which would then get fired when either of these changed. This would be triggered when you either type in a new value on the form, or select something in the linked library browser. You would probably need to have your callback check that neither of the two fields was blank (e.g. using blankstrp() or just ==""), but personally I think this would be a strange use model as if somebody mis-clicked something in the browser, it would run automatically - which is unlikely to be desired.

    Better to have an explicit action - either the OK/Apply on the form, or an additional button on the form.

    Andrew

  • in reply to Andrew Beckett

    Hello Andrew,

    Thanks for a response..above issue has been solved previously

    Regards,

    srv

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.