X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=w+6mSe0sPRdHJkRb8WaP5e7uG0P5O /X1DAo3L1rUTYY=; b=BoP4ht7c4VXj7kJFg70gyRjDMVw4DYMc4eltgO/e8AaGT ntKWqNEEtjayOkzGssOC0NVkSNM3KQtcbx0cJjAP5nfSZArpGGw7gsVC2IKMu2yt juJDLlTSp/3o/WFGLG8A1ueLBmzWk7E9QrYDCfGqCRviqdhSm6p/YbHswxuCbnWy bHOL8Lp2mZ0egijfNx8mjJZWgmAz07qq2akjO5oGY/yODrjVh8u3SKrVzR4oy7mT o4u7pDI7fvmZMjp2JUo0IzCZlUI5AkUU4vsVMQVIQMqrpE3wYT5ImOz7nL4GAote eMYJVnZmzr2wFN2MUzRJZKLW5CLjZpRgDfFA6o35w== X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=w+6mSe 0sPRdHJkRb8WaP5e7uG0P5O/X1DAo3L1rUTYY=; b=gmgoTFthuYiSwL2lIyI4lY ga6CK0gPb/6MbxEEdVSmcLZdJBukTEaTv17vMQd9Emcekuna3p67d2JuXc2rjnoK kw59OOQ97l7fnA0oR1D2Qb0YhCIl8gFYboO45LEmmufJ0kMfPkciEE2uS/S6dzSC OTJytoUT1m8om68Q0jeWzsC9d+i2CqCFYTrNum9Bj8h5T2lCNDEZ/EtNHPtx8CfI g09i8D92T7ntRHfpHHtn3mJ5MHgIwQDSfjDKUSqvPAW2AxXyHLAMFDsxqtqXxcDQ qoAoB1++qKIowD33G2QmtdAF+ljsZjBwvLQVSAXtT69PijiEbJMCynGDYUHchctA == X-ME-Proxy: X-ME-Sender: Message-Id: <1531286153.3131974.1436831304.36E05F01@webmail.messagingengine.com> From: "Edward Hennessy (ehennes+oss AT fastmail DOT com) [via geda-user AT delorie DOT com]" To: "vovka (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-957169fa Date: Tue, 10 Jul 2018 22:15:53 -0700 In-Reply-To: <20180709204944.GA921@debian.lokolhoz> Subject: Re: [geda-user] adventures using arrows (for documentation), or cross my lines References: <20180702125528 DOT D32CF81F76FE AT turkos DOT aspodata DOT se> <20180709204944 DOT GA921 AT debian DOT lokolhoz> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id w6B5G7Dr018700 Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Mon, Jul 9, 2018, at 1:49 PM, vovka (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > Hi Karl, > > On Mon, Jul 02, 2018 at 02:55:28PM +0200, karl AT aspodata DOT se wrote: >> a, nudge the arrow upwards >> b, make the "PATH" object have true line width of 0, at least for filled >>   polygons, i.e. patch gschem/lepton-schematic to make that happen. >> c, use same line width as horiz. line, and use round cap style, i.e. >>   patch gschem/lepton-schematic so that they honor the cap style entry >>   which is currently completely ignored and and an undocumented cap >>   style is used instead (called "miter" in postscript), see [3]. > > You can mitigate the issue a bit by using a smaller line > width. The smallest width is 1, since 0 means "default width" > which is really 10. E.g. use the following path definition line: > > H 3 1 0 0 -1 -1 1 -1 -1 -1 -1 -1 4 There is an issue with a line width of 0. Some backends interpret it as the the thinnest line they can represent. It would result in high-DPI printers making a very thin line. I’d like to suggest a fourth option: D, Add another line style “TYPE_NONE” where the line is not drawn. Ed