Feature request: mark what makes a version incompatible

Hello,

I have a small feature request for the VersionHistory.xml. It would be nice to have an optional attribute on the ChangeItem node that can mark this change item as incompatible. Then This change item gets a special highlight or small icon or something in the object browser version history and also when reloading STD in OES/CPS.

Reason: I often find myself wondering if I can update to a new incompatible version or if it would be too much of a hassle. So I have to browse the version history, identify which updates were incompatible ones and then scan those updates for the content and try to figure out why this update is supposed to be incompatible, which sometimes isn't easy. A little visual guide would be appreciated.

Any chance this will make it into future updates?

Best reply by nexidator

P.Klein : That's absolutely correct. But I don't think that's what MarvinW meant. Knowing that the new version is incompatible often doesn't help that much if you don't know why it is incompatible. Sometimes, it's just the required tool version being increased that makes the change incompatible. In other cases, the behavior may have changed so that changes in user code are required. At the moment, there is no easy way to find out what the incompatible change actually means for the user.

MarvinW : Once more a good idea! We will see if this can be improved...

View original

4

4 replies

Resolved