Create an URL for loading and configuring an EDB database, optionally by modifying the URL of the currently loaded EEvision instance. The configuration encompasses, e.g.,
the activated options
Optional
Readonly
edb?: stringName of the EDB file to load. The filename must be relative to the web server's dataRoot.
Optional
Readonly
f?: null | readonly ObjectID[]Module IDs for filtering EDB data to 100% model.
Optional
Readonly
famo?: numberFilter attributes mode.
Optional
Readonly
fattr?: null | stringEnables the "filter attributes" post-process by specifying the suffix to attribute names.
Optional
Readonly
fblock?: null | readonly string[]Enables the filter-block post-process; additional flags can be specified.
Optional
Readonly
ff?: null | readonly string[]Flags for filtering EDB data to a 100% model.
Optional
Readonly
fsig?: null | stringEnables the filter-by-signal post-process. Optionally an attribute name can be specified that has the signal name as its value. If no signal name should be used, set the parameter to the empty string.
Optional
Readonly
fsigf?: null | readonly string[]Flags for the filter-by-signal process.
Optional
Readonly
fv?: null | readonly string[]Activated/set variables for filtering EDB data to a 100% model.
Optional
Readonly
fwt?: null | readonly string[]Enables the filter-wire-types post-process by listing the types of wires that should be preserved.
Optional
Readonly
home?: null | stringLink that is opened when the user clicks on the "Home" button.
Optional
Readonly
plink?: null | stringPermalink to a stored EEvision state.
Optional
Readonly
tool?: null | string | readonly string[]Available license features: "pro", "signoff", "edbdiff", "docgen". "basic" licensing is always available.
if true then the current EEvision parameters are
updated using the new ones in def
.
a string with the corresponding URL search parameters, including the "?" prefix.
Call a function of a server-side extension after it has been loaded using EEvisionAPI.LoadServerPlugin.
name of the server-side extension (without the file
extension .tcl
of the script)
name of the function to be called.
Optional
params: readonly string[](optional) parameters for the called function. Note that the loaded EDB is automatically added as the first parameter of the function.
the string returned by the server-side function.
Create a permanent link for the current schematic. It can be used to re-create the same situation again. The link is stored in a file on the server and becomes invalid when this file is deleted.
the query part of the link (including the ?
at the
beginning). The caller has to add the protocol and url of the server.
This function returns information about the license used for EEvision. This includes the type of license (Altair Units / FlexNet) and the expiry date.
information about the EEvision license.
If the webserver on which EEvision is hosted uses basic authentication, this function allows to retrieve information about the authenticated user like the username, his/her IP address, and hostname.
information about the user if available.
Retrieve information about the EEvision version.
the version information.
Load a server-side EEvision extension (Tcl script) into the server process of the current session. See also EEvisionAPI.UnloadServerPlugin and EEvisionAPI.CallServerPlugin.
the name of the script file without the
file extension .tcl. The file has to be located in the
srv/
directory of the EEvision installation.
Explode or collapse the connector of a component. Collapsing hides all currently unconnected cavities, exploding a connector shows all cavities. If the connector is already collapsed/exploded, nothing happens. The connector must be available on the canvas.
the ID of the connector of a component.
Optional
collapse: booleanif true, collapse the connector; if false, explode it.
if not specified (or undefined
), the connector is toggled.
true
if the connector is collapsed after the call,
false
otherwise.
An ObjectError is thrown if the object is not loaded or if the object is not a collapsible connector.
Remove a server-side extension from the session's server process.
the name of the script file without the
file extension .tcl
. The file must have been loaded before
using the API function EEvisionAPI.LoadServerPlugin.
Scroll the EEvision canvas such that the object with the given ID is in the center of the canvas. In case an array of object IDs is passed to the function, the center of the joint bounding box of these objects is centered.
The ExtractOne function extracts all wires and components that are electrically connected to the object (component, connector, cavity) that is passed as the function's first parameter.
An exception is thrown if an invalid object should be extracted. Only components, connectors, and cavities are valid objects, but not wires, multicores, modules, and the database root.
The start object.
Optional
options: Partial<true iff the extraction was limited by options.extractMax
,
i.e., if the schematic does not contain all electrically connected
objects.
Show all electrical connections between a list of terminal objects. Terminals are components, connectors, or cavities.
An error is thrown if idList
contains less than two elements or an
object that is not a valid terminal (wires, modules, multicores).
list of EDB object IDs of the terminals.
Optional
options: Partial<configuring the extractor, e. g., to ignore power
or ground wires. If options
is not specified, then all options are
implicitly false.
Extract a so-called Steiner tree between a set of terminal objects from the EDB. A Steiner tree is a (hopefully small) subset of the wires that connect all the terminals if possible. Possible terminal objects are components, connectors, and cavities.
list of terminal objects.
Optional
options: Partial<configuration of the Steiner extractor.
This function is deprecated and might be removed in future. Please consider using EEvisionAPI.ExtractPaths instead which provides an electrically justified semantics.
Zoom the schematic such that it fits onto the canvas (in one or both dimensions).
the dimensions in which the schematic should fit.
"x"
: horizontally"y"
: vertically"xy"
: both horizontally and vertically.Determine the bounding box of an EDB object.
the EDB ID of the object.
specifies what to include in the bounding box:
"full"
: the bounding box should include the name and all visible
attributes of the object, see CoreConfig.compAttrdsp,
CoreConfig.connAttrdsp, CoreConfig.cavAttrdsp,
CoreConfig.wireBotAttr, and CoreConfig.wireTopAttr."tight"
: the bounding box should include only the object itself,
but not its name or its displayed attributes."body"
: for inliner and ECU components, do not include
the connectors in the bounding box, but only the body rectangle.the bounding box or null
if the object is
currently not displayed.
Get the currently selected objects. The most recently selected object (i.e., in netMode the object that the user actually selected) is the first entry in the list. If nothing is selected, the result is an empty array.
for each selected object: its EDB ID, its type, name and sub-type. Note that the attribute list is not part of the returned object info.
Return EEvision's current zoom factor.
Use EEvisionAPI.SetZoom to change Nlview's zoom factor.
Add an array of objects to the schematic. The objects that were loaded
before are removed and replaced by the new objects. Modules are also
admissible objects. In this case, all members of the module are loaded.
If the list of objects is empty or null
, the canvas is cleared.
the EDB IDs of the objects that should be loaded.
Optional
options: { preciseAppear?: boolean; startColor?: null | string }configure the way how the loaded objects are displayed.
Optional
Readonly
preciseAppear?: booleanIf true, only the actual terminal object is highlighted, e.g., in case of a component, only the component body, but not its connectors or cavities. If false, the connectors of the loaded components are highlighted as well.
Optional
Readonly
startColor?: null | stringColor that is used to highlight the loaded object(s). If it is null, the object(s) are not highlighted.
Determine the ID of the EDB object which is located at the point of the mouse click.
the information about the mouse click (essentially a
MouseEvent
without functions as they cannot be serialized).
the Object ID of the object (null
if there is no object at
the click location).
Regenerate the current schematic. This function is useful when the schematic has become confusing after interactive navigation.
if true, the components may change their position in the schematic.
Export the current schematic as an SVG image.
whether to show the highlight colors in the schematic
which part of the schematic should be exported?
an SVG image as a string.
This function changes the scroll position of the current schematic in
the viewport defined by the canvas window. The given relx
and rely
parameter values are relative floating numbers in the range between
-1.0 and 1.0. A negative value for relx
shifts leftwards, a negative
value for rely
shifts upwards. The ScrollBy
function applies limits
to avoid scrolling the schematic diagram outside of the viewport.
the amount to scroll in horizontal direction (positive value means to the right).
the amount to scroll in vertical direction (positive number means down).
Change the set of selected EDB objects.
Only objects that have been loaded onto the EEvision canvas can be selected.
If EEvision's netMode is active and
the id_list
contains wires, the wires that are electrically connected
to the ones in id_list
are added to id_list
before changing the
selection.
the EDB ID(s) of the object(s) whose selection status should be changed.
specifies how to change the set of selected elements.
Optional
data: unknownadditional data that is passed to the registered selection handler. The data passed here must be serializable, i.e., not contain functions etc. For details on the serialization, see the structured clone algorithm.
eevision/api.ObjectError This exception is thrown if
id_list
is not a valid ObjectID or list
of ObjectID
s or null
.Set the zoom factor of EEvision. See the Nlview documentation for details.
the new zoom factor for EEvision.
Use EEvisionAPI.GetZoom to retrieve EEvision's zoom factor.
Adds connected wires connected to the start object to the canvas. If netmode enables, all electrically connected wire and components are added. If netmode is disabled, only the directly connected components are added.
Object ID of double clicked object
Optional
options: { follow?: boolean }follow true: only already connected wires of an inliner are expanded, false: all wires are expanded
Change the current configuration of EEvision. Note that this might lead to a re-initialization of EEvision if the changes affect the server process, calling the EEvisionAPI.onSchematicChange handler.
the changed entries of the configuration. Entries with unchanged values can be omitted.
the new configuration (with all keys, not only the changed ones).
CoreConfig.showArcs
clears the canvas.await API.ChangeConfig({ colorscheme: null });
null
or the empty string. For example, to reset
"backgroundcolor"
to the default (white), you can use one ofawait API.ChangeConfig({ colorscheme: { backgroundcolor: "" } });
await API.ChangeConfig({ colorscheme: { backgroundcolor: null } });
Read access to EEvision's current configuration. The configuration must not be changed by modifying the returned object. Instead use the function EEvisionAPI.ChangeConfig.
the current configuration.
Access to EEvision's server-side configuration file (or the default
configuration if no eev.conf
file is available). This configuration
does not reflect the changes that the user has made.
the server-side configuration of EEvision.
Information about the place from where the EEvision configuration was taken:
""
(empty string): from the browser history"/data/eev.conf"
): from the specified
directory"eev.conf"
: the global configuration file"?"
: no config file available; built-in default settings are used.This function requests a JSON string of a list of objects, identical to EEvisionAPI.QueryJsonList above, but instead of returning all EDB objects, it returns only those objects that are currently loaded to the schematic canvas. The parameters are identical to those of EEvisionAPI.QueryJsonList.
Limit the result to the objects of the given types. If the list is empty or missing, then objects of all types are returned.
if true, switch the query request into flat mode; then the
resulting list contains only objects without nested objects. If
flat = false
, each component object will include all its connectors in
a nested way; and each connector object will include all its cavities in
a nested way; each multicore object will include all its child multicores
in a nested way.
a JSON string with the requested information. The user will
typically apply JSON.parse(...)
to that result string.
Alpha
Get access to the currently loaded Edb database by downloading it from the server.
the downloaded EDB. The EDB API is in an experimental state and not yet to be used in production!
Return information about an EDB database object or the database root node. This information encompasses the object type, sub-type, name, and its attributes.
the EDB object ID or null
for the database root.
if true then all values of attributes with the same name are merged into one entry. The relative order of the values is preserved.
the object information.
Search the EDB database for objects that match a given string. The string can appear either in the object name or in the values of a set of user-specified attributes. The search can be limited to objects of certain types and to a maximum number of returned results.
the search string
Optional
options: {configuration of the search (object types, searched attributes, maximum number of results, ...)
Optional
Readonly
otype?: ObjectType | "any" | "most"Type of object to search for (e.g., "component", "connector", ...).
If the value is "any"
, objects of all types are taken into
consideration (including cavities); if the value is "most"
, then
all types except cavities are considered.
Optional
Readonly
searchAttrs?: readonly string[]List of attribute that EEvision should take into account for the search.
Optional
Readonly
searchMax?: numberMaximum number of search results to return.
A value of 0 means: unlimited.
Optional
Readonly
searchMode?: LiveSearchModeSpecifies whether EEvision should search the whole EDB database on the
server (value "edb"
) or only the currently displayed schematic (value
"scm"
).
Optional
Readonly
stype?: null | stringLimit the search to objects of a certain subtype (e.g., for wire to power or ground wires). If the value is null, all objects of the current type are taken into consideration.
an array with the search results. If not all matches
are returned because of the limit, the last entry of the
returned array is null
.
This function requests a list of objects, represented as a JSON string. Each of those objects corresponds to one EDB object.
Limit the result to the objects of the given types. If the list is empty or missing, then objects of all types are returned.
if true, switch the query request into flat mode; then the
resulting list contains only objects without nested objects. If
flat = false
, each component object will include all its connectors in
a nested way; and each connector object will include all its cavities in
a nested way; each multicore object will include all its child multicores
in a nested way.
a JSON string with the requested information. The user will
typically apply JSON.parse(...)
to that result string.
This function searches for all objects with the given name. The name match may be limited to objects of certain types.
the name of the object to look for.
Limit the search to the objects of the given types. If the list is empty or missing, then objects of all types are returned.
if true, switch the query request into flat mode; then the
resulting list contains only objects without nested objects. If
flat = false
, each returned component object will include all its
connectors in a nested way; and each connector object will include
all its cavities in a nested way; finally, each multicore object will
include all its child multicores in a nested way.
a JSON string with the requested information. The user will
typically apply JSON.parse(...)
to that result string.
Retrieve the stored information about an object from the database on the server.
the EDB object ID
if true, switch the query request into flat mode; then the
resulting object does not include nested objects. If
flat = false
, a component object will include all its connectors in
a nested way; and a connector object will include all its cavities in
a nested way; a multicore object will include all its child multicores
in a nested way.
a JSON string with the requested information. The user will
typically apply JSON.parse(...)
to that result string.
Directly call Nlview, the rendering engine used by EEvision. Use this function with care as it can interfere with EEvision in hard-to-predict ways.
the Nlview command (see Nlview Core API for more information)
the arguments for the Nlview command.
the Nlview result as a string.
Directly call Nlview, the rendering engine used by EEvision. Use this function with care as it can interfere with EEvision in hard-to-predict ways.
the Nlview call as an array of strings; the first entry is the command, the remaining ones the parameters (see Nlview Core API for more information)
the Nlview result as a string.
This handler is called whenever the user requests opening a context menu, e.g., by pressing the right mouse button on an Nlview object.
Handler that is called whenever an error occurs that is not directly caused by an API call, e.g., when interactive navigation or the server communication fails.
This handler is called by the EEvision core whenever a new history state needs to be created (using EEvisionAPI.PushHistoryState) or when the current history state is updated (using EEvisionAPI.UpdateHistoryState).
This handler is called whenever the user goes forward or backward in the browser history and EEvision needs to restore a history state.
This handler is called whenever (1) the current page has switched to a different number, (2) the total number of pages has changed, (3) the current Nlview module has changed, or (4) the current Nlview module was cleared.
This handler is called whenever the number of pending server requests changes.
This handler is called whenever the contents of the schematic changes, i.e., when components or wires are added or removed. It is not called, when only the layout changes, but the set of objects stays the same.
This handler is called whenever the selection of objects in EEvision
changes. If the parameter is null
, then all objects have been
unselected; otherwise selected
gives information about the newly
selected object.
Change the highlighting of objects.
a mapping of object IDs to the desirec highlight slot.
If the slot is null
the object is unhighlighted.
if true
, then the changes will be directly applied;
if false
, the updates are registered, but not applied yet. This allows
to accumulate several sets of updates before applying them, thereby
avoiding flickering.
Return the highlight slot of an EDB object or null
if the object is
not highlighted.
the object ID.
the number of the highlight slot or null
if not highlighted.
Retrieve the highlight slots of all currently highlighted objects.
an object mapping the object IDs of all highlighted objects to their highlight slots.
Get the color of a highlight slot. See EEvisionAPI.Highlight for more information on EEvision's highlighting functionality.
the highlight slot (between HIGHLIGHT_MIN_SLOT and HIGHLIGHT_MAX_SLOT).
the highlight color of that slot.
Highlight a list of objects on the canvas.
Highlighting is done by assigning objects to a slot between HIGHLIGHT_MIN_SLOT and HIGHLIGHT_MAX_SLOT. Each slot can be given a color using the API function EEvisionAPI.SetHighlightColor.
the highlight slot (between HIGHLIGHT_MIN_SLOT and HIGHLIGHT_MAX_SLOT).
the list of object IDs of those objects that should be highlighted with the color of the given slot.
specifies whether the current highlighting should be updated with the new object list or whether the new highlight should replace the existing highlight.
if false
then the schematic is not immediately updated
to reflect the changed highlighting. This way, one can accumulate
changes and apply them at once to avoid flickering.
true if the highlighting has changed.
Set the color of a highlight slot. See EEvisionAPI.Highlight for more information on EEvision's highlighting functionality.
the highlight slot (between HIGHLIGHT_MIN_SLOT and HIGHLIGHT_MAX_SLOT).
the highlight color for that slot (RGB value of the form #RRGGBB in hexadecimal notation).
Remove the highlighting from a list of EDB objects (or all highlighted
objects if null
is passed to the function).
the list of EDB objects that should be un-highlighted
(or null
if that should be done for all currently highlighted objects).
Objects that are not highlighted are ignored.
if false
then the schematic is not immediately updated
to reflect the changed highlighting. This way, one can accumulate
changes and apply them at once to avoid flickering.
true if the highlighting has changed.
This handler is called by the EEvision core whenever a new history state needs to be created (using EEvisionAPI.PushHistoryState) or when the current history state is updated (using EEvisionAPI.UpdateHistoryState).
This handler is called whenever the user goes forward or backward in the browser history and EEvision needs to restore a history state.
Return the current position in the history stack of EEvision. Note
that this value is at most history.length
, but might be smaller
if a different page had been loaded in the same browser tab before
the current EEvision session. This value denotes how many steps
one can go back in the browser history without leaving the current
EEvision session.
Return an object that represents the current state of EEvision. This object can be used later to restore this state by calling EEvisionAPI.RestoreInternalState.
an object with the current state of EEvision.
Create a new entry in EEvision's history stack. This causes a call to the EEvisionAPI.onHistoryRequest handler.
Information about what has changed.
Restore a previously retrieved state of EEvision.
the EEvision state that needs to be restored.
Readonly
config: {The current EEvision configuration
Readonly
autoOptimize: 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7Should EEvision optimize the current schematic automatically whenever it changes? This typically leads to clearer schematics, but creates more movement when incrementally expanding the schematic.
The value of this option is a combination of bits which individually control schematic optimization on certain events.
Bit | Meaning |
---|---|
AutoOptimize.SCHEMATIC = 0x0001 |
If set, then optimize after each change of the schematic content (but not after position changes, e.g., due to manual user interaction). |
AutoOptimize.CONNECTOR = 0x0002 |
If set, optimize whenever a connector is opened or closed by clicking on the [+] / [-] button of the connector. |
AutoOptimize.HIERARCHY = 0x0004 |
If set, optimize whenever a hierarchical component is folded or unfolded. |
The value of the setting is an arbitrary combination of these bits.
0 (= disabled = AutoOptimize.NONE).
Readonly
autoZoom: booleanDetermines whether EEvision's autoZoom mode is active or not.
EEvision has an autoZoom mode, in which the schematic is zoomed automatically to fit the canvas whenever the schematic changes.
Limitation: Expanding and shrinking the connectors of ECU components is currently not covered by the autoZoom mode.
Readonly
busWire: stringDetermine how buses (i.e., wires with type EdbWireTBUS
)
should be displayed in EEvision.
"std"
: use the default style for the wire"#FF00FF"
for red
or one of the
SVG
color names): Display the wire with the specified color.Readonly
cavAttrdsp: null | stringWhich attribute should be shown next to cavities of (L)ECUs?
In contrast to component (CoreConfig.compAttrdsp and connectors (CoreConfig.connAttrdsp), cavities can carry at most one displayed attribute.
Readonly
colorscheme: {This is the color scheme of EEvision that is used for rendering schematics.
Optional
Readonly
attrcolor?: stringSpecifies the color for the "@attr", "@val", "@vconn", "@vconn2" and user-defined pin attributes (see attribute displays).
Optional
Readonly
backgroundcolor?: stringSpecifies the background color for the schematic.
Optional
Readonly
boxcolor0?: stringSpecifies the color of the outline of components.
Optional
Readonly
boxcolor3?: stringSpecifies the color of unconnected pins.
Optional
Readonly
boxinstcolor?: stringSpecifies the instance-name color for the symbols.
Optional
Readonly
boxpincolor?: stringSpecifies the pin color for the symbols.
Optional
Readonly
buscolor?: stringSpecifies the color of the netBundles and netBundle names.
Optional
Readonly
fillcolor1?: stringFill color for the body of UNDEF, ECU, HIER, and EYELET components.
Optional
Readonly
fillcolor2?: stringFill color for the connectors of HIER, ECU, and INLINER components.
Optional
Readonly
fillcolor3?: stringFill color for connectors of ECU and Inliner components that have no connected cavity.
Optional
Readonly
fillcolor6?: stringFill color for the body of INLINER components.
Optional
Readonly
netcolor?: stringSpecifies the color of the wires and wire names.
Optional
Readonly
objectgray?: stringSpecifies the graymode color.
Optional
Readonly
overlaycolor?: stringSpecifies the color of the so called overlay buses (artificial bundles, displayed whenever two or more different nets and/or netBundles connect to the same pinBus/portBus).
Optional
Readonly
portcolor?: stringSpecifies the body and pin color for both port symbols and net page connectors (in page splitting mode).
Optional
Readonly
rippercolor?: stringSpecifies the color of the bus rippers. The color set here is also used for slash rippers.
Readonly
compAttrdsp: readonly string[]Which component attributes should be shown in addition to the component name above the component?
Readonly
connAttrdsp: readonly string[]Which connector attributes (of ECUs and inliners) should be shown next to the connector?
Readonly
explodeSplices: booleanIf true, unconnected “pins” of splices and eyelets are displayed; otherwise they are hidden. This feature is useful to see whether all wires that connect to a splice or eyelet are currently displayed in EEvision.
Readonly
groundWire: stringDetermine how ground wires (i.e., wires with type EdbWireTGROUND
)
should be displayed in EEvision.
"std"
: use the default style for the wire"#FF00FF"
for red
or one of the
SVG
color names): Display the wire with the specified color.Readonly
hierColor: null | stringColor used for highlighting matching connectors in a hierarchical design.
The value must be a hexadecimal RGB-value of the form "#RRGGBB"
.
Readonly
hvWire: stringDetermine how high-voltage wires (i.e., wires with type EdbWireTHV
)
should be displayed in EEvision.
"std"
: use the default style for the wire"#FF00FF"
for red
or one of the
SVG
color names): Display the wire with the specified color.Readonly
license: null | stringEEvision offers the possibility to use a web service for licensing. If that option is used, the URL of the web service should be entered here. By default, licensing is done on the server side using either a FlexNet or Altair license.
Readonly
logicalWire: stringDetermine how logical connections (i.e., wires with type EdbWireTLOGICAL
)
should be displayed in EEvision.
"std"
: use the default style for the wire"#FF00FF"
for red
or one of the
SVG
color names): Display the wire with the specified color.Readonly
multicores: "none" | "bundle" | "basic" | "full"Determines how multicores are rendered in EEvision.
Value | Meaning |
---|---|
"none" |
Do not show multicores. |
"bundle" |
Show multicores as wire bundles. |
"basic" |
Only show well-behaving multicores that can be rendered as part of a component. |
"full" |
Show all multicores (including the ones that require a routing channel). |
Readonly
powerWire: stringDetermine how power wires (i.e., wires with type EdbWireTPOWER
)
should be displayed in EEvision.
"std"
: use the default style for the wire"#FF00FF"
for red
or one of the
SVG
color names): Display the wire with the specified color.Readonly
preciseAppear: booleanThe selection appearance. If true, then selecting a component really only selects the body of the component; if false, then selecting the component also selects all its connectors.
Readonly
rectangleColor: stringColor of the rectangle that is drawn when selecting objects via the rectangleSelection mechanism.
Readonly
rectangleSelection: "none" | "components" | "wires" | "both"Allow the selection of objects using <Ctrl> + dragging the mouse with the left button pressed. The values have the following meaning:
Value | Meaning |
---|---|
"none" |
the rectangle selection mechanism is disabled. |
"components" |
only components are selected. |
"wires" |
only wires are selected. |
"both" |
both components and wires are selected. |
CoreConfig.rectangleColor for setting the color of the selection rectangle.
Readonly
rotate90: booleanDisplay the schematic rotated by 90° (i.e., top to bottom instead of left to right).
Readonly
selectColor: null | stringColor used for highlighting selected objects. If set to null
, no
selection color is applied, but the object is drawn with ticker
lines.
Readonly
space4wirelabel: booleanIf true, let Nlview reserve space such that the whole wire label can be displayed. Otherwise, the label might be shortened to save space, and the complete label is only shown when hovering over the wire.
Readonly
wireBot: booleanIf true, the value of the attribute whose name is given in CoreConfig.wireBotAttr is shown as a wire label (typically below the wire).
Readonly
wireBotAttr: null | stringIf CoreConfig.wireBot is true, the value of the wire attribute whose name is given here is shown as a label (typically below the wire).
Readonly
wireBotFmt: stringFormatting information (foreground/background color) for displaying the additional wire attribute (see CoreConfig.wireBot and CoreConfig.wireBotAttr). It must be empty or one color (defining the background color of the displayed attribute value) or two colors separated by a space (defining the background and foreground colors of the displayed attribute value).
For example wireBotFmt = "#ffd080 #000000"
displays the
attribute value black on beige background.
Readonly
wireMark: booleanIf true, EEvision displays a small color marker on the wire that shows the color of the wire's cover.
Readonly
wireTop: booleanSwitch between showing the wire name or an arbitrary wire attribute above the wire. If false, the wire name is shown; if true, the value of the attribute whose name is given as the value of CoreConfig.wireTopAttr is displayed.
Readonly
wireTopAttr: null | stringName of the wire attribute whose value should be shown above the wire (instead of the wire name) if CoreConfig.wireTop is true.
Readonly
extern: anyAll remaining entries, e.g., from plugins or the GUI.
Readonly
grayMode: booleanGrayMode active or not
Readonly
highlightObjects: readonly (The highlighted objects mapped to their highlight slot (number between HIGHLIGHT_MIN_SLOT and HIGHLIGHT_MAX_SLOT).
Readonly
historyCount: numberPosition in the history stack
Readonly
last_selection: null | stringThe most recently clicked object
Readonly
mtime: null | stringThe EDB modification time.
Readonly
netMode: booleanNetMode active or not
Readonly
schematic: null | stringThe currently loaded Nlview schematic
Readonly
selection: null | stringThe current selection in Nlview
Optional
Readonly
title?: stringThe page title
Optional
Readonly
url?: stringWhen exporting an history state via the EEvision API, we add the URL. When loading the history state, this avoids the problem that loaded EDB and history state do not match.
Readonly
viewport: null | stringThe currently visible part of the schematic
Update EEvision's current history state. This causes a call to the EEvisionAPI.onHistoryRequest handler.
Information about what has changed.
Create a new EEvision API object.
The <iframe> element of the page DOM that runs the EEvision core.
Initialize the EEvision instance.
The URL parameters that should be used for initializing the EEvision database. For the available parameters, see URLParameters.
Optional
Readonly
edb?: stringName of the EDB file to load. The filename must be relative to the web server's dataRoot.
Optional
Readonly
f?: null | readonly ObjectID[]Module IDs for filtering EDB data to 100% model.
Optional
Readonly
famo?: numberFilter attributes mode.
Optional
Readonly
fattr?: null | stringEnables the "filter attributes" post-process by specifying the suffix to attribute names.
Optional
Readonly
fblock?: null | readonly string[]Enables the filter-block post-process; additional flags can be specified.
Optional
Readonly
ff?: null | readonly string[]Flags for filtering EDB data to a 100% model.
Optional
Readonly
fsig?: null | stringEnables the filter-by-signal post-process. Optionally an attribute name can be specified that has the signal name as its value. If no signal name should be used, set the parameter to the empty string.
Optional
Readonly
fsigf?: null | readonly string[]Flags for the filter-by-signal process.
Optional
Readonly
fv?: null | readonly string[]Activated/set variables for filtering EDB data to a 100% model.
Optional
Readonly
fwt?: null | readonly string[]Enables the filter-wire-types post-process by listing the types of wires that should be preserved.
Optional
Readonly
home?: null | stringLink that is opened when the user clicks on the "Home" button.
Optional
Readonly
plink?: null | stringPermalink to a stored EEvision state.
Optional
Readonly
tool?: null | string | readonly string[]Available license features: "pro", "signoff", "edbdiff", "docgen". "basic" licensing is always available.
Initialization must be finished before any other API calls are allowed. The only exception is setting event handlers (e.g., EEvisionAPI.onError etc.). In order to catch errors that occur during initialization, it is necessary to install the handlers before calling EEvisionAPI.Init.
Terminate the EEvision instance and check in its license.
Typically, the lifetime of EEvision is bound to the browser
tab. EEvision is terminated and the license checked in when
the browser tab is closed. For this to work, EEvision relies
on the browser to emit the event beforeunload
when the tab
is closed.
If the lifetime of EEvision is shorter than that of the browser tab, this function should be called once to terminate EEvision.
Temporarily disable the handlers for selections, viewport changes, and page changes. This is sometimes required to avoid infinite calls to event handlers, e.g., when the selection handler needs to change the current selection.
Re-enable the handlers for selection, viewport changes, and page changes after they have been disabled using EEvisionAPI.DisableNotify.
Return EEvision's schematicMode. EEvision can automatically create different kinds of abstractions from a harness model:
the schematicMode of EEvision.
Return whether EEvision's grayMode is active or not.
EEvision's grayMode removes all colors from the schematic except the highlighting colors (see EEvisionAPI.Highlight / EEvisionAPI.Unhighlight). This mode can be convenient to make the highlighting better visible, e.g., when the components or wires are colored themselves.
true if grayMode is active; otherwise false.
Return whether EEvision's netMode is enabled or not.
For instance, in netMode, clicking on a wire automatically selects all wires that are electrically connected with the clicked wire. Similarly, EEvisionAPI.LoadObj loads not only the requested wire, but additionally all other wires that are electrically connected with it (via splices, inline connectors, etc.).
true if netMode is enabled in EEvision.
Toggle, activate or de-activate EEvision's grayMode.
Optional
on: booleanif true activate the grayMode; otherwise de-activate it.
If on
is not specified, switch the grayMode.
true if the grayMode is active after the call.
Toggle, activate, or de-activate EEvision's netMode.
Optional
on: booleanif true, enable netMode; otherwise disable it. If the parameter is missing, then the current netMode status is changed.
true if the netMode is active after the call.
Access to the EEvision Core API. This is the main class for integrating EEvision into a web page (called “parent application”). To get an instance of the API, call
new EEvisionAPI(iframe)
with the iframe element (or pop-up window) that contains the EEvision instance. Before accessing any API function, the API must be initialized by calling EEvisionAPI.Init. An EEvision <iframe> or window must have at most one associated EEvisionAPI instance.Example
These lines of code first retrieve the DOM node with the ID my_iframe from the web page. Then a new EEvisionAPI object is created, passing the <iframe> object as the parameter. As the next step, an error handler is installed such that the user is notified in case an error occurs during initialization. Finally, the API object is initialized, loading an EDB database with the name vehicle.edb from the server, filtering its attributes to the ones in German (“fattr=(DE)”). After initialization, all EEvisionAPI functions can be used.