"Exclude From Sync" and "Remove From This List" Features Don't Persist - Bug?

[Funkybot's Evil Twin]

Because "old major versions" get flagged as being out of date in the "KVR Newer" list, and I have a LOT of those, I'd like to remove them from the sync, and remove them from that list permanently.

Example: I have like 50 T-Racks 5 versions, and it's flagging them as out of date because there's a new T-Racks 6 I haven't upgraded to. So I don't want to see those, since those are the latest versions of version 5 and I don't intend to upgrade. Even Arturia stuff like Jup-8 V3 gets flagged as out of date, despite me having Jup-8 V4 and the latest version of that.

Anyway, "Exclude from Sync" and "Remove from list" seem to work UNTIL I "scan for new/updated plugins" and "sync with KVR again". After that, all the plugins come back in the "KVR Newer" list.

[MrJubbly]

Because "old major versions" get flagged as being out of date in the "KVR Newer" list, and I have a LOT of those, I'd like to remove them from the sync, and remove them from that list permanently.

Example: I have like 50 T-Racks 5 versions, and it's flagging them as out of date because there's a new T-Racks 6 I haven't upgraded to. So I don't want to see those, since those are the latest versions of version 5 and I don't intend to upgrade. Even Arturia stuff like Jup-8 V3 gets flagged as out of date, despite me having Jup-8 V4 and the latest version of that.

Anyway, "Exclude from Sync" and "Remove from list" seem to work UNTIL I "scan for new/updated plugins" and "sync with KVR again". After that, all the plugins come back in the "KVR Newer" list.

But there should be a better way to accommodate certain "updates vs upgrades?" with major releases of plugins?

For example, many people who have FabFilter Pro-Q 3, will also have Pro-Q 2 and the original v1 always installed side-by-side on our devices (and will always continue to) for (backwards compatibility with) our older projects. Which is why such developers still allow users to download those older depreciated, or even discontinued projects from their websites.

Also, there are the types of upgraded plugins which update and overwrite ("over-the-top") of previous versions. Like Synplant v2, which when upgraded and installed, effectively replaces v1. However, some users maybe haven't upgraded to v2 (or don't want to?).

So in addition to standard "updated" plugins. There are also major "upgrades" which can either exist side-by-side with previous versions of the same plugin. Or outright replace their former versions.

Sounds complicated. But there could be some simpler methods to "tame" these types of products or settings to tailor such types of plugins for the KVR Studio Manager.

[Funkybot's Evil Twin]

Honestly, I don't think the logic would be too complex to exclude automatically. Example:

Current Version 2.5.2
Latest Version 3.0.1

Take a LEFT(1) type of thing to get the "Major Revision" number...

Current Major Revision Number: 2
Latest Major Revision Number (from KVR): 3

IF Major Revision Number does not match, THEN exclude. If same, show newer version available...

Current Version 3.0.0
Latest Version 3.0.1

...The logic seems pretty easy. But I'm not a programmer. So everything seems easy.

That said...the next best thing would be exclude functionality that persisted.