- Tim Rehder
- PowerBuilder
- Monday, 28 November 2022 11:28 AM UTC
Hello,
at our company we are currently in the process of migrating our relativly big PowerBuilder project to Git.
So far that has worked fairly well, but we have encountered an issue where it would be interesting to know how this was ment to work and how others are dealing with this.
The problem is that PowerBuilder moves the functions at the end of the exported source code of windows and other objects after they have been altered.
As long as only one person is working on that object this is not realy an issue. It is not ideal since you cannot see the actual changes that were made to the object, but only that the whole function has moved to the end of the source code. But this is not realy a big deal to us.
The actual problem are merge conflicts with such objects.
That is because you have to copy every modified function from the source code to a different comparrison tool to check if the function has been modified and then try to manualy pease these thigs together.
We have a few very big windows with a lot of functions and events.
As soon as two or more people have worked on one of those objects at the same time it is everything but easy to merge them together at the end.
Has someone here had some expirience with this problem and any ideas how we can avoid it in the future?
Are there any plans from appeon to approach this issue with the rearanged code in the exported files? Maybe an option in the PowerBuilder settings so that functions and events are exported in alphabetical order?
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.