| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004276 | NoesisGUI | Studio | public | 2025-07-01 17:50 | 2026-11-06 11:17 |
| Reporter | dstewart | Assigned To | sfernandez | ||
| Priority | normal | Severity | major | ||
| Status | assigned | Resolution | open | ||
| Product Version | Studio_Beta | ||||
| Target Version | Studio_Beta | ||||
| Summary | 0004276: Setting a Style to be "BasedOn" Another Style Produces a XAML Error | ||||
| Description | Currently, it appears that Setting a GlobalResource Style to be based on another GlobalResource Style creates a XAML error. Repro Steps: 1) Download and open the attached Project, and open the MainPage.xaml. 4) In the Style Dummy Editor, select the STYLE from the Navigator, and from the top of the Properties Panel, set its 'BasedOn' Property to be BasedOn the Style named 'CheckBox_Style_Base'. Observe how a XAML Error is produced. Expected Results: Supported and valid "BasedOn" operations don't produce XAML errors. 5) Open GlobalResources.xaml in VSCode Observe how the error appears to be related to the Resource being referenced as a StaticResource. | ||||
| Platform | Any | ||||
 |
Not sure what should be done about this. It's not a bug of Studio, it's expected that it shows errors. The fix would be to move BASE style above the DERIVED one in the resources panel. So technically, nothing on Studio's side. Maybe the UX could be improved somehow, not sure how, but it doesn't even warn the user or anything... |
 |
Interesting. It never occurred to me to have to adjust the order in the Resources. Maybe once you link-up Derived Style and Main Style, we throw a toast up that says "{Derived} Style uses {Base} Style, but is declared before it. It is recommended to move {Base} Style above {Derived} Style in the Resource Dictionary". or, alternately, is this something that wouldn't happen if they used DynamicResource instead of StaticResource? If so, could we just default to setting Resources as Dynamic? |
