Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 13729
  • 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

abIPar.il issue of geGetTopLevelCellView() returning nil

DavidLou

hello experts,

happened to notice the code Andrew made in community.cadence.com/.../1323814 . 

we use this abIPar procedure to collect info from cdf parameters and display them in schematic/symbol. that's all working fine until I have ade session and when I click "run" in ade, all these display procedure go "nil" which traced down to this geGetTopLevelCellView() returning nil. once I do a re-draw then all the display come back to normal life again. 

so wonder why would geGetTopLevelCellView() fail in such occasion? 

P.S., both IC6.1.7-64b.500.21 and IC6.1.7-64b.500.9 have this problem. 

thanks,

David

Parents

  • Hi David,

    The reason is that there are several places in the code where it depends on the current window to determine the top cellView, the hierarchy path to this instance, the simulation session associated with the window and so on. Unfortunately (and this is a limitation since I originally wrote the code in 2003) it is not going to do the right thing if the window being redrawn is not the current window - which is quite likely when using ADE and running a simulation because it refreshes the schematic windows in case any annotations need to be redrawn.

    I'm doing some checks to determine whether I can make public the mechanism for determining the current display window and then I'll update the code.

    It's similar to a problem that  had recently in Annotations are just way too overpowering

    Regards,

    Andrew.

  • in reply to Andrew Beckett

    got it, thanks Andrew. keep us posted if viable options becoming available. 

    thanks,

    David

  • in reply to DavidLou

    Hi Andrew. Given that this thread is related to my other post, I was wondering if you've had any success on obtaining access to the current display window mechanism...

  • in reply to CADcasualty

    I know how it works right now, but we're having a discussion as to whether the current method should be made public or whether we should make something more sustainable/supportable. We always have to be careful about making an internal mechanism public without careful thought because then it comes with a reasonable expectation of future support. CCR 2061032 is asking for a public mechanism for finding the current display window, and that hasn't reached a resolution yet.

    Regards,

    Andrew.

Reply
  • in reply to CADcasualty

    I know how it works right now, but we're having a discussion as to whether the current method should be made public or whether we should make something more sustainable/supportable. We always have to be careful about making an internal mechanism public without careful thought because then it comes with a reasonable expectation of future support. CCR 2061032 is asking for a public mechanism for finding the current display window, and that hasn't reached a resolution yet.

    Regards,

    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.