Quote:
Originally Posted by geek1011
Yes, but you will need to compare the output manually (the checksums).
|
I can do checksums easily enough. Why didn't I think of that
Quote:
Originally Posted by geek1011
Yes. I'm still working out how to extract the strings efficiently, but I'm making progress so far. If @GeoffR has any tips, they would be useful. I am also looking for ideas on how everyone wants this feature to look (simple find/replace, find by CSS ID, etc).
|
Some comments based on my experience of using the pipcat-method...
I'm not sure CSS Id (e.g
/* found: 116 (zlib) pos: 45e7e8 */) is any help because the id number (116 in my example) changes with every firmware, even if the CSS content itself hasn't changed.
I believe it's always possible to define a unique string to identify the required CSS stream, (e.g. #N3TableOfContentsWidget[qApp_deviceIsTrilogy=true]), but you can't rely on being able to find a unique string which starts at the first character in the stream.