Hi, I have several problems with the git extension.
Situation:
I am working with Codesys v3.5 SP19 Patch 1 and Git V1.2.1.0. The remote repository is GitLab Community Edition v16.1.2. I am working on a project with one other person.
Problems:
1: After each start of Codesys all of the visu pages are marked as modified. So we have to discard all changes first. Otherwise the history is not clean and the merge request becomes more complex.
I tested it with a new project and only local. I made the observation, that a page is not marked as modified when it is committed a second time (after a restart of codesys). But this is necessary after every change of a page. However, since we are working in a team, it seems we are playing ping-pong and so all pages are marked as modified on each startup.
2: Each image pool causes a parent child conflict. Also in my local project. The only solution that I have found, is to ignore the issue.
Does anyone have the same problems?
I think it looks more like bugs.
I was able to duplicate this same issue with Visualization 4.4.0.0 and experienced the same results as you. After saving and closing the project and then reopening, the visualization is marked as modified with an orange rectangle. However, when doing a compare, the message reveals that the two commit objects are the same. This seems like a bug and I will investigate further.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
By the way, a file (Program, Function, ...) is also marked as modified if it was edited but the change was undone directly. The comparison recognizes that both objects are the same, nevertheless the status remains on modified.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I have several problems with the git extension.
Situation:
I am working with Codesys v3.5 SP19 Patch 1 and Git V1.2.1.0. The remote repository is GitLab Community Edition v16.1.2. I am working on a project with one other person.
Problems:
1: After each start of Codesys all of the visu pages are marked as modified. So we have to discard all changes first. Otherwise the history is not clean and the merge request becomes more complex.
I tested it with a new project and only local. I made the observation, that a page is not marked as modified when it is committed a second time (after a restart of codesys). But this is necessary after every change of a page. However, since we are working in a team, it seems we are playing ping-pong and so all pages are marked as modified on each startup.
2: Each image pool causes a parent child conflict. Also in my local project. The only solution that I have found, is to ignore the issue.
Does anyone have the same problems?
I think it looks more like bugs.
Thanks
ewi04
Last edit: ewi04 2023-11-22
Hi,
these problems are related to the Visualization Addon.
The parent child conflict is resolved when you use Visu 4.3.0.0
Hello stsch,
thank you for your answer!
Do you think this is a normal behavior or the wrong place for my issue?
Unfortunately I have the conflict with the Visu 4.3.0.0.
Last edit: ewi04 2023-08-07
I was able to duplicate this same issue with Visualization 4.4.0.0 and experienced the same results as you. After saving and closing the project and then reopening, the visualization is marked as modified with an orange rectangle. However, when doing a compare, the message reveals that the two commit objects are the same. This seems like a bug and I will investigate further.
Hello, thanks for your efforts. I am curious about your results.
By the way, a file (Program, Function, ...) is also marked as modified if it was edited but the change was undone directly. The comparison recognizes that both objects are the same, nevertheless the status remains on modified.
The problem (2) with the parent child conflict is resolved with Codesys V3-5 SP19 Patch 2 (Visu 4.4.0.0). The other issues unfortunately not.
The problem with the visu pages marked as modified after starting Codesys has been solved with visu 4.5.0.0. Now working together is more fun!
Notice: I had to recreate the alarm groups.