A Bindkey to Move the Selected Trace to a New Strip in ViVA

The old way

hiSetBindKey( "vivaGraph" "Shift <key>m" "_ddtExecuteAction(awvGetCurrentWindow()->vivaSession \"moveTracesNewStrip\")")

And the new way

Click to copy
Copied!

Comments

Post a Comment

Popular posts from this blog

Plotting Device Parameters (gm, vdsat, etc) Vs Time or Temp

Image
I feel like this has gotten more complicated. I think it might have been easier 10 years ago. Then again, I could be w. Go to resource: How to save and plot operating point parameters for Spectre simulator from ADE Explorer/Assembler In Explorer, you go to Outputs > To be Saved > Select OP Parameters Now, the schematic window is active and you can click on instances and each gets highlighted as you do. These get populated in the Assembler Outputs Setup You will see that the "Type" is not signal but oppoint. If you click on the Details field, it splits into two - the /whatever/deviceName is on the left, and on the new field on the right, you can enter parameters appropriate for that device, like vdsat, vth, cgs, etc.  The UI is very poor, but, on the right of this field is a button you can actually click to choose from a list. It'll even run a sim if necessary! If you want these plotted, you have to check the box to the right under the Plot column. Other gems Finding...
Read more

Why Isn't Your Layout Bindkey Working in Layout XL?

Unfortunately, the application type, or name, is "Virtuoso XL". So you might need an additional definition: hiSetBindKey("Layout" "Ctrl <Key>m" "toglImportSplitRseg()") hiSetBindKey("Virtuoso XL" "Ctrl <Key>m" "toglImportSplitRseg()") How do you get the Application type? hiGetAppType(window(enclosed_number))   When you see 12(23) in the lower left corner of a window, use 23 in this command in the CIW
Read more

veriloga Debugging - $strobe Vs $display

$strobe vs $display in Verilog and Verilog-A: Understanding the Difference Summary: $display prints immediately when called, while $strobe prints at the end of the current simulation time step. In mixed-signal simulations, $strobe often produces cleaner, chronologically ordered logs. Why timing of print statements matters In both Verilog and Verilog-A, simulation events can occur at the same time. This is common in mixed-signal designs where analog events, digital edges, and timers may coincide. Printing in the middle of these updates (as $display does) can lead to logs that look out of order. $strobe avoids this by printing only after all events for that time step have completed. Rule of thumb: Use $display for immediate, step-by-step debugging; use $strobe for clean, time-aligned logs. Key differences Task When it prints Best for Drawbacks $display Immediately when executed Inspecting execution ...
Read more