Skip to content

Specify dimensions when saving an image #7300

Description

@stevenpaligo

What's your use case?
Visualizations, like the scatter plot, allow you to save an image. The dimensions of the resulting image appear to be based on the plot's window size when hitting the "Save Image" button.

I would like to be able to save images with consistent dimensions each time I run the workflow. I can resize the image outside of Orange, but that tends to make things like the axis labels unreadable. Therefore, the image would need to be rendered for a viewport that matches the specified dimensions.

Additionally, it would be great if the dimensions could be saved in the widget's configuration so they didn't need to be specified each time an image is saved.

What's your proposed solution?
When the user presses the "Save image" button on a visualization, they are prompted to specify dimensions. The first time they save it, the default dimensions match the window size. If the user changes those values, then subsequent attempts to save the image uses the new values as the default.

It would be nice if the dimension override values were specific to that instance of the widget (i.e., did not affect others in the workflow) and they persisted in the .ows file the next time it was opened.

Are there any alternative solutions?
I don't think so.

Activity

  1. self-assigned this
    on Jun 19, 2026
  2. janezd commented on Jun 19, 2026

    @janezd
    Contributor

    Thanks for the suggestion. Just a note from the core group meeting: seems doable, but we need to see whether the fonts (e.g. on axes) will scale appropriately. If they do, we should have this for all widgets.

  3. removed their assignment
    on Jun 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions