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 766951 - Enable identical grid of transformation and image.
Enable identical grid of transformation and image.
Status: RESOLVED DUPLICATE of bug 754517
Product: GIMP
Classification: Other
Component: User Interface
2.8.16
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2016-05-27 21:13 UTC by Bertje
Modified: 2016-05-27 21:44 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Example. (158.99 KB, image/jpeg)
2016-05-27 21:13 UTC, Bertje 		Details

Description Bertje 2016-05-27 21:13:25 UTC 
Created attachment 328653 [details]
Example.

I am currently using the perspective transformation for buildings. Like in the example.

I realised it would be convenient to initially align the transformation grid with the image grid. That way one can more easily numerically estimate the transformation relative to the image.

Currently this is hard to do. 
- The transformation grid apparently is both horizontally and vertically on every 1/16th of the image. This means that on a 3 x 4 image that grid is rectangular, either in portrait or in landscape, following the image.
- The image grid is set in pixels or mm. 
- To get the two aligned I would have to calculate 1/16 of the current image dimensions AND consider the current orientation. That is a hassle.

What I suggest is to enable BOTH grids to be set RELATIVELY to the image, like to 1/16th.
Comment 1 Bertje 2016-05-27 21:25:17 UTC 
As I notice now, is in fact:
https://bugzilla.gnome.org/show_bug.cgi?id=754517
Comment 2 Michael Schumacher 2016-05-27 21:44:27 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 754517 ***