Rev 424 | Rev 442 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
| Rev 424 | Rev 440 | ||
|---|---|---|---|
| Line 3... | Line 3... | ||
| 3 | ================== |
3 | ================== |
| 4 | 4 | ||
| 5 | ToDo for the next release |
5 | ToDo for the next release |
| 6 | ------------------------- |
6 | ------------------------- |
| 7 | 7 | ||
| 8 | * Make some parts of the code Unicode aware. Note that Photoshop itself (PIPL etc) doesn't seem to be Unicode aware, and PARM is also not Unicode aware. So the Title/Category/... stays ANSI! But we should allow that filters are loaded/saved from File Dialogs that can read/save Unicode folder names. |
8 | (None) |
| 9 | - | ||
| 10 | 9 | ||
| 11 | Known bugs |
10 | Known bugs |
| 12 | ---------- |
11 | ---------- |
| 13 | 12 | ||
| 14 | * SEVERE: After working with Filter Foundry for a short amount of time (working with sliders, applying, opening again, changing sliders, etc.), the file save dialog (Make dialog) will corrupt the memory!!! You notice it by seeing that icons and folder icons are missing! Later, the program might even crash! (Verified with 1.7.0.12, verified with Visual Studio and OpenWatcom) Application Verifier does not report anything bad. |
13 | * SEVERE: After working with Filter Foundry for a short amount of time (working with sliders, applying, opening again, changing sliders, etc.), the file save dialog (Make dialog) will corrupt the memory!!! You notice it by seeing that icons and folder icons are missing! Later, the program might even crash! (Verified with 1.7.0.12, verified with Visual Studio and OpenWatcom) Application Verifier does not report anything bad. |
| 15 | You can also corrupt the memory by often applying filters and building and doing stuff. And at some point you get the error that preview cannot be shown because memory is out??? |
14 | You can also corrupt the memory by often applying filters and building and doing stuff. And at some point you get the error that preview cannot be shown because memory is out??? |
| 16 | Do we have a leak??? |
15 | Do we have a leak??? |
| 17 | Smashing Ctrl+F does not cause a leak |
16 | Smashing Ctrl+F does NOT cause a leak. |
| - | 17 | "Deleaker" tool only showed small leaks, nothing very big and no leaks with high hit-count! |
|
| 18 | 18 | ||
| 19 | Minor priority stuff or ideas |
19 | Minor priority stuff or ideas |
| 20 | ----------------------------- |
20 | ----------------------------- |
| 21 | 21 | ||
| - | 22 | * Should we completely remove all Apple code? It will make things much easier, and newer Apple ports need completely remake anyway. On the other hand, we lose a potential back port to ancient Mac. |
|
| - | 23 | ||
| 22 | * Right to the sliders you can enter numbers which are outside the range of 0..255 . Prevent that, please. |
24 | * Right to the sliders you can enter numbers which are outside the range of 0..255 . Prevent that, please. |
| 23 | 25 | ||
| 24 | * Win95 cannot detect a 64 bit obfuscated filter, because it cannot read the resources. Should there be a different mechanism for detecting an obfuscated filter? (e.g. a signature in PiPL which can be found using binary search?) |
26 | * Win95 cannot detect a 64 bit obfuscated filter, because it cannot read the resources. Should there be a different mechanism for detecting an obfuscated filter? (e.g. a signature in PiPL which can be found using binary search?) |
| 25 | 27 | ||
| 26 | * compat_win_resource.c (compatibility for Win9x resource generation): Cannot delete resources, see https://bugs.winehq.org/show_bug.cgi?id=52046 |
28 | * compat_win_resource.c (compatibility for Win9x resource generation): Cannot delete resources, see https://bugs.winehq.org/show_bug.cgi?id=52046 |
| Line 33... | Line 35... | ||
| 33 | 35 | ||
| 34 | * The filter `r*(y&1)` looks horrible when you zoom out! |
36 | * The filter `r*(y&1)` looks horrible when you zoom out! |
| 35 | 37 | ||
| 36 | * Memory leak: `strdup()` and `my_strdup()` need `free()` ! |
38 | * Memory leak: `strdup()` and `my_strdup()` need `free()` ! |
| 37 | 39 | ||
| 38 | * Why can't we edit *.rc files in Visual Studio? |
40 | * Why can't we edit *.rc files in Visual Studio? (As text) Visual Studio 2022 crashes if you try to edit the code of win_res.rc |
| 39 | 41 | ||
| 40 | * `host_preserves_parameters` (enabled with GIMP/PSPI) should somehow delete the temporary AFS file at each restart of GIMP. Otherwise, the user would always see the previous session when they re-open GIMP. |
42 | * `host_preserves_parameters` (enabled with GIMP/PSPI) should somehow delete the temporary AFS file at each restart of GIMP. Otherwise, the user would always see the previous session when they re-open GIMP. |
| 41 | 43 | ||
| 42 | * Create and evaluate more testcases, and either fix differences between FilterFactory and FilterFoundry, or document them in "Filter Factory Compatibility.md" |
44 | * Create and evaluate more testcases, and either fix differences between FilterFactory and FilterFoundry, or document them in "Filter Factory Compatibility.md" |
| 43 | 45 | ||
| 44 | * Should an expression like "----r" be forbidden? (Multiple negate signs) On the other hand, FilterFactory didn't forbit them either. |
46 | * Should an expression like "----r" be forbidden? (Multiple negate signs) On the other hand, FilterFactory didn't forbit them either. |
| 45 | 47 | ||
| 46 | * CMYK mode is possible (although a bit misleading to have r=c, g=m, b=y, a=k), but then it is impossible to control the alpha channel. |
48 | * CMYK mode is possible (although a bit misleading to have r=c, g=m, b=y, a=k), but then it is impossible to control the alpha channel. |
| 47 | 49 | ||
| 48 | * I have found following in the source code... Do we need to do something here? |
50 | * I have found the following in the source code... Do we need to do something here? |
| 49 | 51 | ||
| 50 | strcpy(gdata->parm.formula[i],expr[i] ? expr[i] : "bug! see builddlgitem"); |
52 | strcpy(gdata->parm.formula[i],expr[i] ? expr[i] : "bug! see builddlgitem"); |
| 51 | 53 | ||
| 52 | * Search for "TODO", "FIXME" and "Codereview" in the code |
54 | * Search for "TODO", "FIXME" and "Codereview" in the code |
| 53 | 55 | ||
| 54 | * There is no warning if a formula contains a number that exceeds 32 bits. |
56 | * There is no warning if a formula contains a number that exceeds 32 bits. |
| 55 | 57 | ||
| 56 | * Minor bug: Testcase testcases/rst_3.afs applied to a 1000x1000 canvas: When the preview is zoomed in to 29% or 59%, and the preview is panned, the bars change during panning. It does not look "smooth" like in 100%, 50%, or 25% zoom. The problem is that the offset of the preview area is always different, and if the zoom level is not a multiple of two, you will always "pick" other bars. |
58 | * Minor bug: Testcase testcases/rst_3.afs applied to a 1000x1000 canvas: When the preview is zoomed in to 29% or 59%, and the preview is panned, the bars change during panning. It does not look "smooth" like in 100%, 50%, or 25% zoom. The problem is that the offset of the preview area is always different, and if the zoom level is not a multiple of two, you will always "pick" other bars. |
| 57 | 59 | ||
| 58 | * Fast (double) click in [+]/[-] scroll buttons is not accepted as 2 clicks / zoom-requests |
- | |
| 59 | - | ||
| 60 | * Support more colors modes and 16bit. Why is Lab color not accepted, although doesSupportLABColor is set? |
60 | * Support more colors modes and 16bit. Why is Lab color not accepted, although doesSupportLABColor is set? |
| 61 | 61 | ||
| 62 | * Add Unicode support? (Does PiPL support Unicode at all?) |
62 | * Add Unicode support? (Does PiPL support Unicode at all?) |
| 63 | 63 | ||
| 64 | * Picture with 78x63 in grayscale mode: In preview on the left side there is a black bar |
64 | * Picture with 78x63 in grayscale mode: In preview on the left side there is a black bar |
| Line 72... | Line 72... | ||
| 72 | 72 | ||
| 73 | * Let PIPL have resource ID 16 instead of 16000, so that other apps might be able to recognize it as Filter Factory plugin? |
73 | * Let PIPL have resource ID 16 instead of 16000, so that other apps might be able to recognize it as Filter Factory plugin? |
| 74 | 74 | ||
| 75 | * Make Filter Foundry ready for translations? In Windows, put all strings in string lists (resources, `LoadStringA`), as well as in Mac resources. |
75 | * Make Filter Foundry ready for translations? In Windows, put all strings in string lists (resources, `LoadStringA`), as well as in Mac resources. |
| 76 | 76 | ||
| - | 77 | * Should the compiler flags in `funcs.h` as well as settings like `use_plugin_dll_sliders` be placed as resource (binary bits), so that the behavior can be changed if required? |
|
| - | 78 | ||
| 77 | * Should the compiler flags in `funcs.h` placed as resource (binary bits), so that the behavior can be changed if required? |
79 | * Make some parts of the code Unicode aware. Note that Photoshop itself (PIPL etc) doesn't seem to be Unicode aware, and PARM is also not Unicode aware. So the Title/Category/... stays ANSI! But we should allow that filters are loaded/saved from File Dialogs that can read/save Unicode folder names. |
| - | 80 | => Cancelled, because it is extremely heavy work! |
|
| 78 | 81 | ||
| 79 | 82 | ||
| 80 | Big ideas |
83 | Big ideas |
| 81 | --------- |
84 | --------- |
| 82 | 85 | ||