Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Format Data Series (ScatterChart) #1452

Closed
cwolcott opened this issue Apr 24, 2020 · 2 comments
Closed

Format Data Series (ScatterChart) #1452

cwolcott opened this issue Apr 24, 2020 · 2 comments

Comments

@cwolcott
Copy link

cwolcott commented Apr 24, 2020

This is:

- [ ] a bug report
- [X] a feature request
- [ ] **not** a usage question (ask them on https://stackoverflow.com/questions/tagged/phpspreadsheet or https://gitter.im/PHPOffice/PhpSpreadsheet)

What is the expected behavior?

To be able to provide attributes to format data series. Specifically in a ScatterChart for now.

What is the current behavior?

Currently can not provide line attributes to format a data series.
Only the marker style and fill.

Which versions of PhpSpreadsheet and PHP are affected?

1.11.0

The chart below is a ScatterChart made up of 5 Data Series.

  • The 1st data series has 320 values from 1 to 320 and is represented by the blue, nofill, circles.

  • The 2nd and 3rd data series has 2 values at 1 & 320. It is represented by the green transparent dashed line with head/tail triangles and no markers. It is showing the HIT boundaries above and below the lines.

  • The 4th and 5th data series has 2 values at 1 & 320. It is represented by the red transparent dashed line with head/tail triangles with no markers. It is showing the EXCLUSION THRESHOLD boundaries above and below the lines.

image

After reviewing the Xlsx/Chart.php code, and reviewing what is stored in the xl/charts/chart1.xml archive file in the excel spreadsheet I have determine what the format is to correctly configure the chart.

I currently have this working now in the code (backward compatible), but am now trying to determine the most appropriate way to introduce this into the code baseline.

@stale
Copy link

stale bot commented Jun 23, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If this is still an issue for you, please try to help by debugging it further and sharing your results.
Thank you for your contributions.

@stale stale bot added the stale label Jun 23, 2020
@stale stale bot closed this as completed Jul 3, 2020
@oleibman
Copy link
Collaborator

Fixed by PR #2828.

@oleibman oleibman removed the stale label Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants