View Single Post
Old 05-29-2019, 02:57 PM   #12
jackie_w
Grand Sorcerer
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by GeoffR View Post
Maybe this would work? The replacement value can be any number 0-255.
Code:
Increase TOC level indentation:
  - Enabled: yes
  - PatchGroup: TOC Indentation
  - Description: |
      The space indented Table of Contents levels are quite hard to see, as the
      difference is almost too small to easily notice.
  - ReplaceBytes: {Offset: 0x8B2FD6, FindH: 42 00 4F F0 20 01, ReplaceH: 02 22 42 43 20 21}
  # Replacement value:
  - ReplaceInt: {Offset: 0x8B2FD6, Find: 2, Replace: 6}
I really like the customisability (is that a word?) of this, but I do like geek1011's fix to have top-level items not indented (which seems like a bug to me, but calling it that seems to have created a bit of tension earlier today).

Having both would be great, if it was possible.

ETA: I see geek1011 got in first.

Last edited by jackie_w; 05-29-2019 at 02:59 PM. Reason: ETA
jackie_w is offline   Reply With Quote