Therefore, I would read 500 lines for both files inside the FileManager. Considering the appending process for the edit controls is relatively slow, I decided to load 500 lines, and then append the whole packet at once. The FileManager receives both FileEdits from the main class which is the GUI class for the whole dialog.Īs soon as the files are entered in controls dedicated to that, the file manager receives the paths and starts to load the files for both FileEdits. This gives me a base to build on if I want to add certain keybind features later on.īoth FileEdits are being managed by a 'FileManager'. This class is the GUI class at the same time, and receives events like button press, clicks etc. The current implementation I have in mind looks like this:Įach edit control is an object of 'FileEdit'. I could kind of add a reference to the file which I want to compare the original file to in the class of the original file, but I would rather have a dedicated class responsible for all managing and comparing. Of course, I could just add a method to make them load their file, and display it, but that won't help, as I'm not writing an editor, but rather a comparison tool. I have a custom control for each of the 2 edit controls, which are showing the respective file content.

However, I am now sitting here, thinking about a design on how to manage the whole file comparison and the data flow.

I am using C++ with the Win32-API (WTL, ATL, that stuff), and I already designed an UI for this.

My current project is to implement a kind of WinMerge clone to compare two files.

Winmerge compare files date modified