Hi Alan,
There are five other (besides hitting return) possible methods for
terminating the window. There are two window manager controls for
doing
it and the corresponding alt-F4 and the wxwidgets file button for
exit and
the corresponding alt-x. If I use any of those 5
On 2009-01-23 08:59-0800 Alan W. Irwin wrote:
I noticed that (wxwidgets segfaults everywhere unless you remove the build
tree and install tree [in my case since I am doing install-tree testing] and
start fresh for any change) on Debian testing. Such a symptom happens for
no other device that
Hi Alan,
I confirm on my Debian testing platform that for revision 9358
( TTFDIR=/usr/share/fonts/truetype ;
PLPLOT_FREETYPE_SANS_FONT=$TTFDIR/arphic/bkai00mp.ttf
PLPLOT_FREETYPE_SERIF_FONT=$TTFDIR/freefont/FreeSerif.ttf
PLPLOT_FREETYPE_MONO_FONT=$TTFDIR/ttf-devanagari-fonts/lohit_hi.ttf
[Alan wrote]:
when the master is in focus, I get a segfault. Again, this is consistent
with the idea that the wxwidgets device is confusing windows events
from the two separate streams. I assume the fix is to change some
variables
in the wxwidgets device code to be stored in a
Hi,
I'm not 100% sure, if this problem is due to these changes, but suddenly
smoothing with the freetype routines in the wxWidgets driver on Windows
doesn't work anymore. I get the following output:
*** PLPLOT WARNING ***
Insufficient colour slots available in CMAP0 to do text smoothing.
Hi Werner,
wxwidgets works fine for me on Linux using e.g.
./x24c -dev wxwidgets
but I don't think I am getting the freetype backend since the fonts all
work fine.
The message you are getting occurs when freetype is initialised. This is
before any text plotting occurs and so shouldn't be as a
Hi Andrew,
wxwidgets works fine for me on Linux using e.g.
./x24c -dev wxwidgets
but I don't think I am getting the freetype backend since the fonts
all
work fine.
If you don't have the AGG library installed, then you use the basic
backend here which by default uses it's own text
On 2009-01-20 16:52+0100 Werner Smekal wrote:
Ah, sorry. Actually I initialized smooth_text=-1 (although this should
be 1) in my last changes. My bad. But due this you found a bug in the
driver ;). Very well!
So, sorry for the noise, it works now again also on Windows.
Hi Werner:
I have a
On Fri, Jan 16, 2009 at 10:06:29PM -0800, Alan Irwin wrote:
On 2009-01-16 23:43- Andrew Ross wrote:
If it is any consolation I can confirm your report on my Ubuntu system.
Example 24 has not been updated since mid 2006 other than for a const
char * tidy-up. The cookbook in in the
I've pinned down the problem, but I'm not quite sure why the code is
written the way it is.
The problem arises in src/plfreetype.c in FT_PlotChar. There are two
different code paths depending on whether the pixel mode is mono (i.e.
no anti-aliasing) or not. However, the first path is also taken
On Mon, Jan 19, 2009 at 10:27:17PM +1000, Andrew Roach wrote:
I've pinned down the problem, but I'm not quite sure why the code is
written the way it is.
The problem arises in src/plfreetype.c in FT_PlotChar. There are two
different code paths depending on whether the pixel mode is mono
On 2009-01-19 10:08- Andrew Ross wrote:
The [example 24 smooth=1] problem arises in src/plfreetype.c in FT_PlotChar.
There are two
different code paths depending on whether the pixel mode is mono (i.e.
no anti-aliasing) or not. However, the first path is also taken if icol0
= 0, i.e.
If I recall correctly, running the exact directions buried in x24c.c used to
work fine for -dev png (and other plfreetype-related devices)
but that no longer seems to be the case.
(TTFDIR=/usr/share/fonts/truetype ;
PLPLOT_FREETYPE_SANS_FONT=$TTFDIR/arphic/bkai00mp.ttf
13 matches
Mail list logo
