|  | 
|  | 1 | +# Version 0.2.9.0 - (2020-09-05) | 
|  | 2 | +#### Note: Since I am taking up a software developer role next week, releases are going to slow down for the foreseeable future. | 
|  | 3 | +## Known Bugs | 
|  | 4 | +- The GUI can sometimes become unresponsive during morphing calculations (but eventually returns to normal) | 
|  | 5 | +    - QtCore.QCoreApplication.processEvents() is a potential workaround but currently produces buggy results | 
|  | 6 | +     | 
|  | 7 | +## Added | 
|  | 8 | +- <b>Source Image Resizing</b> | 
|  | 9 | +    - Since PIM requires the user's images to be the same size, it can now create and hotswap resized copies of the left/right images at the click of a button | 
|  | 10 | +    - For simplicity, one button resizes the left image to the right image's dimensions and the other button does the opposite | 
|  | 11 | +        - Both images must be loaded to enable this functionality | 
|  | 12 | +        - Additionally scales any added/confirmed/chosen points to the new image dimensions | 
|  | 13 | +        - Buttons will be set to <b>bold</b> whenever the user's images aren't the same size | 
|  | 14 | +    - Resized image files are stored under: <b>ROOT_DIR/Images_Points/filename-[width]x[height].filetype</b> | 
|  | 15 | +    - Resized text files are stored under: <b>ROOT_DIR/Images_Points/filename-[width]x[height]-filetype.txt</b> | 
|  | 16 | +         | 
|  | 17 | +## Changes | 
|  | 18 | +- The program now locks out usage of point placement as well as the <b>Add Corners</b> button when the user's images aren't the same size | 
|  | 19 | +    - Comment: <i> This is to really drive the point home: fix one of your images or you'll just be wasting your time!</i> | 
|  | 20 | +- Moderate rewrite of <b>loadDataLeft()</b> and <b>loadDataRight()</b> | 
|  | 21 | +    - New helper function: <b>checkFiles(sourceFunc, basePath, rootPath)</b> | 
|  | 22 | +    - Text files are now stored under: <b>ROOT_DIR/Images_Points/filename-filetype.txt</b> | 
|  | 23 | +    - Comment: <i> While polishing these, I found that due to how the functions were written, it was possible for the program to  | 
|  | 24 | +    generate text files with varying naming schemes.. some ended with 'filename.txt', others ended with 'filename.FILETYPE.txt'. | 
|  | 25 | +    This has been streamlined into a more readable 'filename-filetype.txt' - images that share a name but differ in type should | 
|  | 26 | +    play more nicely with this change. | 
|  | 27 | + | 
| 1 | 28 | # Version 0.2.8.2 - (2020-08-26) | 
| 2 | 29 | ## Changes | 
| 3 | 30 | - Support for morphing two images of different sizes, while initially left up in the air as a potential feature, is no longer being considered | 
|  | 
0 commit comments