View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002229 | NoesisGUI | C# SDK | public | 2022-01-02 20:31 | 2022-01-26 20:35 |
| Reporter | stonstad | Assigned To | sfernandez | ||
| Priority | normal | Severity | trivial | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.1.2 | ||||
| Target Version | 3.1.3 | Fixed in Version | 3.1.3 | ||
| Summary | 0002229: System.Windows.Media.PathSegmentCollection Runtime Compatibility | ||||
| Description | Trivial -- *PathSegmentCollection *PathFigureCollection I don't know if this is by design. I'm just calling attention to the departure in behavior. | ||||
| Platform | Any | ||||
|
You mean PathGeometry.Figures and PathFigure.Segments collections, right? |
|
|
https://www.noesisengine.com/forums/viewtopic.php?f=3&t=2503 |
|
|
Re: Sergio, yes. Creating an instance of PathGeometry or PathFigure results in a null collection. I believe WPF behavior is different due to code examples showing these collections being initialized to empty instead of null. This has no impact on my projects -- I'm reporting this if code parity with WPF is desired. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-01-02 20:31 | stonstad | New Issue | |
| 2022-01-03 11:46 | sfernandez | Assigned To | => sfernandez |
| 2022-01-03 11:46 | sfernandez | Status | new => assigned |
| 2022-01-03 11:46 | sfernandez | Target Version | => 3.1.3 |
| 2022-01-03 11:49 | sfernandez | Status | assigned => feedback |
| 2022-01-03 11:49 | sfernandez | Note Added: 0007705 | |
| 2022-01-03 18:01 | jsantos | Note Added: 0007708 | |
| 2022-01-04 17:39 | stonstad | Note Added: 0007711 | |
| 2022-01-04 17:39 | stonstad | Status | feedback => assigned |
| 2022-01-26 20:35 | sfernandez | Status | assigned => resolved |
| 2022-01-26 20:35 | sfernandez | Resolution | open => fixed |
| 2022-01-26 20:35 | sfernandez | Fixed in Version | => 3.1.3 |