View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002207 | NoesisGUI | C++ SDK | public | 2021-12-03 10:28 | 2021-12-03 11:24 |
| Reporter | pdx_lysannschlegel | Assigned To | sfernandez | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | duplicate | ||
| Product Version | 3.0.12 | ||||
| Target Version | 3.1.2 | Fixed in Version | 3.1.2 | ||
| Summary | 0002207: Binding issues reported as errors (inconsistency with WPF) | ||||
| Description | In some cases noesis generates error logs for binding issues which are have only "warning" or "information" level in WPF/Blend. My general take on this is: When our UX designers work with Blend most of the time, I think it is important that the warnings and errors logged are similar between Blend and Noesis, otherwise they'll make a nice UI in WPF that can then spew a lot of errors in Noesis. So I think deviating much from what WPF considers a warning/error needs to have very good reasons. sfernandez agreed and asked me to report this in the bug tracker. Forum thread for full context and some examples: https://www.noesisengine.com/forums/viewtopic.php?f=3&t=2464 | ||||
| Tags | No tags attached. | ||||
| Platform | Any | ||||
| duplicate of | 0002200 | resolved | sfernandez | Avoid binding errors when part of the path is null |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-12-03 10:28 | pdx_lysannschlegel | New Issue | |
| 2021-12-03 11:23 | sfernandez | Assigned To | => sfernandez |
| 2021-12-03 11:23 | sfernandez | Status | new => assigned |
| 2021-12-03 11:23 | sfernandez | Target Version | => 3.1.2 |
| 2021-12-03 11:23 | sfernandez | Relationship added | duplicate of 0002200 |
| 2021-12-03 11:24 | sfernandez | Status | assigned => resolved |
| 2021-12-03 11:24 | sfernandez | Resolution | open => duplicate |
| 2021-12-03 11:24 | sfernandez | Fixed in Version | => 3.1.2 |
