Let the user edit the range of each axis on a scatter plot.

[R180]

Description

Currently, users can edit a plot, but not if it's 'complex' in that it consists of multiple plot objects. All of the ways of getting a scatter plot in JASP involve complex, multiple plot objects.

Purpose

No response

Use-case

Eg., a user may want each axis to cover the entire range of the variable being plotted.

Is your feature request related to a problem?

No response

Is your feature request related to a JASP module?

No response

Describe the solution you would like

In DESCRIPTIVES / BASIC PLOTS / CORRELATION PLOTS, make the produced scatter plot a truly basic plot so that it can be edited.

Describe alternatives that you have considered

No response

Additional context

No response

[tomtomme]

I just found an old issue discussing this:
#1354

There are several workarounds for you at the moment:

• Save the plot as pptx and edit it in Powerpoint.
• plot the scatterplot with visual modeling => flexplot

This is certainly only a temporary solution until we can make multiplots editable.
Your request mentions another possible workaround (renounce multiplots in descriptives), which might also be a nice solution. Which solution would you prefer? Or is one of the workarounds above already sufficient?

Related: jasp-stats/jaspGraphs#72

[R180]

Hi. Thanks. Unfortunately, I don't think there are any workarounds at the moment. Pptx files are graphic files that permit editing things such as line colors, text, and fonts, but not the data-range of an axis. Flexplot could work in principle. However, there's a current bug in flexplot that permits editing the scatterplot's x axis range but prevents editing the scatterplot's y axis range (see below). So I think the flexplot option would be fine if the bug were fixed.

[tomtomme]

I tried again with current beta and the flexplot error persists. But not for every data set. I can change axis on small data sets.
But with bigger ones like the big5 I can produce the error:

b5.jasp.zip

@dustinfife
Can you also reproduce this error with the above data?