• 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. Functional Verification
  3. Simvision plugin problem

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 13601
  • 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

Simvision plugin problem

vinay1
vinay1 over 9 years ago

Hi,

I'm trying out a small plugin for simvision.

Here the plugin expects a signal path from the user using tk entry widget, and assign it to a variabe sigPath.

I have tied this script as a command to a button which is invoked from .simvisionrc

The problem is the variable in the entry seems to be not created, as when I use it after this piece of code, it says unknown variable sigPath.

The same code works on wish. Can anyone suggest me what I'm doing wrong or is there any other method to solve this issue?


# Create a input box to get the signal name
catch {destroy .inpSigName}
toplevel .inpSigName
wm title .inpSigName "Signal addition"
wm geometry .inpSigName +10+10
frame .inpSigName.f1
frame .inpSigName.f2
entry .inpSigName.f1.eSigName -textvariable sigPath -width 100
button .inpSigName.f2.bSigName -text "OK" -command {destroy .inpSigName}
bind .inpSigName <Return> {.inpSigName.f2.bSigName invoke}
focus .inpSigName.f1.eSigName
pack .inpSigName.f1 .inpSigName.f2
pack .inpSigName.f1.eSigName
pack .inpSigName.f2.bSigName

# Wait for the input box
tkwait window .inpSigName

puts $sigPath

Edit: If I were to load the script from console I don't see this issue. But If I call the script as a proc from a button I see this issue.

-Thanks

Vinay

  • Cancel
  • vinay1
    vinay1 over 9 years ago
    Fixed the issue. The textvariable should be global.
    • 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