• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. How to correct use - ddsFileBrowseCB & Delete Field when...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 1366
  • 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 correct use - ddsFileBrowseCB & Delete Field when has hiCreateTabField

Charley Chen
Charley Chen over 11 years ago
 Dear All , 
 
In this code , if no  hiCreateTabField , it's correct , but when i use , it has 2 warning message.
 
;*WARNING* ddsFileBrowseCB: Invalid target string field: Field2; not found on the form
;*WARNING* hiDeleteFields: Can't find field Field4 in form Form. NO fields deleted.
 
How to fix the code ?
 
 
procedure( QQ()
       Field2 = hiCreateComboField(
       ?name 'Field2
       ?prompt "File Path"
       ?items list("This is a book.")
       ?value "This is a book."
       );

       Field3 = hiCreateButton(
       ?name 'Field3
       ?buttonText "Browse"
       ?enabled t
       ?callback "ddsFileBrowseCB(hiGetCurrentForm() 'Field2)"
      ;*WARNING* ddsFileBrowseCB: Invalid target string field: Field2; not found on the form 
       )

       Field4 = hiCreateButton(
       ?name 'Field4
       ?buttonText "Delete"
       ?enabled t
       ?callback "MyCB()"
       ;*WARNING* hiDeleteFields: Can't find field Field4 in form Form. NO fields deleted.
       )

       TabField1 = list(
list(Field2 5:00 200:30 70)
list(Field3 5:50 130:30 80) list(Field4 150:50 130:30 80)
      );

       TabField = hiCreateTabField(
       ?name 'TabField
       ?notebookStyle nil
       ?pageScroller nil
       ?tabPlacement 'top
       ?tabs list("Hello")
       ?fields list(TabField1)
       ?value   1
       )

       Form = hiCreateAppForm(
       ?name 'Form
       ?formTitle "Hello"
       ?fields list(list(TabField 0:0 640:150 110))
       ;?fields TabField1
       );hiCreateAppForm
       hiDisplayForm(Form 40:54)
);pro

procedure( MyCB()
    hiDeleteFields(Form
 list(
      'Field4
     );;list
    );hiDeleteFields
); 
 
 
Thank you,
Charley 
  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Hi Charley,

    When you have a tab field (or a scroll region for that matter), most functions that you call which reference a field within a page of the tab field (or within a scroll region) need to be passed the page instead of the top level form - effectively the page is like a sub-form.

    So the callback for Field3 should be:

            ?callback "ddsFileBrowseCB(hiGetCurrentForm()->TabField->page1 'Field2)"

    and your MyCB() function should be:

    procedure( MyCB()
        hiDeleteFields(Form->TabField->page1
     list(
          'Field4
         );;list
        );hiDeleteFields
    );

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Hi Charley,

    When you have a tab field (or a scroll region for that matter), most functions that you call which reference a field within a page of the tab field (or within a scroll region) need to be passed the page instead of the top level form - effectively the page is like a sub-form.

    So the callback for Field3 should be:

            ?callback "ddsFileBrowseCB(hiGetCurrentForm()->TabField->page1 'Field2)"

    and your MyCB() function should be:

    procedure( MyCB()
        hiDeleteFields(Form->TabField->page1
     list(
          'Field4
         );;list
        );hiDeleteFields
    );

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information