View Issue Details

IDProjectCategoryView StatusLast Update
0002885NoesisGUIStudiopublic2025-02-05 00:34
Reporterfllorens Assigned Todfranjic  
PrioritynormalSeverityminor 
Status resolvedResolutionfixed 
Target VersionStudio_Alpha 
Summary0002885: Duplicated resource names in different dictionaries
Description

As seen here https://youtu.be/nyaiHuqcR08?feature=shared&t=5642 the Studio creates sequential brush names without checking merged dictionaries, thus binding the brush to the former resource

Steps To Reproduce
  1. Create a brush resource
  2. Create a merged dictionary
  3. Create another brush resource with the new dictionary selected
PlatformAny

Activities

dfranjic

dfranjic

2024-03-05 22:40

developer   ~0009278

I think it's allowed to have same name resources in two different places, though I don't know how that should be handled in UI so that it's not confusing for the user.

Maybe some kind of adorner telling user that this resource can't be bound to the property (since there's a same-named resource that would be used instead).

fllorens

fllorens

2024-03-06 10:13

developer   ~0009283

Thanks Dario, maybe I wasn't clear enough with the problem: If you assign a resouce with the same name in a different dictionary, Studio only applies the first one, so for example:

  1. Create a brush resource
  2. Create a merged dictionary
  3. Create another brush resource with the new dictionary selected
  4. You've got two different brushes with the same name (e.g. SolidColorBrush.001)
  5. Create an element and apply the first resource you created
  6. Then try to change it to the second resource, either drag and dropping it or using the Resource expander.
    You'll discover that it's not updating.
fllorens

fllorens

2024-03-06 12:02

developer   ~0009286

Now that I thought a little about this, you're right. It's working as expected, so there's this solutions, change the suffix for the newly created resources in merged dictionaries or show either a toast or dialog when trying to use a resource with the same name.
We should close this bug.

fllorens

fllorens

2024-05-08 17:42

developer   ~0009504

Unfortunately, we have the same problem here: https://youtu.be/j-TOPx6B0AI?feature=shared&t=527

fllorens

fllorens

2025-02-04 18:19

developer   ~0010302

This is working now, should be closed

Issue History

Date Modified Username Field Change
2023-11-23 13:47 fllorens New Issue
2023-11-23 14:07 sfernandez Target Version => Studio_Alpha
2024-02-12 11:28 sfernandez Assigned To => dfranjic
2024-02-12 11:28 sfernandez Status new => assigned
2024-03-05 22:40 dfranjic Note Added: 0009278
2024-03-06 10:13 fllorens Note Added: 0009283
2024-03-06 12:02 fllorens Note Added: 0009286
2024-05-08 17:42 fllorens Note Added: 0009504
2025-02-04 18:19 fllorens Note Added: 0010302
2025-02-05 00:34 dfranjic Status assigned => resolved
2025-02-05 00:34 dfranjic Resolution open => fixed