About nexidator

Are you actually using a 1280x800 display? Most 15" displays are 1366x768. That would explain the missing height. ... View more

We have just released a new version of the EventRecorder Service (V1.5.10). Maybe it's worth a try updating to this version. ... View more

One more hint concerning 2: I guess you are using the EasyPanel add-on, which contains a dependency to the ModeHandlerTemplate allowing several versions. In general, when an object contains a BaseRef or Using allowing several versions, Object Browser selects all applicable versions of the referenced object. It should not select objects referenced as "Dependency", but it currently does. These two points are already in our backlog. What I cannot reproduce is that the ModeHandlerTemplate wasn't even selected before it was downloaded. When I select the EasyPanel, several ModeHandlerTemplate versions are selected. And another hint concerning 3: The import from the ObjectVersions.xml does not consider the object versions. It will always download the latest version. It's also on our list to improve the function so it tries to download compatible versions at least. But still I am not sure if the function would be a good replacement for backing up the Std folder. Maybe it is good enough for a BaseStation project if you don't care if the exact same object versions are used every time. ... View more

About piont 1: I understand your suggestion and it might have been a good idea to start like this 9 years ago, although I am not even sure about this. I think it is still easier to understand that higher version numbers are higher... 😉 But I definitely don't think it is a good idea to change the behavior now. It's not only the object browser but also Control plus Studio that is affected by such a definition. And as object definitions are often usable by many OES/CpStudio versions it is impossible to get a consistent behavior in all tools if we change this definition. So, the way Thorsten suggested is the right direction. About incompatible versions: Yes, the test version needs to show the incompatibility as well. For instance, when you are planning to move from 1.2.3.0 to 1.3.x you should start the test versions at 1.3.0.1. This means that the first release will be 1.3.1.0. That way, 1.3.0.0 will never exist, but I don't see a technical problem with that. ... View more