From: Magnus L. H. <ma...@he...> - 2004-01-12 14:36:17
|
Just to clear up a misunderstanding in one of my earlier posts (which might have been to pyx-devel -- I don't quite remember): I complained about the arrowheads being dashed, but that was because I thought I couldn't avoid it. Now I see that applying a separate style to the arrowhead is quite easy :) I still don't see whether or not it is possible to avoid stroking the arrowhead -- when I try to supply a deco.filled() to (e.g.) earrow(), I get a complaint about it not having a __neg__ method... It seems to believe it is an angle :] - Magnus (still trying to make arrows point to their end-points) -- Magnus Lie Hetland "The mind is not a vessel to be filled, http://hetland.org but a fire to be lighted." [Plutarch] |
From: Joerg L. <jo...@us...> - 2004-01-12 20:25:32
|
On 12.01.04, Magnus Lie Hetland wrote: > Just to clear up a misunderstanding in one of my earlier posts (which > might have been to pyx-devel -- I don't quite remember): I complained > about the arrowheads being dashed, but that was because I thought I > couldn't avoid it. Now I see that applying a separate style to the > arrowhead is quite easy :) Yes this is possible and was one of the goals of the decorator syntax. > I still don't see whether or not it is possible to avoid stroking the > arrowhead -- when I try to supply a deco.filled() to (e.g.) earrow(), > I get a complaint about it not having a __neg__ method... It seems to > believe it is an angle :] Ok, this is a little bit more tricky and in fact one of the points I tried to point out in my previous long mail. Arrows are a little bit more complicated in that they allow to set a variety of options. This is why you have to specify the attributes as follows (all variants are equivalent) - deco.earrow.normal([deco.filled(), color.rgb.red]) - deco.earrow.normal(attrs=[deco.filled(), color.rgb.red]) - deco.earrow(attrs=[deco.filled(), color.rgb.red) No longer possible is - deco.earrow.normal(deco.filled(), color.rgb.red) > - Magnus (still trying to make arrows point to their end-points) Try deco.earrow.normal(attrs=deco.stroked.clear) Jörg -- JOERG LEHMANN | PyX - High quality PostScript figures with Python & TeX jo...@lu... | Visit http://pyx.sourceforge.net/ |
From: Magnus L. H. <ma...@he...> - 2004-01-12 21:44:30
|
Joerg Lehmann <jo...@us...>: > [snip] > > - Magnus (still trying to make arrows point to their end-points) >=20 > Try deco.earrow.normal(attrs=3Ddeco.stroked.clear) Just checking: Here I could just use deco.earrow.normal(deco.stroked.clear) right? (Since I'm just using one argument...) Just to repeat myself a bit (see my previous email): It seems to me that the need to use the attrs keyword argument (as opposed to in the styles) is just as artificial as the difference between having to call decos and not styles... On another note -- I can't get the call above to work. I get the following error: TypeError: instance <pyx.attr.clearclass instance at 0x298800> not allowed > 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] |
From: Andre W. <wo...@us...> - 2004-01-13 06:56:21
|
Hi, On 12.01.04, Magnus Lie Hetland wrote: > > Try deco.earrow.normal(attrs=deco.stroked.clear) > > Just checking: Here I could just use > > deco.earrow.normal(deco.stroked.clear) > > right? (Since I'm just using one argument...) Well, right. This happens when attrs is the first argument and you have only one attribute. Usually, we allow for attrs=color.rgb.red instead enforcing the usage of attrs=[color.rgb.red], e.g. creating a list out of a single attribute automatically. May be, this is more confusing than it helps. > On another note -- I can't get the call above to work. I get the > following error: > > TypeError: instance <pyx.attr.clearclass instance at 0x298800> not > allowed I guess there are some type checks for the argument list being performed before the merging of the attributes took place. Those errors are likely to be in the code all around ... ;-( André -- by _ _ _ Dr. André Wobst / \ \ / ) wo...@us..., http://www.wobsta.de/ / _ \ \/\/ / PyX - High quality PostScript figures with Python & TeX (_/ \_)_/\_/ visit http://pyx.sourceforge.net/ |
From: Magnus L. H. <ma...@he...> - 2004-01-17 15:47:27
|
Andre Wobst <wo...@us...>: > [snip] > > On another note -- I can't get the call above to work. I get the > > following error: > >=20 > > TypeError: instance <pyx.attr.clearclass instance at 0x298800> not > > allowed >=20 > I guess there are some type checks for the argument list being > performed before the merging of the attributes took place. Those > errors are likely to be in the code all around ... ;-( But this is something that will be fixed, so that the code will eventually work? (That is, I will eventually be able to draw arrowheads with clear strokes, i.e., with fill only?) > Andr=E9 --=20 Magnus Lie Hetland "The mind is not a vessel to be filled, http://hetland.org but a fire to be lighted." [Plutarch] |
From: Joerg L. <jo...@us...> - 2004-01-17 17:14:16
|
On 17.01.04, Magnus Lie Hetland wrote: > But this is something that will be fixed, so that the code will > eventually work? (That is, I will eventually be able to draw > arrowheads with clear strokes, i.e., with fill only?) I just checked in the decorator rewrite as discussed on the list. You can now do the following: deco.earrow.Large([deco.stroked.clear]) Here, the attribute deco.stroked.clear removes any previous deco.stroked instance from the attribute list. Some other arrow examples are: deco.earrow.Large([deco.filled([color.rgb.red]), style.linewidth.normal]) deco.earrow.normal(constriction=0) deco.earrow.Large([style.linejoin.round]) and so on... Jörg |
From: Magnus L. H. <ma...@he...> - 2004-01-18 15:11:33
|
Joerg Lehmann <jo...@us...>: > > On 17.01.04, Magnus Lie Hetland wrote: > > But this is something that will be fixed, so that the code will > > eventually work? (That is, I will eventually be able to draw > > arrowheads with clear strokes, i.e., with fill only?) > > I just checked in the decorator rewrite as discussed on the list. Great! For some reason, anonymous CVS seems to be down, though (as it was yesterday). Developer CVS seems fine (although there is some scheduled downtime, which shouldn't, according to SF, affect the anonymous CVS). Does anyone know anything about this? Can't find any report on sf.net... -- Magnus Lie Hetland "The mind is not a vessel to be filled, http://hetland.org but a fire to be lighted." [Plutarch] |
From: Joerg L. <jo...@us...> - 2004-01-18 16:57:00
|
On 18.01.04, Magnus Lie Hetland wrote: > For some reason, anonymous CVS seems to be down, though (as it was > yesterday). Developer CVS seems fine (although there is some scheduled > downtime, which shouldn't, according to SF, affect the anonymous CVS). You're right, according to the SF site status page there should be no problems with anonymous CVS. At least, ViewCVS works. Jörg |
From: Magnus L. H. <ma...@he...> - 2004-01-20 14:56:24
|
Joerg Lehmann <jo...@us...>: > > On 17.01.04, Magnus Lie Hetland wrote: > > But this is something that will be fixed, so that the code will > > eventually work? (That is, I will eventually be able to draw > > arrowheads with clear strokes, i.e., with fill only?) > > I just checked in the decorator rewrite as discussed on the list. > You can now do the following: > > deco.earrow.Large([deco.stroked.clear]) I now managed to check out the updates from SourceForge (the anonymous server is finally up again...) but it doesn't seem to help. I still get the complaint that instance <pyx.attr.clearclass instance at 0x28c3f0> not allowed For example, the following produces this error: c.stroke(path.line(0, 0, 1, 0), deco.earrow.normal([deco.stroked.clear])) I also noticed a few other things that surprised me. For example, the following was *not* legal: c.stroke(path.line(0, 0, 1, 0), [deco.earrow.normal()]) # or [deco.earrow.normal] And neither was the following: c.stroke(path.line(0, 0, 1, 0), deco.earrow.normal) But the following *was*: c.stroke(path.line(0, 0, 1, 0), deco.earrow.normal()) I thought the requirement of instantiation was removed? And why am I not allowed to use a list of decorations/styles here? I thought perhaps that was even going to be *required*, but certainly not illegal? -- Magnus Lie Hetland "The mind is not a vessel to be filled, http://hetland.org but a fire to be lighted." [Plutarch] |
From: Joerg L. <jo...@us...> - 2004-01-20 15:52:51
|
On 20.01.04, Magnus Lie Hetland wrote: > I now managed to check out the updates from SourceForge (the anonymous > server is finally up again...) but it doesn't seem to help. I still > get the complaint that > > instance <pyx.attr.clearclass instance at 0x28c3f0> not allowed You may also want to try PyX 0.5, which was just released. > For example, the following produces this error: > > c.stroke(path.line(0, 0, 1, 0), > deco.earrow.normal([deco.stroked.clear])) Use c.stroke(path.line(0, 0, 1, 0), [deco.earrow.normal([deco.stroked.clear])]) > I also noticed a few other things that surprised me. For example, the > following was *not* legal: > > c.stroke(path.line(0, 0, 1, 0), > [deco.earrow.normal()]) # or [deco.earrow.normal] Is perfectly valid and works for me. > And neither was the following: > > c.stroke(path.line(0, 0, 1, 0), > deco.earrow.normal) > > But the following *was*: > > c.stroke(path.line(0, 0, 1, 0), > deco.earrow.normal()) Both are not valid and do not work. ;-) > I thought the requirement of instantiation was removed? And why am I > not allowed to use a list of decorations/styles here? I thought > perhaps that was even going to be *required*, but certainly not > illegal? The requirement of instantiation was removed and you have to specify lists now. Jörg |
From: Magnus L. H. <ma...@he...> - 2004-01-20 17:26:31
|
Joerg Lehmann <jo...@us...>: > [snip] > > You may also want to try PyX 0.5, which was just released. Sorry... Just a braindead mistake on my part. I thought I had the cvs checkout in my PYTHONPATH but I didn't -- and I hadn't run setup.py after updating from cvs, so I actually used an old version :) -- Magnus Lie Hetland "The mind is not a vessel to be filled, http://hetland.org but a fire to be lighted." [Plutarch] |