dePush

dePush( 
[ l_fileSpec [ g_winSpec [ t_accessMode [ t_appName ] ] ] ] 
) 
=> w_window / nil

Description

The same as deOpen, except that if the window already exists, the current contents are not removed. Instead the new design is pushed on top of the existing one.

Arguments

l_fileSpec	File specification for the cellview to be pushed. See deOpen for a detailed explanation of the format for this argument.
g_winSpec	Window specification for the window in which to do the push. See deOpen for a detailed description of this argument.
t_accessMode	Access mode desired for the new design. Must be either edit or read.
t_appName	Name of the application to install after the data is placed on the stack. The application must be a part of the view type subclass tree that is indicated by the data.

Value Returned

w_window

Window in which the push is done. Normally this is the same as the window passed in, but if necessary a new window is created and returned

Examples

Brings up the Open File form, asking for the library, cell, and view names of a cellview to edit. When this form is completed, the cellview opened is pushed on the stack in window(3).

dePush( nil window(3) )

Assume I4 is an instance of a symbol in window(3). Also assume that the schematic view represented by that symbol exists in some library on the current library search path.

myFileSpec = list( ’instanceName "I4" ’viewNameList "schematic symbol")

Switches into the schematic master corresponding to instance I4 in the edit cellview in window(3) for reading, then starts up the Timing Analysis application in that window.

dePush( myFileSpec window(3) "read" "Timing Analysis" )

Return to top