Skip to end of metadata
Go to start of metadata

Description

A component to display MES property value components for the active MES Response Segment. The MES property value entry components that are shown depend on the configuration of the MES associated objects.

In the image below, a MES Operations Segment with a material resource that references a MES Material Definition that has a Viscosity custom property. This is causing the entry component to accept a viscosity value be added. In order for the custom property to be shown, the Production Visible option for the custom property must be set to True. Likewise, the required indication will be shown when the Required option for the custom property is set to True. All this is performed automatically and there is no need to create custom Ignition windows for each combination of how associated MES objects are configured.

 

Component Palette

If more than one property has been defined for the associated MES objects, then the MES Property Value Editor component will automatically populate components for each one.

The MES Property Value Editor must be used in conjunction with the MES Segment Selector or MES Sublot List components. Which one it works with is determined by the Mode property of this component.

If the Mode is set to Segment, then the active MES Response Segment is retrieved from the MES Segment Selector component. MES Response Segment objects are derived from MES Operations Segment objects and drive the entry components created in the MES Property Value Editor component. No binding is required for the two to work together. Behind the scenes, the MES Property Value Editor finds the MES Segment Selector and the two will communicate.

If the Mode is set to Lot, then the active MES Response Segment is retrieved from the MES Segment Selector component. All lot references will be scanned for MES properties and drive the entry components created in the MES Property Value Editor component. No binding is required for the two to work together. Behind the scenes, the MES Property Value Editor finds the MES Segment Selector and the two will communicate.

If the Mode property is set to Sublot, then the selected MES Material Sublot is retrieved from the MES Sublot List component. The MES Material Sublot object drive the entry components created in the MES Property Value Editor component. No binding is required for the two to work together. Behind the scenes, the MES Property Value Editor finds the MES Sublot List and the two will communicate.

For the MES Property Value Editor component to find the MES Segment Selector or MES Sublot List, it must be in the same container on the window. It is okay to be in a container, they just both have to be in the same container or root container. Multiple containers can exist on the same window containing separate MES Segment Selector and/or MES Sublot List and MES Property Value Editor components in each. The components residing in the same container will work together allowing multiple segments to be controlled from the same window.

If two MES Property Value Editor components exist on the same container and one is set to Segment mode and the other is set the Sublot mode, the two will connect to the correct parent. This allows MES property values to be entered for both the segment or lot and for the selected sublot on the same screen.


 

Component Properties

Properties are provided that can be set to affect the operation and look of the component. They can be set through the Property Editor in the Designer or through scripting.

Example
event.source.parent.getComponent('MES Property Value Editor').nameFilter = 'Att*'

 Data
NameScriptingProperty TypeDescription
Name FilternameFilterStringLot names to filter on.
Read OnlyreadOnlyBoolean

Allow editing of editor.

ModemodeintSelect mode to work with a segment selector or sublot list component.
 Appearance
NameScriptingProperty TypeDescription
Required Icon PathrequiredIconPathStringThe relative path of an icon image to indicate required property values.
Modified Icon PathmodifiedIconPathStringThe relative path of an icon image to indicate modified property values.

 

Event Handlers

Event handlers provide the ability to add custom script when a user interacts with a component such as by clicking a mouse, selecting a menu item or when a component property changes.

 mouse
 mouseClicked

This event signifies a mouse click on the source component. A mouse click the combination of a mouse press and a mouse release, both of which must have occurred over the source component. Note that this event fires after the pressed and released events have fired.

PropertyDescription
.sourceThe component that fired this event.
.buttonThe code for the button that caused this event to fire.
.clickCountThe number of mouse clicks associated with this event.
.xThe x-coordinate (with respect to the source component) of this mouse event.
.yThe y-coordinate (with respect to the source component) of this mouse event.
.popupTriggerReturns True (1) if this mouse event is a popup trigger. What constitutes a popup trigger is operating system dependent, which is why this abstraction exists.
.altDownTrue (1) if the Alt key was held down during this event, false (0) otherwise.
.controlDownTrue (1) if the Ctrl key was held down during this event, false (0) otherwise.
.shiftDownTrue (1) if the Shift key was held down during this event, false (0) otherwise.
 mouseEntered

This event fires when the mouse enters the space over the source component.

PropertyDescription
.sourceThe component that fired this event.
.buttonThe code for the button that caused this event to fire.
.clickCountThe number of mouse clicks associated with this event.
.xThe x-coordinate (with respect to the source component) of this mouse event.
.yThe y-coordinate (with respect to the source component) of this mouse event.
.popupTriggerReturns True (1) if this mouse event is a popup trigger. What constitutes a popup trigger is operating system dependent, which is why this abstraction exists.
.altDownTrue (1) if the Alt key was held down during this event, false (0) otherwise.
.controlDownTrue (1) if the Ctrl key was held down during this event, false (0) otherwise.
.shiftDownTrue (1) if the Shift key was held down during this event, false (0) otherwise.
 mouseExited

This event fires when the mouse leaves the space over the source component.

PropertyDescription
.sourceThe component that fired this event.
.buttonThe code for the button that caused this event to fire.
.clickCountThe number of mouse clicks associated with this event.
.xThe x-coordinate (with respect to the source component) of this mouse event.
.yThe y-coordinate (with respect to the source component) of this mouse event.
.popupTriggerReturns True (1) if this mouse event is a popup trigger. What constitutes a popup trigger is operating system dependent, which is why this abstraction exists.
.altDownTrue (1) if the Alt key was held down during this event, false (0) otherwise.
.controlDownTrue (1) if the Ctrl key was held down during this event, false (0) otherwise.
.shiftDownTrue (1) if the Shift key was held down during this event, false (0) otherwise.
 mousePressed

This event fires when a mouse button is pressed down on the source component.

PropertyDescription
.sourceThe component that fired this event.
.buttonThe code for the button that caused this event to fire.
.clickCountThe number of mouse clicks associated with this event.
.xThe x-coordinate (with respect to the source component) of this mouse event.
.yThe y-coordinate (with respect to the source component) of this mouse event.
.popupTriggerReturns True (1) if this mouse event is a popup trigger. What constitutes a popup trigger is operating system dependent, which is why this abstraction exists.
.altDownTrue (1) if the Alt key was held down during this event, false (0) otherwise.
.controlDownTrue (1) if the Ctrl key was held down during this event, false (0) otherwise.
.shiftDownTrue (1) if the Shift key was held down during this event, false (0) otherwise.
 mouseReleased

This event fires when a mouse button is released, if that mouse button's press happened over this component.

PropertyDescription
.sourceThe component that fired this event.
.buttonThe code for the button that caused this event to fire.
.clickCountThe number of mouse clicks associated with this event.
.xThe x-coordinate (with respect to the source component) of this mouse event.
.yThe y-coordinate (with respect to the source component) of this mouse event.
.popupTriggerReturns True (1) if this mouse event is a popup trigger. What constitutes a popup trigger is operating system dependent, which is why this abstraction exists.
.altDownTrue (1) if the Alt key was held down during this event, false (0) otherwise.
.controlDownTrue (1) if the Ctrl key was held down during this event, false (0) otherwise.
.shiftDownTrue (1) if the Shift key was held down during this event, false (0) otherwise.
 mouseMotion
 mouseDragged

Fires when the mouse moves over a component after a button has been pushed.

 

PropertyDescription
.sourceThe component that fired this event.
.buttonThe code for the button that caused this event to fire.
.clickCountThe number of mouse clicks associated with this event.
.xThe x-coordinate (with respect to the source component) of this mouse event.
.yThe y-coordinate (with respect to the source component) of this mouse event.
.popupTriggerReturns True (1) if this mouse event is a popup trigger. What constitutes a popup trigger is operating system dependent, which is why this abstraction exists.
.altDownTrue (1) if the Alt key was held down during this event, false (0) otherwise.
.controlDownTrue (1) if the Ctrl key was held down during this event, false (0) otherwise.
.shiftDownTrue (1) if the Shift key was held down during this event, false (0) otherwise.
 mouseMoved

Fires when the mouse moves over a component, but no buttons are pushed.

PropertyDescription
.sourceThe component that fired this event.
.buttonThe code for the button that caused this event to fire.
.clickCountThe number of mouse clicks associated with this event.
.xThe x-coordinate (with respect to the source component) of this mouse event.
.yThe y-coordinate (with respect to the source component) of this mouse event.
.popupTriggerReturns True (1) if this mouse event is a popup trigger. What constitutes a popup trigger is operating system dependent, which is why this abstraction exists.
.altDownTrue (1) if the Alt key was held down during this event, false (0) otherwise.
.controlDownTrue (1) if the Ctrl key was held down during this event, false (0) otherwise.
.shiftDownTrue (1) if the Shift key was held down during this event, false (0) otherwise.
 propertyChange
 propertyChange

Fires whenever a bindable property of the source component changes. This works for standard and custom (dynamic) properties.

PropertyDescription
.sourceThe component that fired this event.
.newValueThe new value that this property changed to.
.oldValueThe value that this property was before it changed. Note that not all components include an accurate oldValue in their events.
.propertyNameThe name of the property that changed. NOTE: Remember to always filter out these events for the property that you are looking for! Components often have many properties that change.

 


 

Extension Functions

This component does not have extension functions associated with it. 

 


 

Custom Methods

Custom methods allow you to add your own component functions to a component that can be called through scripting. This is a useful and clean method of re-using script that is specific to the component (say you want to update a visual aspect of the component in the same way whether a user clicks on the component or a window property value changes). See Component Custom Methods in the Ignition Help Manual for more information.

 


 

Customizers
This component does not have any custom properties.

 

Component Functions

This component does not have functions associated with it.

  • No labels