View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005002 | NoesisGUI | Studio | public | 2026-04-17 16:26 | 2026-04-17 16:36 |
| Reporter | dstewart | Assigned To | |||
| Priority | normal | Severity | feature | ||
| Status | new | Resolution | open | ||
| Product Version | Studio_Beta | ||||
| Summary | 0005002: Triggers Missing Descriptive Default Naming | ||||
| Description | Currently, any newly-created Setter in the Interactivity/Setters Panel is given a default name that provides some indication as to its mechanism. For example "IsMouseOver=True". However in the case of Triggers, these are only named [TriggerType] without any detail as to the function they perform. This results in Triggers being essentially indistinguishable in the Triggers Panel. Whilst each Trigger does offer the ability to input a custom, descriptive name to address this, and this functionality absolutely needs to be conserved, this ticket is moreso about providing more useful, descriptive defaults to help users in cases when they are not manually-renamed. Note that in the case of users who are making use of their own custom Triggers, responsibility will be on them to populate their metadata with their desired syntax for this, otherwise they will be left with the TriggerType name syntax as it currently functions as the default Each Trigger Type offers different functionality; find below a first proposal for their syntax: -- DATAEVENT TRIGGER Syntax: [On {DataSource} {Event}] Example: [On SelectedItem, ElementName=PlayerList MyCustomEvent] -- DATA TRIGGER Syntax: [On {Binding} {Comparison} {Value}] Example: [On BackgroundBorder.ActualHeight = 512] -- EVENT TRIGGER Syntax: [On {Source} {Event}] Example: [On BackgroundBorder Loaded] -- GAMEPAD TRIGGER Syntax: [On {FiredOn} '{Button}'] Example: [On Down 'Accept'] -- KEYTRIGGER Syntax: [On {FiredOn} '{ModifierKey}' {+} '{Key}'] Example: [On Down 'Alt' + 'W'] Note: Omit '{ModifierKey}' and {+} if no Modifier Key specified. Example: [On Down 'W'} -- MOUSEHWEEL TRIGGER Syntax: [On MouseWheel {Direction}] Example: [On MouseWheel Down] -- PROPERTYCHANGED TRIGGER Syntax: [On {Binding} Changed] Example: [On BackgroundBorder.ActualHeight Changed] -- STORYBOARDCOMPLETED TRIGGER Syntax: [On {StoryboardName} Completed] Example: [On MyStorboard Completed] -- TIMER TRIGGER Syntax: [On {Source} {Event} + {TotalTicks}] Example: [On BackgroundBorder Loaded + 1] | ||||
| Platform | Any | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-04-17 16:26 | dstewart | New Issue | |
| 2026-04-17 16:26 | dstewart | Description Updated | |
| 2026-04-17 16:27 | dstewart | Description Updated | |
| 2026-04-17 16:28 | dstewart | Description Updated | |
| 2026-04-17 16:34 | dstewart | Description Updated | |
| 2026-04-17 16:34 | dstewart | Description Updated | |
| 2026-04-17 16:35 | dstewart | Description Updated | |
| 2026-04-17 16:36 | dstewart | Description Updated |