View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004541 | NoesisGUI | Studio | public | 2025-11-17 17:10 | 2026-04-08 02:14 |
| Reporter | dstewart | Assigned To | dfranjic | ||
| Priority | normal | Severity | major | ||
| Status | assigned | Resolution | open | ||
| Product Version | Studio_Beta | ||||
| Target Version | Studio_Beta | ||||
| Summary | 0004541: Created Resources Can Sometimes Be Unavailable Until Restart | ||||
| Description | Currently, there are instances, where upon the creation of a new Resource, it can be unavailable and unfindable to Elements wtihin the same scope as the one in which it was created, until the Page is closed and re-opened. I have been unable to reproduce this issue from Scratch, but I do however have a file (attached) in which this issue has a 100% repro rate. Repro Steps: 1) Download and open the attached Studio Project. 2) On the right of the screen, enter the ContentControl/Content Template containing all of the tiles. 3) Right-click on the tile with the "4.0.1-beta2" label, and enter its ContentControl/Content Template. 4) Select the TextBlock reading "4.0.1-beta2", and in its Properties Panel, give it a DropShadowEffect from its 'Effect' Property. 5) From the newly-created Effect's 3-Dot menu, select 'Convert to Resource', and save the DropShowEffect to GlobalResources, saved with a name that can be easily remembered/identified. 6) Select any other Element in the same scope, and from its 'Effect' Property, click on its 3-Dot menu and select 'Apply Resource'. 7) Seek the DropShadowEffect Resource created in Step 5), and attempt to apply it to this Element. Observe how the Resource does not exist. 8) Save all open documents, and repeat steps 2) and 3). 9) Attempt to apply the created DropShadowEffect on any Element. Observe how the Resource now exists. Expected Results: Created Resources are immediately available in the scope in which they are created. | ||||
| Attached Files | |||||
| Platform | Any | ||||
|
Note for future: this happens because on CreateResourceCommand a resource is only registered for the runtime file (MainPage.xaml) and scope file (GlobalResources.xaml), other non-active files (Templates_.xaml) are set to reload on active state change (when selected). Thus, when an user tries to apply the resource (while editing a template from Templates_.xaml) it uses a version of ResourceDictionary instance created specifically for this Templates_*.xaml. And thus, it fails to find the resource since only MainPage.xaml version of GR.xaml and standalone GR.xaml are updated with the new resource. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-11-17 17:10 | dstewart | New Issue | |
| 2025-11-17 17:10 | dstewart | File Added: EffectResourceMissing.zip | |
| 2025-11-17 17:15 | jsantos | Assigned To | => dfranjic |
| 2025-11-17 17:15 | jsantos | Status | new => assigned |
| 2025-11-17 17:16 | jsantos | Target Version | => Studio_Beta |
| 2026-04-08 02:13 | dfranjic | Note Added: 0012167 | |
| 2026-04-08 02:14 | dfranjic | Note Edited: 0012167 |