## pyx-user — PyX user

You can subscribe to this list here.

2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 Jan (1) Feb (2) Mar (6) Apr (11) May Jun (2) Jul Aug (1) Sep (15) Oct (12) Nov (11) Dec (18) Jan (57) Feb (16) Mar (3) Apr (14) May (35) Jun (41) Jul (19) Aug (25) Sep (14) Oct (36) Nov (41) Dec (29) Jan (44) Feb (21) Mar (17) Apr (45) May (23) Jun (26) Jul (30) Aug (9) Sep (120) Oct (34) Nov (17) Dec (6) Jan (23) Feb (56) Mar (78) Apr (14) May (87) Jun (52) Jul (69) Aug (41) Sep (53) Oct (37) Nov (8) Dec (17) Jan (32) Feb (3) Mar (21) Apr (29) May (14) Jun (9) Jul (30) Aug (26) Sep (6) Oct (9) Nov (7) Dec (6) Jan (9) Feb (19) Mar (46) Apr (44) May (28) Jun (32) Jul (37) Aug (14) Sep (7) Oct (3) Nov (15) Dec (3) Jan Feb (6) Mar (7) Apr May (20) Jun (8) Jul (5) Aug (6) Sep Oct (45) Nov (8) Dec (20) Jan (3) Feb (1) Mar (12) Apr May (3) Jun (12) Jul (1) Aug (2) Sep (3) Oct (11) Nov (5) Dec (6) Jan (4) Feb Mar Apr (13) May (9) Jun (12) Jul (12) Aug (2) Sep (11) Oct (8) Nov (2) Dec (16) Jan (23) Feb Mar Apr (2) May Jun Jul Aug Sep (6) Oct (7) Nov Dec (3) Jan (1) Feb Mar Apr (2) May (7) Jun (6) Jul (2) Aug (12) Sep Oct (3) Nov Dec (3) Jan Feb Mar Apr (2) May Jun Jul Aug Sep Oct Nov (3) Dec Jan Feb (5) Mar (5) Apr (1) May (7) Jun (28) Jul (9) Aug Sep Oct (2) Nov (3) Dec (10) Jan (16) Feb (6) Mar Apr May (9) Jun (5) Jul (6) Aug Sep Oct Nov Dec
S M T W T F S

1

2

3

4

5

6
(2)
7
(5)
8

9
(3)
10
(3)
11
(2)
12
(9)
13
(5)
14
(6)
15
(2)
16

17
(2)
18
(6)
19
(1)
20
(4)
21
(2)
22
(3)
23

24

25

26

27
(1)
28

29
(1)
30

31

Showing 3 results of 3

 Re: [Pyx-user] Some arrow issues From: Magnus Lie Hetland - 2004-01-10 18:52:54 ```Joerg Lehmann : > > Hi Magnus, >=20 > On 09.01.04, Magnus Lie Hetland wrote: > > 1. Why do arrow points jut out beyond the end-point of the line? I > > know the reason is probably simply the linejoin behavior, but is > > there a motivation? If not, could the arrowheads be rewritten to > > avoid this? (For example, they could be rewritten using only fill, > > and not stroke, which would also fix the next issue...) >=20 > Maybe, you're right. But then we would lose the ability to have rounded= arrow > heads. On the other hand, we could reimplement this feature by construc= ting a > suitable arrow head path. Another nice feature, namely the ability to d= raw > arrows in two colors, however, cannot be reimplemented in this way. Indeed. An alternative is simply to move them back along the arrow so that the tip of the arrow is at the end-point. Another possibility is, I suppose, to allow this as an option -- for example setting the line style of the arrowhead separately, and setting it to None to avoid drawing it (or setting its width to zero or something). > > 2. Why are the contours of arrowheads dashed when the line is dashed? > > I can't think of any situations where this would be useful. >=20 > Indeed, this is not a very useful feature, but see my points above. Yes, but it isn't simply not (IMO) useful -- it is (IMO) inconvenient. It means that I cannot have dashed arrows without having very strange-looking arrowheads. Again, it would seem useful to be able to specify the styles of the arrowhead separately from the rest of the arrow. > > 3. Why must deco.earrow.normal be instantiated to be used, while > > (e.g.) color.rgb.red must not? (A glitch in CVS? Or am I missing > > something?) >=20 > This important point is really worth a separate mail, which I will > send tomorrow. Ah. OK. Looking forward to it. > > - Magnus, a happy PyX user :) >=20 > That's always nice to hear! :) Being able to write this sort of thing in Python is such a relief. I'm getting sort of used to MetaPost, but it is, of course, nowhere near as convenient (for a Python user, anyway). > J=F6rg --=20 Magnus Lie Hetland "The mind is not a vessel to be filled, http://hetland.org but a fire to be lighted." [Plutarch] ```
 Re: [Pyx-user] Some arrow issues From: Joerg Lehmann - 2004-01-10 18:17:29 ```Hi Magnus, On 09.01.04, Magnus Lie Hetland wrote: > 1. Why do arrow points jut out beyond the end-point of the line? I > know the reason is probably simply the linejoin behavior, but is > there a motivation? If not, could the arrowheads be rewritten to > avoid this? (For example, they could be rewritten using only fill, > and not stroke, which would also fix the next issue...) Maybe, you're right. But then we would lose the ability to have rounded arrow heads. On the other hand, we could reimplement this feature by constructing a suitable arrow head path. Another nice feature, namely the ability to draw arrows in two colors, however, cannot be reimplemented in this way. > 2. Why are the contours of arrowheads dashed when the line is dashed? > I can't think of any situations where this would be useful. Indeed, this is not a very useful feature, but see my points above. > 3. Why must deco.earrow.normal be instantiated to be used, while > (e.g.) color.rgb.red must not? (A glitch in CVS? Or am I missing > something?) This important point is really worth a separate mail, which I will send tomorrow. > - Magnus, a happy PyX user :) That's always nice to hear! Jörg ```
 Re: [Pyx-user] Problems on Windows From: Gary Pajer - 2004-01-10 16:28:43 ```Hello, Andre [...] > > C:\Python23\Lib\site-packages\pyx\examples>python hello.py > > > > Error: module writet1 (file C:/tex/texmf/fonts/type1/bluesky/cm/cmr10.pfb): > > unex > > pected end of file > > ==> Fatal error occurred, the output PDF file is not finished! > > > > helloworld.pdf is perfect. [...] > 1. Can you try to look into the helloworld.log from the pdftex run and > see, if there are path names in it? Just to make sure, that you are > using this same pfb font in pdftex and in PyX). I know, they really > should be the same, but lets check this first. > No additional info there. > 2. Can you try my new pfbtopfa converter to read the cmr10.pfb on your > system? Just fetch the latest CVS and step into the directory > pyx/t1strip (you may have to wait some hours until it becomes > available for anonymous checkout). Then try the following: > > andre@...:~/python/pyx/pyx/t1strip\$ python > Python 2.3 (#1, Sep 13 2003, 00:49:11) > [GCC 3.3 20030304 (Apple Computer, Inc. build 1495)] on darwin > Type "help", "copyright", "credits" or "license" for more information. > >>> from fullfont import fullfont > >>> fullfont(open("cmr10.pfa", "w"), "/sw/share/texmf/fonts/type1/bluesky/cm/cmr10.pfb") This works perfectly > > If this works, my guess is, that you're opening the pfb in ascii > instead of binary mode in writet1.c. How do we try to fix it? I took a quick look at stript1.c, but I don't speak c very well ... Did I mention that I'm using the Mingw compiler? (FWIW) -gary ```

Showing 3 results of 3