I already saw all those calls, I think I see how to modify my design to
make it work. Thanks for the help! I am going to do some hacking and get
another commit together.
Thanks,
wt
On Sat, Sep 7, 2013 at 5:07 AM, Joao S. O. Bueno wrote:
> On 7 September 2013 03:20, Warren Turkal wrote:
> > On
I thought that the palette loader code that is currently there created a
palette before putting it in the UI. However, upon closer inspection, each
of the loaders appear to create a palette based on the filename being
imported, then the common code in gimp renames the object. Given that the
current
On 7 September 2013 04:18, Warren Turkal wrote:
> I haven't found any way to make that interface work for what I am doing.
> Basically, I need to be able to return a palette object, but not one in the
> UI yet. That palette object can then be loaded by the existing gimp code
> into a new palette i
On 7 September 2013 03:20, Warren Turkal wrote:
> On Fri, Sep 6, 2013 at 11:20 AM, Joao S. O. Bueno
> wrote:
>>
> From the above comment, I assume that what I want to do will be hard. Any
> pointers on what would need to change to make it more useful? I'd be happy
> to try to do some of the work
On Fri, Sep 6, 2013 at 1:16 PM, Joao S. O. Bueno wrote:
> Besides - you have to check what makes more sense - I't think Palette
> exporting/importing plug-ins have to be on the Palletes context menu
>
> My basic design is going to be as follows:
>
>- Add a procedure to register a palette loa
