matplotlib-devel Mailing List for matplotlib

On 9/24/07, Eric Firing <ef...@ha...> wrote:

> Maybe this is the result of the Mono people contacting Maxim as
> suggested by his 10/26 news post here:
> http://www.antigrain.com/news/index.html
>
> "# Current AGG users who are willing to continue using AGG under the old
> terms and conditions are encouraged to contact me and I will consider
> their requests."

This is certainly a possibility for us.  We are still on agg 2.3
actually, so I don't see this as a burning issue, but if we ever need
to upgrade from 2.4 or want upgrade for bugfixes, etc, I will email
Maxim and ask him about licensing options.

JDH

On Saturday 22 September 2007 08:06:56 pm Eike Welk wrote:
> Hi all!
>
> The QT backend (backend_qt.py) does not enter QT's event loop when
> multiple figures were created. It works fine with a single figure
> though.
>
> I have tested this with Suse Linux 10.2.
> matplotlib.__version__ : 0.90.1
>
> I have attached a little test program that illustrates the bug: When
> this program is run, two windows will appear for a split second, and
> the program finishes immediately.
> When lines 10 and 11 are commented out, the program works as expected:
> One window with a figure appears, and the program finishes when the
> window is closed.
>
> The attached patch fixes this bug. It is against the current HEAD in
> trunk.
>
> >From reading the code, the exact same fix should be done in the QT4
>
> backend.

Thank you for the report and for solving the problem. I applied your fix to 
backend_qt and backend_qt4 in svn-3879.

Darren

Bill Baxter wrote:
> 
> On 9/24/07, *Eric Firing* <ef...@ha... 
> <mailto:ef...@ha...>> wrote:
> 
>     John et al.,
> 
>     "Agg 2.5 will ship with a libsigc++ license that will allow us to treat
>     the code as MIT X11 unless the code is pulled out, allowing Antigrain to
>     be used internally for Silverlight and allowing them to license
>     Antigrain for other customers."
> 
>     I found the above quote on this page:
>     http://www.mono-project.com/Moonlight
> 
>     I don't understand it; does it mean that we, too, can continue using
>     future versions of Agg?
> 
> 
> Weird.  It reads to me more like they struck some sort of deal whereby 
> the code can be used as MIT X11 as long as it's an internal part of 
> Silverlight, but if removed from Silverlight, then it will revert to the 
> current GPL/commercial dual license.
> 
> --bb

Maybe this is the result of the Mono people contacting Maxim as 
suggested by his 10/26 news post here: 
http://www.antigrain.com/news/index.html

"# Current AGG users who are willing to continue using AGG under the old 
terms and conditions are encouraged to contact me and I will consider 
their requests."

Eric

On 9/24/07, Eric Firing <ef...@ha...> wrote:
>
> John et al.,
>
> "Agg 2.5 will ship with a libsigc++ license that will allow us to treat
> the code as MIT X11 unless the code is pulled out, allowing Antigrain to
> be used internally for Silverlight and allowing them to license
> Antigrain for other customers."
>
> I found the above quote on this page:
> http://www.mono-project.com/Moonlight
>
> I don't understand it; does it mean that we, too, can continue using
> future versions of Agg?


Weird.  It reads to me more like they struck some sort of deal whereby the
code can be used as MIT X11 as long as it's an internal part of Silverlight,
but if removed from Silverlight, then it will revert to the current
GPL/commercial dual license.

--bb

John et al.,

"Agg 2.5 will ship with a libsigc++ license that will allow us to treat 
the code as MIT X11 unless the code is pulled out, allowing Antigrain to 
be used internally for Silverlight and allowing them to license 
Antigrain for other customers."

I found the above quote on this page: http://www.mono-project.com/Moonlight

I don't understand it; does it mean that we, too, can continue using 
future versions of Agg?

Eric