View Single Post
Old 11-11-2014, 12:59 AM   #154
GeoffR
Wizard
GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.
 
GeoffR's Avatar
 
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
Quote:
Originally Posted by rogerinnyc View Post
I apologize, but I'm a noob with Kobo and patching. I was able to follow the instructions in post 1, without doing any customization of any of the libnickel files, and it did a great job in reducing the bottom margin on my new H2O. But I'm not getting it in terms of further customization (e.g. I would like to increase the padding on the footer).

I'm using Notepad++ to open the libnickel file with the custom footer patch, but what exactly am I changing? When I delete all (or frankly any) of the # signs before the example lines for H2O (e.g., lines 41 through 46) and then run the 3.11.0.bat file, I get a replace_string mismatched data error for whichever line I removed the # sign from. But I haven't done anything but delete the # character and then save the file. Am I supposed to uncomment all the replace_string lines in the H2O example? Do I do anything with the main entry of the patch (e.g., line 17)? Is there something more to uncommenting than deleting the hashmark?

Any guidance would be much appreciated! Thanks.
As well as uncommenting (removing the '#' from) the example you want, you also need to comment out (add a '#' to) the examples you don't want. Only one example can be active (uncommented) at once.

E.g. after choosing the H2O example it should look like this:
Code:
# Example for Glo/Aura:
#replace_string = DBDC0D, `min-height: 70px;`, `min-height: 40px;`
#replace_string = DBDC20, `max-height: 70px;`, `max-height: 40px;`
#replace_string = DBDC3D, `footerMargin: 105;`, `footerMargin: 105;`
#replace_string = DBDC58, `font-size: 16px;`, `font-size: 20px;`
#replace_string = DBDC6A, `padding-bottom: 0px;`, `padding-bottom: 5px;`
#replace_string = DBDC80, `margin-top: 0px;`, `margin-top: 0px;`
#
# Example for AuraHD/H2O:
replace_string = DBDC0D, `min-height: 70px;`, `min-height: 50px;`
replace_string = DBDC20, `max-height: 70px;`, `max-height: 50px;`
replace_string = DBDC3D, `footerMargin: 105;`, `footerMargin: 170;`
replace_string = DBDC58, `font-size: 16px;`, `font-size: 26px;`
replace_string = DBDC6A, `padding-bottom: 0px;`, `padding-bottom: 8px;`
replace_string = DBDC80, `margin-top: 0px;`, `margin-top: 0px;`
#
Edit: Once that is done, to increase the padding (space between bezel and bottom of footer text) change the replacement string in the padding-bottom line, without increasing the length of the replacement string. E.g. to add an extra 10 pixels (note that the extra digit relaces the leading space):
Code:
replace_string = DBDC6A, `padding-bottom: 0px;`, `padding-bottom:18px;`

Last edited by GeoffR; 11-11-2014 at 01:10 AM. Reason: change padding example
GeoffR is offline   Reply With Quote