Indeed for the wxWidgets driver it is bad too. When I first started
using PLplot I spent a lot of time wondering why my wxWidgets apps
kept crashing It turned out to be mostly due to plplot exit calls
when e.g. the Hershey font files weren't found.
Also for thread safety we are likely going to
Oh and floating point coordinate system was on there too.
Phil
On 21 May 2015 at 23:07, Phil Rosenberg p.d.rosenb...@gmail.com wrote:
Indeed for the wxWidgets driver it is bad too. When I first started
using PLplot I spent a lot of time wondering why my wxWidgets apps
kept crashing It turned
On Tue, May 12, 2015 at 02:51:12PM -0400, Hazen Babcock wrote:
This e-mail is to provide a summary of what we had discussed, please let
me know if I left anything out. I think we had a consensus that the
following change would be made as part of a possible version 6:
1. All API functions
Probably the biggest issue is the use of plsc.
Consider two threads which both set different streams then call
another plplot function function. Between the first thread's call to
set the stream and it's subsequent call to the other function it is
entirely likely that the second thread will
On 2015-03-24 14:59- Phil Rosenberg wrote:
Probably the biggest issue is the use of plsc.
Consider two threads which both set different streams then call
another plplot function function. Between the first thread's call to
set the stream and it's subsequent call to the other function it
On Mar 24, 2015, at 2:00 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
On 2015-03-24 14:59- Phil Rosenberg wrote:
Probably the biggest issue is the use of plsc.
Consider two threads which both set different streams then call
another plplot function function. Between the first
On 2015-03-24 14:55-0400 Jim Dishaw wrote:
One solution to the plsc issue is to use thread local storage. Both gcc and
msvc support it.
I had frankly never heard of that, but I have now looked it up, and it
does sound like it might work, but with some caveats.
The biggest of those in my
On 03/21/2015 05:51 PM, Jim Dishaw wrote:
On Mar 21, 2015, at 1:48 PM, Hazen Babcock hbabc...@mac.com wrote:
On 03/20/2015 05:35 PM, Jim Dishaw wrote:
In sum, the technical choice is between the alt approach which
requires already implemented code in the core with simpler code in the
On 2015-03-23 14:02-0400 Jim Dishaw wrote:
Last time I looked, achieving thread safety at a plot stream level
should be achievable with modest effort (eliminating globals and
static arrays). Achieving thread safety within a plot steam is more
challenging and would require a fair number of mutex
On 2015-03-23 17:56- Phil Rosenberg wrote:
i) Fontconfig is nearly impossible to build on native Windows. We have
had these discussions before. GIMP does appear to use it, but they
have no doubt had considerably more development person-hours than us
to work out how on earth to get it to
Hi Hazen
This seems like a good plan to me.
I agree with most things. To me the core role of plplot is to take
plot instructions and convert them to drawing instructions for
whichever device we are rendering to.
I have found rewriting the wxWidgets driver challenging as there are a
lot of things
I should check further up my unread mail before I reply. At least we
are in agreement :-)
On 21 March 2015 at 09:41, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
On 2015-03-20 08:46-0400 Hazen Babcock wrote:
Hello,
Since we are considering a number of changes, such as fixing error
I am slightly late to the show here, but I have fought with all three
text implimentations for the different wxWidgets backends and have
some thoughts.
i) Fontconfig is nearly impossible to build on native Windows. We have
had these discussions before. GIMP does appear to use it, but they
have no
On Mar 21, 2015, at 1:48 PM, Hazen Babcock hbabc...@mac.com wrote:
On 03/20/2015 05:35 PM, Jim Dishaw wrote:
In sum, the technical choice is between the alt approach which
requires already implemented code in the core with simpler code in the
unicode-aware drivers and the original
Hello,
Since we are considering a number of changes, such as fixing error
handling, that would break backwards compatibility anyway I propose that
we think a bit about all the other things that we might like to change,
perhaps bringing us to version 6 of PLplot. So, my proposals in no
On 2015-03-20 08:46-0400 Hazen Babcock wrote:
5. Use a library (Freetype?) for rendering text instead of delegating
this to the driver? The driver would instead be responsible for the
display of the resulting bitmaps. This would finally solve the problem
of the text looking slightly different
On 03/20/2015 03:58 PM, Alan W. Irwin wrote:
On 2015-03-20 14:31-0400 Jim Dishaw wrote:
On Mar 20, 2015, at 2:09 PM, Alan W. Irwin
ir...@beluga.phys.uvic.ca wrote:
On 2015-03-20 08:46-0400 Hazen Babcock wrote:
5. Use a library (Freetype?) for rendering text instead of delegating
this to
On Mar 20, 2015, at 3:58 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
On 2015-03-20 14:31-0400 Jim Dishaw wrote:
On Mar 20, 2015, at 2:09 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca
wrote:
On 2015-03-20 08:46-0400 Hazen Babcock wrote:
5. Use a library (Freetype?) for
18 matches
Mail list logo
