Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.3.1
-
Fix Version/s: 6.3.2
-
Component/s: Core/Parsing, Core/Rendering
-
Labels:None
-
Environment:any
-
Support Case References:Support Case 14382;- https://icesoft.my.salesforce.com/5000g00001wIoFl
Description
A community member has submitted a file that has missing a bunch of graph data. The lines in question are vector based and use a dashed line type. Further analysis is needed but the dash sequence or parsing of it is likely the issue.
Activity
Field | Original Value | New Value |
---|---|---|
Fix Version/s | 6.3.2 [ 13175 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #52705 | Mon Aug 27 21:01:23 MDT 2018 | patrick.corless | |
Files Changed | ||||
![]() |
Support Case References | Support Case 14382;- https://icesoft.my.salesforce.com/5000g00001wIoFl |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #52871 | Thu Jan 10 21:33:35 MST 2019 | patrick.corless | |
Files Changed | ||||
![]() |
Turns out the root of the issue is related to how we restore the graphics state with regards to stroking or non stroking values. Will need to do a full qa round on this as it a big change to the rendering core but it does make sense that we shouldn't add new alpha values on the stack, they will get put there on a F or f call later.