Mixing LexActivator and LexFloatClient static lib versions

My application links in both the LexActivator and LexFloatClient static libs. I assume LexFloatClient could well itself be using LexActivator behind the scenes; could that give a clash when versions are mixed? For now I’ve thus always religiously been matching them by release date (for as much as possible anyways), but I wonder if that is strictly needed?

If matching versions is indeed a thing, it would be nice if both products would share the same version numbering scheme.

Hi @CarlColijn,

Thanks for reaching out!

LexFloatClient and LexActivator do not have any such dependency, however, we still recommend utilizing the latest versions of both.

If you’re experiencing any issues, please feel free to let us know!

1 Like

Thanks for the heads-up! I’m free to lose that religion then :slight_smile:

1 Like