View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004037 | NoesisGUI | Studio | public | 2025-04-03 18:05 | 2025-10-28 15:46 |
| Reporter | dstewart | Assigned To | sfernandez | ||
| Priority | normal | Severity | minor | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | Studio_Beta | ||||
| Target Version | Studio_Beta | ||||
| Summary | 0004037: Resources Moved From A Dictionary Into A Page Can Break The Page Due To Being Incorrectly Positioned In the XAML When Relocated | ||||
| Description | Currently, if you have a set of Resources in a ResourceDictionary (GlobalResources.xaml for example), and using Studio's built-in Resources Manager, you move them into a Page, it can result in XAML errors and presentation breakage due to the Resources being positioned after their usage location, rather than being positioned at the top of the Page. | ||||
| Steps To Reproduce | Repro Steps: 1) Open the Localization sample from the InternalProjects repo. Observe, how at a certain point, the GlobalResources.xaml tab will go red, indicating errors. Expected Results: When using Studio's Resource Management toolset, the application automatically places Resources in a xaml page position that will not cause project breakage. | ||||
| Attached Files | |||||
| Platform | Any | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-04-03 18:05 | dstewart | New Issue | |
| 2025-04-03 18:05 | dstewart | File Added: MovingGlobalResourcesToPageErrors.png | |
| 2025-04-04 00:36 | jsantos | Assigned To | => sfernandez |
| 2025-04-04 00:36 | jsantos | Status | new => assigned |
| 2025-04-04 00:36 | jsantos | Target Version | => Studio_Beta |
| 2025-10-28 15:46 | dstewart | Status | assigned => resolved |
| 2025-10-28 15:46 | dstewart | Resolution | open => fixed |
| 2025-10-28 15:46 | dstewart | Note Added: 0011267 |
