weird formInitProc error?

Discussion in 'Cadence' started by Raj, Jan 31, 2006.

  1. Raj

    Raj Guest

    I have a really weird problem...I have a custom skill function
    specified in the formInitProc. There is no skill error as part of this
    function. When I Q a instance that has already been placed, the edit
    object properties form opens up...but I keep getting a error that seems
    like it has to do something with the form height. Because if I
    set/unset the system/user/cdf toggle buttons, the error string also
    changes...

    *Error* difference: can't handle (959 - nil)
    *WARNING* CDF parameter function has problem.

    The 959 seems to have something to do with the height of the
    form...because this number changes based on the whether the
    system/user/cdf options are set/unset. There is no error while
    instantiating a new cell, only while querying to edit (the logic inside
    the custom skill function for instantiation and querying is the same).
    The error also goes away if I don't specify any function for
    formInitProc. Its almost like since I specify a function, some variable
    that is used to determine the form geometry is not getting set...I am
    100% sure that there is no error as part of the custom skill func.

    Any ideas?

    Thanks
    Raj
     
    Raj, Jan 31, 2006
    #1
  2. Raj

    Raj Guest

    One thing I noticed is that the cdfgForm->param and cdfgForm->prop dpl
    evaluate to nil when I specify the function in formInitProc. This is
    where the fieldHeight, fieldWidth props are stored, so may be this is
    what the tool is trying to access? I still don't know why these props
    are not available...
     
    Raj, Jan 31, 2006
    #2
  3. Raj

    CadGuyy Guest

    Raj,
    Which icfb version is this occuring on, platform?
    Have you tried it in an older version? Same problem?

    Can you post the formInitProc procedure here?
     
    CadGuyy, Jan 31, 2006
    #3
  4. Raj

    Raj Guest

    Hey CadG,

    Thanks for responding...

    I tried both 5141 USR3 and 5033 ISR1...same problem. The same custom
    function is used in another library and there is no problem there. The
    function has too many calls to in house functions, so there is no easy
    way to post that function here. I even tried putting print statements
    and the error is not within that function.

    I am almost convinced that its the missing cdfgForm->param and prop
    dpl's...but don'y know why they are missing or how & where to set them.
     
    Raj, Jan 31, 2006
    #4
  5. Try setting:

    _stacktrace=40

    and then seeing what the stack trace is when the error occurs. It might reveal
    something...

    Andrew.
     
    Andrew Beckett, Jan 31, 2006
    #5
  6. Raj

    Raj Guest

    Thanks Andrew. I will try that...
     
    Raj, Feb 2, 2006
    #6
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.