Footer menubar reduction

[MGlitch]

I know there's a patch to reduce the menubar in the header, but what about the footer?

I only recently tried the header one, and was surprised by how much I liked it. Even though I don't see it often, it's nice to have it reduced down so there's less white space.

[jackie_w]

Originally Posted by MGlitch

I know there's a patch to reduce the menubar in the header, but what about the footer?

There's the patch called `Custom reading footer style` in the nickel.patch file. It doesn't actually shrink the footerbar but it does reduce the amount of vertical space used by the 'page x of y' progress footer whilst reading.

I searched in vain to replicate the headerbar patch for the footer. There were several potential candidates but none of them actually reduced the footerbar ... except for one. It is possible to reduce the height of the Search footerbar when searching for a word in the current book. I use it on my own devices but I haven't published it because I haven't read of any pent-up demand for such a feature.

[ItalianUruguayan]

Originally Posted by jackie_w

There's the patch called `Custom reading footer style` in the nickel.patch file. It doesn't actually shrink the footerbar but it does reduce the amount of vertical space used by the 'page x of y' progress footer whilst reading.

I searched in vain to replicate the headerbar patch for the footer. There were several potential candidates but none of them actually reduced the footerbar ... except for one. It is possible to reduce the height of the Search footerbar when searching for a word in the current book. I use it on my own devices but I haven't published it because I haven't read of any pent-up demand for such a feature.

I am curious about it. Would you mind to share?

[jackie_w]

Originally Posted by ItalianUruguayan

I am curious about it. Would you mind to share?

Assuming you're asking about my Search footerbar comment ...

The CSS stream I modified in fw4.7.10413 is in the nickel file.

Using the pipcat-method (I noticed in another recent thread that you're already familiar with this) it is the zlib stream beginning:

/* found: 83 (zlib) pos: 45cc58 */
#SearchMenuView[qApp_deviceIsTrilogy=true] {
  max-height: 71px;
  min-height: 71px;
}
#SearchMenuView[qApp_deviceIsPhoenix=true] {
  max-height: 91px;
  min-height: 91px;
}
#SearchMenuView[qApp_deviceIsDragon=true] {
  max-height: 121px;
  min-height: 121px;
}
#SearchMenuView[qApp_deviceIsDaylight=true] {
  max-height: 157px;
  min-height: 157px;
}

The only changes I made are to the above code where I reduced the max/min-heights to something smaller. I see you have a GloHD in your Info details, so using this as an example I reduced both values of 121px to 80px.

For anyone reading this and wondering why I bothered ... the only reason I applied this extra patch is because I have also applied the `Custom reading footer style` patch to reduce the height of the 'Page x of y' footer. If you've done that and then run a 'search in book' query, the Search results footer covers the bottom line(s) of book text which is a nuisance if the word you've searched for is on the bottom line(s). It doesn't really happen often enough to be a serious problem for me but it was easy enough to remove the issue by applying this extra patch at the same time as the rest of my list of nickel patches via the pipcat-method.