Rev 173 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
Rev 173 | Rev 178 | ||
---|---|---|---|
Line 71... | Line 71... | ||
71 | When the preview is zoomed in to 29% or 59%, and the preview is panned, the |
71 | When the preview is zoomed in to 29% or 59%, and the preview is panned, the |
72 | bars change during panning. It does not look "smooth" like in 100%, 50%, or 25% zoom. |
72 | bars change during panning. It does not look "smooth" like in 100%, 50%, or 25% zoom. |
73 | The problem is that the offset of the preview area is always different, and if the zoom |
73 | The problem is that the offset of the preview area is always different, and if the zoom |
74 | level is not a multiple of two, you will always "pick" other bars. |
74 | level is not a multiple of two, you will always "pick" other bars. |
75 | 75 | ||
76 | * In regards "Apple scripting" (AETE resource): |
76 | * In regards "Actions/Scripting": |
77 | - | ||
78 | a) Why do we include the AETE resource in Windows, and use fixaete() in the build-process, |
77 | fixaete(): Replace the cTl0...cTl7 descriptions with the names of the slider! |
79 | although there is no AppleScript support on Windows? |
- | |
80 | - | ||
81 | b) In a standalone filter, should the AETE dictionary only contain the controls which are used |
- | |
82 | by the built filter, and should these dictionary entries have the correct user-defined |
- | |
83 | control/slider name? |
- | |
84 | 78 | ||
85 | * Fast (double) click in [+]/[-] scroll buttons is not accepted as 2 clicks / zoom-requests |
79 | * Fast (double) click in [+]/[-] scroll buttons is not accepted as 2 clicks / zoom-requests |
86 | 80 | ||
87 | * Support more colors modes and 16bit. Why is Lab color not accepted, although doesSupportLABColor is set? |
81 | * Support more colors modes and 16bit. Why is Lab color not accepted, although doesSupportLABColor is set? |
88 | 82 |