View Single Post
Old 04-27-2018, 02:41 PM   #14
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,255
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by geek1011 View Post
I can have a FindZlibBaseAddress instruction which can take either: a checksum of the CSS, the CSS Id, or a unique string anywhere in the CSS.
I'm going to assume that your aim is for the creator/maintainer of each patch to have as little work to do as possible (ideally none at all) for each new firmware. If so the 3rd option is the one least likely to change between firmwares, assuming one chooses the unique string wisely, of course.

Quote:
Originally Posted by geek1011 View Post
Also, should I make an option to dump the CSS?
Yes - for those who create/maintain patches. Not necessary for the average user, though.
jackie_w is offline   Reply With Quote