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

Revive ScalyPlot #744

Merged
merged 2 commits into from
Jun 1, 2021
Merged

Revive ScalyPlot #744

merged 2 commits into from
Jun 1, 2021

Conversation

aaronayres35
Copy link
Contributor

@aaronayres35 aaronayres35 commented May 28, 2021

ScalyPlot was removed in #667, however it is still used / needed.

It was independent of any other aspect of chaco.shell and is brought back here to simply sit in chaco.scaly_plot.py.

NOTE: we are planning some internal reorg (see #738), so this module may be moved in the future.

It should be imported for the api module (I will add it to the api in this PR)

@rkern
Copy link
Member

rkern commented May 28, 2021

#738 isn't relevant. ScalyPlot is like Plot, not like the PlotRenderers that you are moving.

Thank you!

Copy link
Contributor

@rahulporuri rahulporuri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly LGTM

)

def _index_scale_changed(self, old, new):
Plot._index_scale_changed(self, old, new)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not entirely sure how this works. Shouldn't this be super()._index_scale_changed(old, new)? Same comment below with Plot._value_scale_changed(...)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, super makes more sense / is cleaner here. This code I believe is also untested, I simply copy pasted the old file to revive it.
It could probably use a closer look / some updates / some new tests. I can do so in some follow up PRs

@rahulporuri
Copy link
Contributor

Nice catch. How'd you notice it?

@aaronayres35
Copy link
Contributor Author

Nice catch. How'd you notice it?

There was a slack discussion which Robert tagged me in asking to revive it.

@aaronayres35 aaronayres35 merged commit 46038ef into master Jun 1, 2021
@aaronayres35 aaronayres35 deleted the revive-scaly-plot branch June 1, 2021 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants