ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Gavin via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Gavin <gavinpublic@icloud.com>
Subject: [NTG-context] Re: Seeking advice for module that draws globes
Date: Sun, 17 Dec 2023 20:49:59 -0700	[thread overview]
Message-ID: <AE79DC8E-DAD9-49DA-82AF-BFF96A534829@icloud.com> (raw)
In-Reply-To: <09bcff56-2b9c-45ec-a285-4b621c73725d@freedom.nl>

[-- Attachment #1: Type: text/plain, Size: 484 bytes --]

Hi Hans,

Thanks for all the suggestions! I am going through them carefully.

> - in mp you can do this
> 
> vardef theglobe(expr lat, lon) =
>    for i = 1 upto lua.mp.makeglobe(lat, lon):
>        (lua.mp.getglobepath(i)) &&&&
>    endfor
>    cycle
> enddef ;

Does "&&&&" allow a disconnected path? I haven’t seen "&&&&" or a disconnected path before.

Also, we do have a strange artifact, at least when I run this code. There is a line running across Brazil:


[-- Attachment #2: luageoTest.png --]
[-- Type: image/png, Size: 9789 bytes --]

[-- Attachment #3: Type: text/plain, Size: 273 bytes --]



I only got the line for (23,0), not for other latitude and longitude. I’m not sure what caused that. The code for cutting and mending paths that cross the horizon is tricky. I’m not sure how it will interact with "&&&&" and “cycle" connecting everything.

Gavin

[-- Attachment #4: Type: text/plain, Size: 511 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2023-12-18 16:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-17 22:22 [NTG-context] " Gavin via ntg-context
2023-12-17 23:58 ` [NTG-context] " Hans Hagen via ntg-context
2023-12-18  7:12   ` Henning Hraban Ramm
2023-12-19 14:27     ` Gavin via ntg-context
2023-12-19 17:42       ` Henning Hraban Ramm
2023-12-18  0:55 ` Hans Hagen via ntg-context
2023-12-18  3:49   ` Gavin via ntg-context [this message]
2023-12-18 10:08     ` Hans Hagen via ntg-context
2023-12-18 10:12 ` Hans Hagen via ntg-context
2023-12-18 16:22   ` Gavin via ntg-context
2023-12-18 17:27     ` Hans Hagen via ntg-context

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AE79DC8E-DAD9-49DA-82AF-BFF96A534829@icloud.com \
    --to=ntg-context@ntg.nl \
    --cc=gavinpublic@icloud.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).