After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 735707 - Cannot print larger than paper size
Cannot print larger than paper size
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: Plugins
2.8.10
Other All
: Normal enhancement
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2014-08-30 11:26 UTC by teo (Account deactivated)
Modified: 2018-05-24 14:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description teo (Account deactivated) 2014-08-30 11:26:19 UTC
Open an image, go to print -> Image Settings tab.

Here you can change the image size and its position within the page.

However, it won't let you scale the image to anything bigger than the paper size.
It should, so that you could be able to print an arbitrary portion of the image.

Now, if you want to print a portion of an image into a page where the whole image doesn't fit, you have to manually crop the image and then print it, which is painful.
Comment 1 Michael Natterer 2014-08-31 13:15:05 UTC
Seems like a useful addition to me.
Comment 2 teo (Account deactivated) 2014-08-31 14:03:52 UTC
I think it's wrong to consider this an enhancement (especially if that really implies a priority less than "minor" or "trivial").

There seems to be currently a restriction to the size of the printed image, that is, it is being restricted to no bigger than the paper size, and the margins are restricted to non-negative values. Having put those limitations is an error. Call it a bug or a design flaw, but it is a plain error, not something that may be enhanced.

This wrong restriction cripples a function as basic as printing, so it is of major importance.
Comment 3 Michael Schumacher 2014-09-18 11:19:13 UTC
Regardless of what you call it; unless someone writes the code, it will stay as it is. Changing its severity won't magically summon a coder with time to do that.
Comment 4 teo (Account deactivated) 2014-09-18 12:04:04 UTC
> Changing its severity won't magically summon a coder with time to do
that.

Oh, really? I thought it would :P

According to that argument, then the "severity" field is totally irrelevant and could be removed altogether from the bugtracker. 
If we use it, then let's use it right.

Assuming there _are_ coders with time to browse through bug reports, pick a bug and write the code to fix it, although of course nothing will force any particular coder to choose a given bug based on its severity alone, they're likely to look at most severe bugs first, right?

Setting the severity wrongly definitely won't help to fix most important bugs first.
Comment 5 Michael Schumacher 2014-09-24 07:58:48 UTC
I don't know if any coders take that into account - it doesn't even appear as a column in the bug listings by default, for example.

Getting an interface for printing an arbitrary portion of the image - complete with an UI for selecting and moving that - is definitely an enhancement that needs UI speccing, and not something that you can sneak in as a bug fix.
Comment 6 teo (Account deactivated) 2014-09-24 11:42:49 UTC
>Getting an interface for printing an arbitrary portion of the image - complete
with an UI for selecting and moving that - is definitely an enhancement that
needs UI speccing, and not something that you can sneak in as a bug fix.

You must be kidding.

That interface is already there, only it doesn't allow you to increase the size of the image beyond the page size, nor to move it to outside it.
The speccing was already done, and it was done wrong, by placing wrong restriction (e.g. the minimum value for x, or left margin, should not be zero, etc.) Only minimum and maximum allowed values need to be changed. 

The only potentially "tricky" part is that if image exceeds printable area, an implicit crop previous to printing (and displaying in the preview) may be needed - which is something that definitely _can_ be "sneaked in" as a bug fix.
Comment 7 Michael Natterer 2014-09-24 15:24:40 UTC
We are not kidding. If you know exactly that it's so easy, why don't
you provide a patch?
Comment 8 teo (Account deactivated) 2014-09-24 15:40:30 UTC
I didn't say it's easy (I kind of guess it probably is but I can't tell). I only said that it's not an enhancement that needs any UI speccing (or any non-trivial kind of speccing), just a bug due to wrong constraints. That doesn't mean it's necessarily easy to fix.

I'd happily try to provide a patch if I were fluent in C++ (or whatever language Gimp is written in).
Comment 9 GNOME Infrastructure Team 2018-05-24 14:33:10 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/577.