Rev 463 | Rev 474 | Go to most recent revision | Only display areas with differences | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
| Rev 463 | Rev 466 | ||
|---|---|---|---|
| 1 | 1 | ||
| 2 | Wishlist/ToDo-List |
2 | Wishlist/ToDo-List |
| 3 | ================== |
3 | ================== |
| 4 | 4 | ||
| 5 | ToDo for the next release |
5 | ToDo for the next release |
| 6 | ------------------------- |
6 | ------------------------- |
| 7 | 7 | ||
| 8 | (None) |
8 | (None) |
| 9 | 9 | ||
| 10 | 10 | ||
| 11 | Known problems |
11 | Known problems |
| 12 | -------------- |
12 | -------------- |
| 13 | 13 | ||
| 14 | * The preview will show the manipulation on the whole rectangle. It does not accurately exclude areas which aren't in a polygon selection area! |
14 | * The preview will show the manipulation on the whole rectangle. It does not accurately exclude areas which aren't in a polygon selection area! |
| 15 | see wishlist\bug_rectangle.png |
15 | see wishlist\bug_rectangle.png |
| 16 | 16 | ||
| 17 | 17 | ||
| 18 | Minor priority stuff or ideas |
18 | Minor priority stuff or ideas |
| 19 | ----------------------------- |
19 | ----------------------------- |
| 20 | 20 | ||
| 21 | * Can we still improve the speed? Filter Factory still seems to be faster! |
21 | * Can we still improve the speed? Filter Factory still seems to be faster! |
| 22 | 22 | ||
| 23 | * 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 | * 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. |
| 24 | 24 | ||
| 25 | * Right to the sliders you can enter numbers which are outside the range of 0..255 . Prevent that, please. |
25 | * Right to the sliders you can enter numbers which are outside the range of 0..255 . Prevent that, please. |
| 26 | 26 | ||
| 27 | * 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?) |
27 | * 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?) |
| 28 | 28 | ||
| 29 | * compat_win_resource.c (compatibility for Win9x resource generation): Cannot delete resources, see https://bugs.winehq.org/show_bug.cgi?id=52046 |
29 | * compat_win_resource.c (compatibility for Win9x resource generation): Cannot delete resources, see https://bugs.winehq.org/show_bug.cgi?id=52046 |
| 30 | 30 | ||
| 31 | * Add functionality to save to FFX (Filters Unlimited) filters. But we must use the "Make" dialog, because it contains title/category/author/copyright? |
31 | * Add functionality to save to FFX (Filters Unlimited) filters. But we must use the "Make" dialog, because it contains title/category/author/copyright? |
| 32 | 32 | ||
| 33 | * When a filter is created obfuscated and you click "Make" again, or if you loaded an old obfuscated filter (without protection), should then be the "obfuscate" checkbox be checked again? |
33 | * When a filter is created protected and you click "Make" again, should then be the "protection" checkbox be checked again? |
| 34 | 34 | ||
| 35 | * The filter `r*(y&1)` looks horrible when you zoom out! |
35 | * The filter `r*(y&1)` looks horrible when you zoom out! |
| 36 | 36 | ||
| 37 | * Verify if there are memory leaks: `strdup()` and `my_strdup()` need `free()` ! |
37 | * Verify if there are memory leaks: `strdup()` and `my_strdup()` need `free()` ! |
| 38 | 38 | ||
| 39 | * 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 | * 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 |
| 40 | 40 | ||
| 41 | * `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 | * `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 | 42 | ||
| 43 | * Create and evaluate more testcases, and either fix differences between FilterFactory and FilterFoundry, or document them in "Filter Factory Compatibility.md" |
43 | * Create and evaluate more testcases, and either fix differences between FilterFactory and FilterFoundry, or document them in "Filter Factory Compatibility.md" |
| 44 | 44 | ||
| 45 | * Should an expression like "----r" be forbidden? (Multiple negate signs) On the other hand, FilterFactory didn't forbit them either. |
45 | * Should an expression like "----r" be forbidden? (Multiple negate signs) On the other hand, FilterFactory didn't forbit them either. |
| 46 | 46 | ||
| 47 | * 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 | * 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 | 48 | ||
| 49 | * I have found the following in the source code... Do we need to do something here? |
49 | * I have found the following in the source code... Do we need to do something here? |
| 50 | 50 | ||
| 51 | strcpy(gdata->parm.formula[i],expr[i] ? expr[i] : "bug! see builddlgitem"); |
51 | strcpy(gdata->parm.formula[i],expr[i] ? expr[i] : "bug! see builddlgitem"); |
| 52 | 52 | ||
| 53 | * Search for "TODO", "FIXME" and "Codereview" in the code |
53 | * Search for "TODO", "FIXME" and "Codereview" in the code |
| 54 | 54 | ||
| 55 | * There is no warning if a formula contains a number that exceeds 32 bits. |
55 | * There is no warning if a formula contains a number that exceeds 32 bits. |
| 56 | 56 | ||
| 57 | * 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 | * 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 | 58 | ||
| 59 | * Support more colors modes and 16bit. Why is Lab color not accepted, although doesSupportLABColor is set? |
59 | * Support more colors modes and 16bit. Why is Lab color not accepted, although doesSupportLABColor is set? |
| 60 | 60 | ||
| 61 | * Picture with 78x63 in grayscale mode: In preview on the left side there is a black bar |
61 | * Picture with 78x63 in grayscale mode: In preview on the left side there is a black bar |
| 62 | 62 | ||
| 63 | * With the change in 1.7 in re "*preview evaluates whole picture if state changing functions rst,put,rnd are used*": Is there anything we can do to make it more performant when the user changes sliders? Especially with large pictures, the process becomes a bit laggy! => This feature was removed in 1.7.0.9, because it was extremely slow for some filters! |
63 | * With the change in 1.7 in re "*preview evaluates whole picture if state changing functions rst,put,rnd are used*": Is there anything we can do to make it more performant when the user changes sliders? Especially with large pictures, the process becomes a bit laggy! => This feature was removed in 1.7.0.9, because it was extremely slow for some filters! |
| 64 | 64 | ||
| 65 | * Check why the plugin crashes Premiere 5 (called in image filter mode; obviously not as transition filter) |
65 | * Check why the plugin crashes Premiere 5 (called in image filter mode; obviously not as transition filter) |
| 66 | 66 | ||
| 67 | * Cosmetics: Include a plugin-like-icon as icon #1 so that there would be a good icon in case some apps try to display an icon from the 8BF file? |
67 | * Cosmetics: Include a plugin-like-icon as icon #1 so that there would be a good icon in case some apps try to display an icon from the 8BF file? |
| 68 | (Attention: make_win.c deletes icon #1 because it thinks that it is the exclamation icon, so this needs to be changed then) |
68 | (Attention: make_win.c deletes icon #1 because it thinks that it is the exclamation icon, so this needs to be changed then) |
| 69 | 69 | ||
| 70 | * Let PIPL have resource ID 16 instead of 16000, so that other apps might be able to recognize it as Filter Factory plugin? |
70 | * Let PIPL have resource ID 16 instead of 16000, so that other apps might be able to recognize it as Filter Factory plugin? |
| 71 | 71 | ||
| 72 | * Make Filter Foundry ready for translations? In Windows, put all strings in string lists (resources, `LoadStringA`), as well as in Mac resources. |
72 | * Make Filter Foundry ready for translations? In Windows, put all strings in string lists (resources, `LoadStringA`), as well as in Mac resources. |
| 73 | 73 | ||
| 74 | * 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? |
74 | * 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? |
| 75 | 75 | ||
| 76 | 76 | ||
| 77 | Big ideas |
77 | Big ideas |
| 78 | --------- |
78 | --------- |
| 79 | 79 | ||
| 80 | * How about implementing the "Filters Unlimited" (FFX) language? |
80 | * How about implementing the "Filters Unlimited" (FFX) language? |
| 81 | 81 | ||
| 82 | 82 | ||
| 83 | Questions |
83 | Questions |
| 84 | --------- |
84 | --------- |
| 85 | 85 | ||
| 86 | * What is the exact purpose of the variable `needinput`? |
86 | * What is the exact purpose of the variable `needinput`? |
| 87 | It is set if we use rgbaiuvc or `cnv()` |
87 | It is set if we use rgbaiuvc or `cnv()` |
| 88 | But why isn't it set if we use `src()` or `rad()`. Is that OK??? |
88 | But why isn't it set if we use `src()` or `rad()`. Is that OK??? |
| 89 | 89 | ||
| 90 | * Is `D` is supposed to be a synonym `dmax` (then `D` should stay 512), |
90 | * Is `D` is supposed to be a synonym `dmax` (then `D` should stay 512), |
| 91 | or is `D` supposed to be `dmax-dmin` (then `D` should be 1024 and `dmin` should be 512)? |
91 | or is `D` supposed to be `dmax-dmin` (then `D` should be 1024 and `dmin` should be 512)? |
| 92 | 92 | ||
| 93 | * In regards length of the PIPL TLV, should it contain padding or not? Asked in https://community.adobe.com/t5/photoshop-ecosystem-discussions/question-about-pipl-tlv-encoding/m-p/12377822 |
93 | * In regards length of the PIPL TLV, should it contain padding or not? Asked in https://community.adobe.com/t5/photoshop-ecosystem-discussions/question-about-pipl-tlv-encoding/m-p/12377822 |
| 94 | - No: |
94 | - No: |
| 95 | * Photoshop does not accept if padding is not added to the length value |
95 | * Photoshop does not accept if padding is not added to the length value |
| 96 | * pluginsdk\photoshopapi\pica_sp\SPPiPL.h states: "Number of characters in the data array. Rounded to a multiple of 4." |
96 | * pluginsdk\photoshopapi\pica_sp\SPPiPL.h states: "Number of characters in the data array. Rounded to a multiple of 4." |
| 97 | * Official Adobe plugins, e.g. „3D Transform.8bf“ are rounding the length to a multiple of 4 (actually, rounding to the next possible multiple 4, so that padding is always guaranteed). |
97 | * Official Adobe plugins, e.g. „3D Transform.8bf“ are rounding the length to a multiple of 4 (actually, rounding to the next possible multiple 4, so that padding is always guaranteed). |
| 98 | * cnvtpipl.exe does the same |
98 | * cnvtpipl.exe does the same |
| 99 | - Yes: |
99 | - Yes: |
| 100 | * The 1997 PICA documentation (page 23) and 1996 "Cross-Application Plug-in Development Resource Guide" describe both: "Contains the length of the propertyData field. It does not include any padding bytes after propertyData to achieve four byte alignment. This field may be zero." |
100 | * The 1997 PICA documentation (page 23) and 1996 "Cross-Application Plug-in Development Resource Guide" describe both: "Contains the length of the propertyData field. It does not include any padding bytes after propertyData to achieve four byte alignment. This field may be zero." |
| 101 | * pluginsdk/documentation/html/struct_p_i_property.html writes the same thing |
101 | * pluginsdk/documentation/html/struct_p_i_property.html writes the same thing |
| 102 | 102 | ||
| 103 | Is there really a defect in these documentations? |
103 | Is there really a defect in these documentations? |
| 104 | 104 | ||
| 105 | 105 | ||
| 106 | Design/UI Tweaks |
106 | Design/UI Tweaks |
| 107 | ---------------- |
107 | ---------------- |
| 108 | 108 | ||
| 109 | * ctl(i) edit controls: Use a spinedit control so you can +1 and -1 with the mouse. Maybe `ControlTextWndProc` isn't neccessary anymore? |
109 | * ctl(i) edit controls: Use a spinedit control so you can +1 and -1 with the mouse. Maybe `ControlTextWndProc` isn't neccessary anymore? |
| 110 | 110 | ||
| 111 | * Should it be possible to zoom more than 100%? |
111 | * Should it be possible to zoom more than 100%? |
| 112 | 112 | ||
| 113 | * The vertical scrollbar should auto-hide when the expression formula is short. (Also for Mac). Unfortunately, this task is very hard in WIN32 API. |
113 | * The vertical scrollbar should auto-hide when the expression formula is short. (Also for Mac). Unfortunately, this task is very hard in WIN32 API. |
| 114 | 114 | ||
| 115 | * Should there be more (visual) space for expressions, like in Filter Factory? Also, Filter Factory had more visual space for slider names (e.g. required in Alf's Power Tools). |
115 | * Should there be more (visual) space for expressions, like in Filter Factory? Also, Filter Factory had more visual space for slider names (e.g. required in Alf's Power Tools). |
| 116 | 116 | ||
| 117 | * With some canvas formats, the initial zoom level is not "fully zoomed out" |
117 | * With some canvas formats, the initial zoom level is not "fully zoomed out" |
| 118 | 118 | ||
| 119 | * If you load an AFS file which has multi-line expressions, then the first expression (R) is scrolled down (because it has the focus) |
119 | * If you load an AFS file which has multi-line expressions, then the first expression (R) is scrolled down (because it has the focus) |
| 120 | 120 | ||
| 121 | 121 | ||
| 122 | Regarding Macintosh |
122 | Regarding Macintosh |
| 123 | ------------------- |
123 | ------------------- |
| 124 | 124 | ||
| 125 | * Please make a port to the latest Apple versions (and possible builds for older MacOS versions, too?) |
125 | * Please make a port to the latest Apple versions (and possible builds for older MacOS versions, too?) |
| 126 | 126 | ||
| 127 | * Unsure regarding AppleScript ! |
127 | * Unsure regarding AppleScript ! |
| 128 | https://developer.apple.com/library/archive/documentation/mac/pdf/Interapplication_Communication/AE_Term_Resources.pdf |
128 | https://developer.apple.com/library/archive/documentation/mac/pdf/Interapplication_Communication/AE_Term_Resources.pdf |
| 129 | 1. Do we need an 'auet' resource? |
129 | 1. Do we need an 'auet' resource? |
| 130 | 2. Does our implementation work with AppleScript? |
130 | 2. Does our implementation work with AppleScript? |
| 131 | 3. Must the human-language term REALLY be unique?! So only one plugin on the whole system may use the word "ctl(0)" or "red" or "size"??? Why do we have unique keys if the human language needs to be unique too?! (see "Important" section at page 8-14) |
131 | 3. Must the human-language term REALLY be unique?! So only one plugin on the whole system may use the word "ctl(0)" or "red" or "size"??? Why do we have unique keys if the human language needs to be unique too?! (see "Important" section at page 8-14) |
| 132 | 132 | ||
| 133 | * In ui_mac.c, there does not seem to be a limit for the expressions. So, is it possible to write an expression longer than 1023 bytes, which would lead to a crash? |
133 | * In ui_mac.c, there does not seem to be a limit for the expressions. So, is it possible to write an expression longer than 1023 bytes, which would lead to a crash? |
| 134 | 134 | ||
| 135 | * Macintosh: Please look at the (*) marked entries in CHANGELOG.md and verify the bugs/fixes and/or apply the changes on Mac. |
135 | * Macintosh: Please look at the (*) marked entries in CHANGELOG.md and verify the bugs/fixes and/or apply the changes on Mac. |
| 136 | 136 | ||
| 137 | * Macintosh: Is it possible to create a 64 bit version of FilterFoundry? Do we need to rewrite the UI code because the Carbon Framework is replaced by Cocoa! |
137 | * Macintosh: Is it possible to create a 64 bit version of FilterFoundry? Do we need to rewrite the UI code because the Carbon Framework is replaced by Cocoa! |
| 138 | 138 | ||
| 139 | * Some *.r files include "PiMI.r". Is this part of an old SDK or is a file missing? |
139 | * Some *.r files include "PiMI.r". Is this part of an old SDK or is a file missing? |
| 140 | 140 | ||
| 141 | * Support BigDocument (Add "ms32" PiPL, set `pb->bigDocumentData->PluginUsing32BitCoordinates` and use `pb->bigDocumentData->*`) |
141 | * Support BigDocument (Add "ms32" PiPL, set `pb->bigDocumentData->PluginUsing32BitCoordinates` and use `pb->bigDocumentData->*`) |
| 142 | 142 | ||
| 143 | * Correctly implement obfuscation version 6 (need to fix the binary executable code during build!) |
143 | * Correctly implement obfuscation version 6 (need to fix the binary executable code during build!) |
| 144 | 144 | ||
| 145 | 145 | ||
| 146 | Things to check/correct for other Telegraphics plugins (FIXED in FilterFoundry) |
146 | Things to check/correct for other Telegraphics plugins (FIXED in FilterFoundry) |
| 147 | ------------------------------------------------------ |
147 | ------------------------------------------------------ |
| 148 | 148 | ||
| 149 | * The lengths of the PIPL TLV structure must include everything, including string paddings, with 1 zero padding guaranteed. See annotations in "GIMP Incompatibilities.md". |
149 | * The lengths of the PIPL TLV structure must include everything, including string paddings, with 1 zero padding guaranteed. See annotations in "GIMP Incompatibilities.md". |
| 150 | 150 | ||
| 151 | * The language/country code in VarFileInfo must be a code that exists in StringFileInfo. The translation strings "04900000" don't fit together "080904B0". |
151 | * The language/country code in VarFileInfo must be a code that exists in StringFileInfo. The translation strings "04900000" don't fit together "080904B0". |
| 152 | 152 | ||
| 153 | * 64 Bit Windows builds |
153 | * 64 Bit Windows builds |
| 154 | 154 | ||
| 155 | * XP Manifests (+ activation contexts) |
155 | * XP Manifests (+ activation contexts) |
| 156 | 156 | ||
| 157 | * Fix AETE resources, make keys unique and remove scope in order to enable AppleScript |
157 | * Fix AETE resources, make keys unique and remove scope in order to enable AppleScript |
| 158 | 158 | ||
| 159 | * Support BigDocument (Add "ms32" PiPL, set `pb->bigDocumentData->PluginUsing32BitCoordinates` and use `pb->bigDocumentData->*`) |
159 | * Support BigDocument (Add "ms32" PiPL, set `pb->bigDocumentData->PluginUsing32BitCoordinates` and use `pb->bigDocumentData->*`) |
| 160 | 160 | ||
| 161 | * Place plugin dialogs on the correct screen |
161 | * Place plugin dialogs on the correct screen |