Is there any tool to show what are inside a prop.xx file?

M

m.deng

Guest
It's hard to figure out what have been set for a cell from the UI.

Ming
 
In the library manager, middle mouse ->edit properties or view properties over
the library (gives you library prop.xx), cell (gives you cell prop.xx) or view
(gives you view prop.xx)

That's fairly easy...

Andrew

On Wed, 16 Feb 2005 13:14:29 -0500, "m.deng" <mingdeng@rogers.com> wrote:

It's hard to figure out what have been set for a cell from the UI.

Ming
 
Andrew Beckett wrote:
In the library manager, middle mouse ->edit properties or view properties over
the library (gives you library prop.xx), cell (gives you cell prop.xx) or view
(gives you view prop.xx)

That's fairly easy...

Andrew

On Wed, 16 Feb 2005 13:14:29 -0500, "m.deng" <mingdeng@rogers.com> wrote:


It's hard to figure out what have been set for a cell from the UI.

Ming


Thanks. The Cadence UI is quite unfriendly, showing a several kilo byte
long string in such a short single line text field, :)

Ming
 
m.deng wrote:

Thanks. The Cadence UI is quite unfriendly, showing a several kilo byte
long string in such a short single line text field, :)
'cdfDump' may be your friend ...
 
You can also use my bit of SKILL
code which provides a UI to the SKILL 'cdfDump'
command.

See link below:
http://groups.google.de/groups?hl=de&lr=&selm=3E5219C0.3F75EF95%40xignal.de&rnum=7m.deng


Bernd
 
On Wed, 16 Feb 2005 16:19:43 -0500, "m.deng" <mingdeng@rogers.com> wrote:

Andrew Beckett wrote:
In the library manager, middle mouse ->edit properties or view properties over
the library (gives you library prop.xx), cell (gives you cell prop.xx) or view
(gives you view prop.xx)

That's fairly easy...

Andrew

On Wed, 16 Feb 2005 13:14:29 -0500, "m.deng" <mingdeng@rogers.com> wrote:


It's hard to figure out what have been set for a cell from the UI.

Ming


Thanks. The Cadence UI is quite unfriendly, showing a several kilo byte
long string in such a short single line text field, :)

Ming
From this comment, I assume you're talking about looking at the cdfData
property. That's about the only lengthy Cadence-generated property - others
would tend to be generated by non-Cadence apps, perhaps.

If it is CDF, then you should use Tools->CDF->Edit from the CIW. That shows
the CDF data split up into its component parts.

Or you could use the cdfDump() SKILL function to dump it to an ASCII
representation of the SKILL needed to create it.

Regards,

Andrew.
 

Welcome to EDABoard.com

Sponsor

Back
Top