Jump to content

Event Components.Property: Difference between revisions

From Flowcode Help
Admin (talk | contribs)
XML import
m Text replacement - "class="wikitable" style="width:60%; background-color:#FFFFFF;"" to "class="mtx-class-macrotable wikitable""
 
(10 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{| class="mtx-class-macrotable wikitable"
|-
| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
| width="90%" class="mtx-class-macrohead" | '''Property'''
|-
| colspan="2" | Sent when a property has been changed by the User 
|-
|-
| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-void-icon.png]] - NONE
| width="90%" style="border-top: 2px solid #000;" | ''Return''
|}


Sent when a property has been changed by the User


This event is part of the [[Event class Components|Components]] class
Details on using Event Macros can be found here: [[Simulation Events|Event Macros]]


__TOC__


==Parameters==
==Detailed description==
''This event has no parameters''
This event is called whenever a property owned by your component changes.


 
This event simply notifies ''something'' has changed. This means changes will be accumulated, so changing three properties in quick succession will only result in a single event being sent. Because of this, it is the components responsibility to remember previous property states to establish what has changed.
==Return value==
[[Variable types|ULONG]]
The return of this event is currently unused
 
 
==Detailed description==
''<span style="color:red;">No additional information</span>''




==Examples==
==Examples==
''<span style="color:red;">No additional information</span>''

Latest revision as of 14:13, 13 July 2026

Property
Sent when a property has been changed by the User 
- NONE Return


Details on using Event Macros can be found here: Event Macros


Detailed description

This event is called whenever a property owned by your component changes.

This event simply notifies something has changed. This means changes will be accumulated, so changing three properties in quick succession will only result in a single event being sent. Because of this, it is the components responsibility to remember previous property states to establish what has changed.


Examples