Is there a way to mark plugins as incompatible?

Programming Kaleidoscope Internals
1

I’m working on designing a plugin that I believe would be incompatible with TopsyTurvy, because both would alter the state of the shift modifiers, and probably cause undesired behaviour if both were used in the same sketch. I’m wondering if it would be a good idea to have mechanisms in the compilation that would allow plugins to declare that they want ownership of certain classes of behaviour to prevent conflicts of this sort.

Or is this idea more trouble than it’s worth, and we should leave it to plugin authors to try to warn users of the possible conflicts they might encounter?

1 Like
2

There isn’t such a way at the moment. I’m not sure we can implement compile-time conflicts in a way that isn’t too complex.

Documenting it in the README is, in my opinion, the best way, all things considered.

3 Likes