GNOME Bugzilla – Bug 649714
Remember "Gnumeric Print Range" settings
Last modified: 2011-05-23 07:58:15 UTC
Currently when you press Print and go to the "Gnumeric Print Range" tab and change from the default setting ("Active workbook sheet"), Gnumeric does not remember the settings even during the same session. Next time you open the Print dialog, the setting has been reset to "Active workbook sheet". I propose that this should be saved either per-document or as a general setting for the application. Either way would be better than now. Thanks :)
Hmm, we are already saving that information (on an application wide basis) but on print after restoring the information we seem to intentionally overwrite it. I need to figure out why that was done.
Oh, that's weird - and wonderful :) I actually started diving into the printing code and tried to find out how to fix the other bugs I filed today; bug 649711 and bug 649713. My 30-minute quest stopped when I tried to understand gnumeric-gconf.c:gnm_conf_get_printsetup_gtk_setting(void), but perhaps I will take another look some day when my schedule allows it! But I digress. Could I present the case for storing the print range on a per-document basis, at least for .gnumeric files - and perhaps just fall back to application-level settings on imported documents?
This is not saved and restored as an application setting. I agree that for gnumeric files (and probably any other file format that support such a setting) it should be stored in the file. I suspect that enhancement will take significantly more work though! (I would also think that it should not be automatically saved in the file since you may just do a one-up test print that should not be saved in the file.
I disagree, any such settings should be applied and saved without confirmation just like regular Gnome preferences. If you're doing a one-off test print you remember what you changed for testing purposes anyway :) But yeah, I can imagine it would be a lot of work! Especially for me since I don't know GTK or any of the supporting libraries really. I wish I had the time to dive in.
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.