Subversion Repositories filter_foundry

Rev

Rev 442 | Rev 445 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed

Rev 442 Rev 444
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
* Test UNICODE very intense.
8
(None)
9
 
-
 
10
* Non-Windows source files: Don't use TCHAR. Instead typedef a type we can use independently of the WinAPI library!
9
 
11
 
10
 
12
 
11
Known bugs
13
Known bugs
12
----------
14
----------
13
 
15
 
Line 34... Line 36...
34
 
36
 
35
* 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?
37
* 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?
36
 
38
 
37
* The filter `r*(y&1)` looks horrible when you zoom out!
39
* The filter `r*(y&1)` looks horrible when you zoom out!
38
 
40
 
39
* Memory leak: `strdup()` and `my_strdup()` need `free()` !
41
* Verify if there are memory leaks: `strdup()` and `my_strdup()` need `free()` !
40
 
42
 
41
* 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
43
* 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
42
 
44
 
43
* `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.
45
* `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.
44
 
46
 
Line 58... Line 60...
58
 
60
 
59
* 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.
61
* 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.
60
 
62
 
61
* Support more colors modes and 16bit. Why is Lab color not accepted, although doesSupportLABColor is set?
63
* Support more colors modes and 16bit. Why is Lab color not accepted, although doesSupportLABColor is set?
62
 
64
 
63
* Add Unicode support? (Does PiPL support Unicode at all?)
-
 
64
 
-
 
65
* Picture with 78x63 in grayscale mode: In preview on the left side there is a black bar
65
* Picture with 78x63 in grayscale mode: In preview on the left side there is a black bar
66
 
66
 
67
* 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!
67
* 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!
68
 
68
 
69
* Check why the plugin crashes Premiere 5 (called in image filter mode; obviously not as transition filter)
69
* Check why the plugin crashes Premiere 5 (called in image filter mode; obviously not as transition filter)
Line 75... Line 75...
75
 
75
 
76
* Make Filter Foundry ready for translations? In Windows, put all strings in string lists (resources, `LoadStringA`), as well as in Mac resources.
76
* Make Filter Foundry ready for translations? In Windows, put all strings in string lists (resources, `LoadStringA`), as well as in Mac resources.
77
 
77
 
78
* 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
* 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?
79
 
79
 
80
* 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.
-
 
81
	=> Cancelled, because it is extremely heavy work!
-
 
82
 
-
 
83
 
80
 
84
Big ideas
81
Big ideas
85
---------
82
---------
86
 
83
 
87
* How about implementing the "Filters Unlimited" (FFX) language?
84
* How about implementing the "Filters Unlimited" (FFX) language?