Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 12771
  • 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

modifying a pcell parm in the properties window using external editor?

TrevorB

Hi,

My pcells have some string fields, which require very large values.  It is tedious - er, impossible - to edit these huge values in the single-line text field for a string param in the "Properties" window.

So, I added a button param, which when pushed, uses the user's default "editor" to edit a tempFile representing the field's contents.

When the default editor returns, I parse the file's contents and update the string parm's value in both cdfgData and/or cdfgForm.  (It doesn't make a difference for this problem.)

Everything almost works.  The values are being sent and received correctly via the external editor.  And, the cdf is being modified correctly, just as I do in all my other callbacks.  However, the interim step of the external editor is throwing things off somehow...

In the Schematic composer, I see that the field is updated almost immediately after the editor closes with the editor's parsed contents.  However, any field, whose "editable" property is dynamically based upon a field updated by this process, does not have its "editable" status updated.

In the Layout window, it's worse.  Not only does the editable values not change, but the actual field values do not change - visibly.  Programmatically, I can see the change through cdfgData and cdfgForm, but the form is just not being updated.

In both cases, for the schematic and layout editors, if I just toggle any boolean field, the forms instantly and magically update all fields to the correct values!  ...  Hmmm, smells like a bug in form refresh code to me...

BTW, I make judicious use of the line:

cdfgForm->cdfModified = t

But, alas, that does not help.

What think ye?  :)  I was going to file an SR, but I thought I would first check the experienced minds here.  :-)

Thanks!

Trevor

  • Trevor,

    You shouldn't really touch cdfgForm - the usage of that is really not wise - the only case is for cdfgForm->cdfModified, which is supposed to ONLY be used in a formInitProc for a specific purpose (search for cdfModifed in the documentation).

    Sounds as if something is not working properly - best to contact Cadence Customer Support with an example to reproduce the problem - bit hard to diagnose without the code. Unfortunately I don't really have the bandwidth right now to recreate an example to try this out, and anyway if it's a bug, it really should be filed with you as the customer (customer CCRs get more attention than internal CCRs).

    Regards,

    Andrew.

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.