Modeling Events

The ClientFeatureDoubleClick notifies the client when the user double-clicks a feature.

EventNames:

  • ClientFeatureDoubleClick_Post

Examples:

ClientFeatureDoubleClick_Post:

Register-InventorEvent -EventName ClientFeatureDoubleClick_Post -Action 'PostClientFeatureDoubleClick'

function PostClientFeatureDoubleClick() {
	#Write event code here
}

The ModelingDelete notifies the client when a modeling entity is deleted.

Remarks

Currently the notification is limited to features and parameters. Notification for parameters is only sent when a parameter is explicitly deleted, not when it is deleted as a result of its owner being deleted. For example if you delete a fillet feature, the notification will be sent for the fillet feature, but not for the parameter that controls the fillet radius, even though the parameter is deleted as a result of the feature delete. The type of entities supported for this event may be expanded in the future.

EventNames:

  • ModelingDelete_Pre

  • ModelingDelete_Post

Examples:

ModelingDelete_Pre:

Register-InventorEvent -EventName ModelingDelete_Pre -Action 'PreModelingDelete'

function PreModelingDelete() {
	#Write event code here
}

ModelingDelete_Post:

Register-InventorEvent -EventName ModelingDelete_Post -Action 'PostModelingDelete'

function PostModelingDelete() {
	#Write event code here
}

The FeatureChange event notifies the client whenever a feature changes.

Remarks

This is provided for features in parts and also for assembly features. A change is defined as the modification of a feature’s definition. This can occur when the end-user uses the edit command for that particular feature and when a feature is modified using the API. A feature recomputing as the result of other changes in the model is not considered a feature change. For example, if a fillet recomputes because the underlying geometry has changed, this is not considered a feature change because only the resulting geometry changed, not the definition of the fillet. Also, editing any of the various objects the feature is dependent on (sketch, parameters) is also not considered a feature change.

EventNames:

  • FeatureChange_Pre

  • FeatureChange_Post

Examples:

FeatureChange_Pre:

Register-InventorEvent -EventName FeatureChange_Pre -Action 'PreFeatureChange'

function PreFeatureChange() {
	#Write event code here
}

FeatureChange_Post:

Register-InventorEvent -EventName FeatureChange_Post -Action 'PostFeatureChange'

function PostFeatureChange() {
	#Write event code here
}

The GenerateMember event is fired before and after an iPart or an iAssembly member is being generated or regenerated.

EventNames:

  • GenerateMember_Pre

  • GenerateMember_Post

Parameters

Type

Name

Description

String

memberName

Name of iPart or iAssembly member. If multiple members are generated this returns the first member name

Examples:

GenerateMember_Pre:

Register-InventorEvent -EventName GenerateMember_Pre -Action 'PreGenerateMember'

function PreGenerateMember($memberName) {
	#Write event code here
}

GenerateMember_Post:

Register-InventorEvent -EventName GenerateMember_Post -Action 'PostGenerateMember'

function PostGenerateMember($memberName) {
	#Write event code here
}

The NewFeature event notifies the client whenever a new feature is created.

EventNames:

  • NewFeature_Pre

  • NewFeature_Post

Examples:

NewFeature_Pre:

Register-InventorEvent -EventName NewFeature_Pre -Action 'PreNewFeature'

function PreNewFeature() {
	#Write event code here
}

NewFeature_Post:

Register-InventorEvent -EventName NewFeature_Post -Action 'PostNewFeature'

function PostNewFeature() {
	#Write event code here
}

The NewParameter event notifies the client when a new Parameter is created.

Remarks

New parameters can be created explicitly by the end-user using the Add button on the Parameters dialog and they are also created implicitly as the result of placing dimension constraints and constructing features. This event provides notification is both cases.

EventNames:

  • NewParameter_Pre

  • NewParameter_Post

Examples:

NewParameter_Pre:

Register-InventorEvent -EventName NewParameter_Pre -Action 'PreNewParameter'

function PreNewParameter() {
	#Write event code here
}

NewParameter_Post:

Register-InventorEvent -EventName NewParameter_Post -Action 'PostNewParameter'

function PostNewParameter() {
	#Write event code here
}

The ParameterChange event notifies the client when a parameter is changed.

Remarks

A parameter’s value can be changed in many ways. This notification is sent for any change, regardless of what caused it.

EventNames:

  • ParameterChange_Pre

  • ParameterChange_Post

Examples:

ParameterChange_Pre:

Register-InventorEvent -EventName ParameterChange_Pre -Action 'PreParameterChange'

function PreParameterChange() {
	#Write event code here
}

ParameterChange_Post:

Register-InventorEvent -EventName ParameterChange_Post -Action 'PostParameterChange'

function PostParameterChange() {
	#Write event code here
}