• 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. Single Tool or App for multiple DataFormats or viewType...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 149
  • Views 14264
  • 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

Single Tool or App for multiple DataFormats or viewTypes

Curtisma
Curtisma over 5 years ago

Hello:

I am defining several DataFormats in a data.reg.  I would like to be able to use a single application to open several views with different file extensions.  When I try to assign two different dataformat with different extensions to the same application, it doesn't work.  Only the last definition listed in the data.reg (format_B in the example) shows up when I try to create a new cell view.  When I try checking deGetAppInfo with the first defintion, deGetAppInfo("format_A") below, it comes back empty, but deGetAppInfo("format_B") gives the expected result. Do I have to make a unique App/Tool for every cellview?  I would prefer one application definition since all the views, each pointing to files with different extensions, use the same callback code to start the application since the application supports multiple formats.

Also, the deRegApp documentation refers to view subtypes and says you can sobclass any number of parent types.  However I couldn't find a definition to these terms or a clear explanation of what they are.  Is that just for inheriting the callbacks from the parent viewType or is there more to it?  Would it help with this issue?

data.reg for Example:

DataFormat format_A {
Pattern = *.extA;
Preferred_Editor = exampleEditor;
Default_Editor = exampleEditor;
dfII_ViewType = format_A;
Co_Managed = master.tag data.dm *.extC;
}

DataFormat format_B {
Pattern = *.extB;
Preferred_Editor = exampleEditor;
Default_Editor = exampleEditor;
dfII_ViewType = format_B;
Co_Managed = master.tag data.dm;
}

deRegApp code for Example:

when(!member("format_A" deGetAllViewTypes()) 
deRegApp(
?appName "exampleEditor"
?enableTrigger 'EnableTrigger
?dataTrigger 'DataTrigger
?viewType "format_A"
?appTrigger 'ViewAppTrigger
?widgetType "graphics"
)
)
when(!member("format_B" deGetAllViewTypes()) 
deRegApp(
?appName "exampleEditor"
?enableTrigger 'EnableTrigger
?dataTrigger 'DataTrigger
?viewType "notebook"
?appTrigger 'ViewAppTrigger
?widgetType "graphics"
)
)

Tool exampleEditor {  }

Regards,

Curtis

  • Cancel
Parents
  • Curtisma
    Curtisma over 5 years ago

    I am using IC6.1.8-64b.500.8.  I went ahead and submitted a support request.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Curtisma
    Curtisma over 5 years ago

    I am using IC6.1.8-64b.500.8.  I went ahead and submitted a support request.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Curtisma

    I don't think this can be done. You can't share the same application for different data formats. Using a parent viewType doesn't help because you have to declare the triggers anyway for each application - but you can share the functions.

    It's a bit of an unusual request - so probably best followed up via your support request (which was the best thing to do anyway for this question). Unfortunately I'd spent time looking at it and experimenting before I saw that you'd edited your post to say that you'd submitted a support request (I wouldn't have done otherwise as duplicating the work of a colleague doesn't make sense either for me or them).

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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