On Wednesday, April 4, 2012, 15:01:34, Ragnar Brynjúlfsson wrote:
> Anyone know how to do this on windows.
The simple way is to run gimp with --verbose switch - that'll open a
console window.
--
< Jernej Simončič ><><><><>< http://eternallybored.org/ >
If you don't care where you are, you ain'
Thanks for the info guys.
Yes, I am already developing on Linux (I am a long time linux user, I
haven't touched Windows since win98).I'll start launching Gimp from the
terminal and watching for output there
On Apr 4, 2012 9:01 AM, "Ragnar Brynjúlfsson" wrote:
> I'm assuming Jon is working o
I'm assuming Jon is working on Windows. On Linux you can just start
gimp from a terminal and get all the output you need, but when I was
porting a plug-in I wrote to Windows, there was no info in the command
line, and I had to resort to printing stuff to the gimp error console.
Anyone know how to d
On 3 April 2012 08:01, Jon Decker wrote:
> Hello
>
> I have a lot of work into my first large plugin. One thing that really
> slows my progress is the lack of any kind of debugging or work flow. For
> example, if I make a syntax error, the plugin will just silently fail, or
> fail to appear in t
Hello
I have a lot of work into my first large plugin. One thing that really
slows my progress is the lack of any kind of debugging or work flow. For
example, if I make a syntax error, the plugin will just silently fail, or
fail to appear in the menu. I receive no erros or hints as to where the
