GNOME Bugzilla – Bug 562366
Default image dimensions are not correctly transferred in the file/new dialog box
Last modified: 2008-11-27 07:32:28 UTC
Please describe the problem: When the default image dimensions are set to e.g. A4 (209.97 x 297.1 mm) in the Edit/Preferences/Default Image menu, the File/new dialog box indicates improper dimensions (874.86 x 1237.57). Need to click on the reset button to get the good dimensions. Steps to reproduce: 1. Select for example Template = A4 (300 ppi) in the Edit/Preferences/Default Image menu. 2. Restart Gimp 3. Create a new image using the File/New menu. Actual results: The dialog box indicates wrong dimensions. Expected results: The dialog box should indicates good dimensions ;-) Does this happen every time? Yes. Other information: Seems to affect all "A" templates (A3, A4, A5...). Affects Linux 2.6.1 version as well as Windows 2.6.3 version (previous versions not tested).
Hi and thanks for the bug report! The fix/hack for the New Image dialog made in connection to bug 546924 needed to be copied to the Default Image-place in Preferences as well. Fixed in trunk (revision 27720) and gimp-2-6: 2008-11-26 Martin Nordholts <martinn@svn.gnome.org> Bug 562366 – Default image dimensions are not correctly transferred in the file/new dialog box * app/dialogs/preferences-dialog.c (prefs_template_select_callback): We need to copy the template in the same way as in the New Image dialog.
That only seemed to have fixed the problem during the lifetime of the session; the values saved to gimprc is still wrong. Reopening...
gimprc was fine (I forgot that width and height are always in pixels there) it was just another order-dependent copying that was needed which I have commited to trunk (rev 27724) and gimp-2-6: * app/dialogs/image-new-dialog.c (image_new_dialog_set): ... and when we copy the template to the New Image dialog. I noticed some other issues with templates as well where "invalidation" is not handled properly That is however a separate issues (which existed also in 2.4) so I'm closing this as FIXED now. I will file a separate bug report(s) of the discovered problems later.