Quote:
Originally Posted by ixtab
That's not a bug, it's a feature 
What the display actually tells is how many classes could theoretically be patched (20), and how many have actually been patched (14). It is normal for these numbers to both be higher than the number of patches (a single patch can change many classes), and to be less than the maximum (not all potential changes will be applied: the TTS patch can change 6 classes, but will at most change 2 of them at runtime). The number of applied patches can even change at runtime, because a patch only gets applied when its "target" class gets loaded. This is also (more or less) documented in the README.txt of version 1.3.1. |
Ahh...
Will the "jbpatch with no reboot" go away if the patches are again stored in /mnt/us or do you have plans for a way to copy all jbatches from /mnt/us to /var/local when the configuration ui starts?