Thank you for the feedback! I will release a small update in the next few days to support the new Kobo Elipsa 2E.
Quote:
Originally Posted by JSWolf
I agree. It's not overkill. Without this, this patch GUI is not useful at all (IMHO).
|
I understand your frustration. Maybe you can explain again in detail and in detail and maybe with a layout diagram how you imagine it best.
My approach would be like this:
- Add a checkbox "Keep track of this patch" for each patch.
- If checked, the code of the patch is written to a separate file.
- The patches saved in this way are displayed in a new tab. There is a button "Compare this patch with the fresh patch". The changes... I don't know how to show the changes. The old code on the left and the new code on the right?
- There must be an option to edit the saved patch code directly to adapt it to the fresh patch if necessary. And then there is a button "Overwrite fresh patch file" to write the saved patch into the fresh patch file and thus overwrite the fresh patch with your own patch.
But that's so much stuff again and somehow I don't feel it. Maybe I'll just implement a comparison of the complete .yaml files in a new tab? Then you could see at a glance what has changed. Maybe that would also be clearer?