> AFAIK, If your plugin can run with no image (i.e. It creates an image)
> then it doesn't matter.
OK, that's what I thought.
Thanks a lot.
--
Alesh SlovakLinux Team -- AVASYS Corporation
alesh.slo...@avasys.jp http://avasys.jp
__
AFAIK, If your plugin can run with no image (i.e. It creates an image)
then it doesn't matter.
If it can also operate on an existing image, you will have to ensure
it either has the proper checks or conversions coded in.
-Rob A>
On 2/18/09, Alesh Slovak wrote:
>> I believe it is tied to the ima
> I believe it is tied to the image type in your plugin declaration.
> Instead of "RGB*" (or whatever) set it to "".
Thanks for the tip. But won't setting the image type to "" cause other
problems?
--
Alesh SlovakLinux Team -- AVASYS Corporation
alesh.slo...@avasys.jp
I believe it is tied to the image type in your plugin declaration.
Instead of "RGB*" (or whatever) set it to "".
The "problem" is that with no image, it doesn't have a image type and
so fails the check and is greyed out.
-Rob A>
> alesh.slo...@avasys.jp http://avasys.jp
>
>
Hi,
I am a developer working on scanning software which provides a Gimp
plugin interface. As of Gimp 2.6, our plugin is placed in the wrong
location in the menu, and is grayed out until the user creates or opens
a new document.
I have been unable to find any up to date documentation or anythin