Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 3750
  • 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

[ CCSChangeTrace]change default style and thickness of waveform/trace in ViVA XL-- Does NOT work for expression plot.

RFStuff

Dear All,

I gone through the link https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1Od0000000nWAKEA2&pageName=ArticleContent.

I have used CCSChangeTrace("thickLine") in CIW. 

When I added the lines 

In .cdsenv

asimenv.plotting  useDisplayDrf  boolean  nil

In .cdsinit

envSetVal("asimenv.plotting" "useDisplayDrf" 'boolean nil ) .

With the above addition, CCSChangeTrace didn't work.

I then removed envSetVal("asimenv.plotting" "useDisplayDrf" 'boolean nil ) .

With that, CCSChangeTrace("thickLine") did work for wave data as below. But, it did not work for the expressioin (the left sub-window wave plot).

Can anybody please tell how to fix this issue.

Parents

  • The article talks (in the problem section) about two env vars that can control the default thickness and line style. These normally only affect expressions and not signals that are plotted (it says that) unless the useDisplayDrf is set to nil. If. you do that, the two env vars affect both expressions and signals - the downside is that the highlighting of the nets on the schematic will not match the colours they are plotted in when plotting signals - but you do have control over the linestyle/thickness.

    The other approach (using CCSChangeTrace) is alternating the display.drf packets in memory in a way that means the colours/lineStyles/thicknesses will match the schematic probing (provided you've left useDisplayDrf at t). This will not affect the plotting of expressions though, because these don't ever use the display.drf packets because there's no need for them to match schematic probing, as the schematic is not probed for an expression. Instead, expressions will always honour the values of the lineThickness/lineStyle env vars, regardless of the setting of useDisplayDrf.

    I just re-tested this to make absolutely sure that this was still the case (it is).

    Andrew

Reply

  • The article talks (in the problem section) about two env vars that can control the default thickness and line style. These normally only affect expressions and not signals that are plotted (it says that) unless the useDisplayDrf is set to nil. If. you do that, the two env vars affect both expressions and signals - the downside is that the highlighting of the nets on the schematic will not match the colours they are plotted in when plotting signals - but you do have control over the linestyle/thickness.

    The other approach (using CCSChangeTrace) is alternating the display.drf packets in memory in a way that means the colours/lineStyles/thicknesses will match the schematic probing (provided you've left useDisplayDrf at t). This will not affect the plotting of expressions though, because these don't ever use the display.drf packets because there's no need for them to match schematic probing, as the schematic is not probed for an expression. Instead, expressions will always honour the values of the lineThickness/lineStyle env vars, regardless of the setting of useDisplayDrf.

    I just re-tested this to make absolutely sure that this was still the case (it is).

    Andrew

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.