@thomthom said:
@dan rathbun said:
The registration script adds 4 patches to the Preferences (dialog) > Extensions (panel) list.
Why have a patch in the extension list? Why would an end user ever need to enable/disable this? Don't you think it can cause confusion?
@dan rathbun said:
I have separated each patch into it's own file, so it can be switched on/off, tested and updated individually.
Formost.. for testing.
But as sometimes happens, patches can either introduce other unforseen issues, or perhaps a very popular plugin relies on some quirkiness that the patch fixed. Because it may be large and complex, the author of this "example" popular plugin, needs time to update his code.
So the patch can be switched off.. until an update is issued.
Patches, in general: I have thought many times upon a patching system, similar to the extension system. I imagine it having it's own checklist, separate from the plugin checklist.