Re: Fierce and scary geometry algorithm for ‘ParallelPath’

Newsgroups	comp.lang.postscript
Date	2019-06-19 15:04 -0700
References	<e7dba0a9-68e6-4dfe-90ba-6e9b00e7d3d3@googlegroups.com> <e0f28d19-18c4-4fb5-8825-597c56373326@googlegroups.com> <ec33e951-0c51-4fdd-b62e-4a65c99a9b52@googlegroups.com> <qa5h6c$dvh$1@dont-email.me>
Message-ID	<a837e718-be44-4ff9-bd4c-e06c86e2e80e@googlegroups.com> (permalink)
Subject	Re: Fierce and scary geometry algorithm for ‘ParallelPath’
From	jdaw1 <jdawiseman@gmail.com>

Show all headers | View raw

Sorry about delay in replying — original post was from wrong gmail account, and there‘s no way to stop it being my browser’s default. Sigh. 

On Sunday, 28 April 2019 21:33:08 UTC+1, luser droog  wrote:
> … we want something like a *morph* between
> the inner curve and the outer curve. 

No. The outer curve is merely a version of all the curves. Wha’s wanted is derived from the inner curve only. 

On Sunday, 28 April 2019 21:33:08 UTC+1, luser droog  wrote:
> I think I should read up on 'upath' which I think handles some of the
> gymnastics I've been doing with paths. Writing a function to take
> two paths can't really work with the currentpath as naively as I've
> grown used to doing.

Please report back. 

Sorry about delay in replying — original post was from wrong gmail account, and there‘s no way to stop it being my browser’s default. Sigh. 

On Sunday, 28 April 2019 21:33:08 UTC+1, luser droog  wrote:
> … we want something like a *morph* between
> the inner curve and the outer curve. 

No. The outer curve is merely a version of all the curves. Wha’s wanted is derived from the inner curve only. 

On Sunday, 28 April 2019 21:33:08 UTC+1, luser droog  wrote:
> I think I should read up on 'upath' which I think handles some of the
> gymnastics I've been doing with paths. Writing a function to take
> two paths can't really work with the currentpath as naively as I've
> grown used to doing.

Please report back. 

On Monday, 29 April 2019 01:40:45 UTC+1, Carlos  wrote:
> I think what he means is, if your last stroke is thin white, then *that* 
> stroke would have a clip edge, but it doesn't matter, because it's 
> invisible. The outermost black line would have overpaint on both sides. 
> Depending on the width of the outermost white stroke the glyph's contour 
> will appear more or less distorted though.

Agreed.

Back to comp.lang.postscript | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Fierce and scary geometry algorithm for ‘ParallelPath’ jdawiseman.bloomberg@gmail.com - 2019-04-17 13:37 -0700
  Re: Fierce and scary geometry algorithm for ‘ParallelPath’ edspikechapman@gmail.com - 2019-04-19 08:55 -0700
    Re: Fierce and scary geometry algorithm for ‘ParallelPath’ jdawiseman.bloomberg@gmail.com - 2019-04-20 02:44 -0700
      Re: Fierce and scary geometry algorithm for ‘ParallelPath’ Carlos <carlos@cvkm.cz> - 2019-04-29 02:41 +0200
        Re: Fierce and scary geometry algorithm for ‘ParallelPath’ jdaw1 <jdawiseman@gmail.com> - 2019-06-19 15:04 -0700
          Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-06-22 13:33 -0700
            Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-06-22 14:54 -0700
              Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-06-22 15:37 -0700
                Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-06-23 15:59 -0700
                Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-06-27 06:59 -0700
                Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-06-27 07:48 -0700
                Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-06-27 08:30 -0700
                Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-06-28 12:10 -0700
                Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-07-19 14:00 -0700
                Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-07-20 09:33 -0700
                Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-07-20 13:20 -0700
                Re: Fierce and scary geometry algorithm for ‘ParallelPath’ jdaw1 <jdawiseman@gmail.com> - 2021-03-14 10:25 -0700
  Re: Fierce and scary geometry algorithm for ‘ParallelPath’ jdawiseman.bloomberg@gmail.com - 2019-04-20 06:54 -0700
    Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-04-20 10:44 -0700
      Re: Fierce and scary geometry algorithm for ‘ParallelPath’ jdawiseman.bloomberg@gmail.com - 2019-04-20 11:01 -0700
        Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-04-20 11:33 -0700
          Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-04-20 11:50 -0700
            Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-04-20 13:01 -0700
              Re: Fierce and scary geometry algorithm for ‘ParallelPath’ jdawiseman.bloomberg@gmail.com - 2019-04-21 03:29 -0700
                Re: Fierce and scary geometry algorithm for ‘ParallelPath’ luser droog <luser.droog@gmail.com> - 2019-04-28 13:33 -0700

csiph-web