@soegaard2 I’m getting the following error when running your example in DrRacket 7.3:
. . do-super-curve: got: ((#(struct:pt 0.7880661134318665 –0.6186239064870838) #(struct:tension-and 1 1) #(struct:pt 0.999069616419709 –0.08472110347239137) #(struct:tension-and 1 1) #(struct:pt 0.9543112976041062 0.3085126975504061) #(struct:tension-and 1 1) #(struct:pt 0.765686954024065 0.6505941342125146) #(struct:tension-and 1 1) #(struct:pt 0.5099251322206195 0.8647946599729002) #(struct:tension-and 1 1) #(struct:pt 0.20301094605648506 0.9830845025569938) #(struct:tension-and 1 1) #(struct:pt –0.0655389668371329 0.999069616419709) #(struct:tension-and 1 1) #(struct:pt –0.34687697082092306 0.9383261837413908)))
Red arrow line from line 111 to line 115
I’ll check.
Did you try before or after my commit 3 minutes ago?
lol - that’s close, I don’t know. I’ll try again :slightly_smiling_face:
It works here, but is possible I forgot to commit a file.
just tried with the latest and same error
Okay, let’s see.
I just did raco pkg install metapict
right before trying it
If you open your local copy of that file, does it match the one on github?
Got a few errors when installing metapict, but they’re all the same and seem harmless: “Library/Racket/7.3/pkgs/metapict/metapict/scribblings/coordinates.scrbl:3:41: module: identifier already required for label”
Try killing the repl window and run it again.
Maybe the repl has an instance of the old metapict module.
I killed DrRacket and re-started it - same error
Hmm.
oh, when you said your recent commit - were you referring to the example or metapict? I’ve only installed metapict once - just now
I’m on a Mac 10.11.6 - I haven’t upgraded to Racket 7.4 yet
Using 7.3 here too.
Try replacing (require metapict) with (require "../metapict.rkt")
This makes sure we are getting the metapict, where the racket-logo file is.
And not some other version (I got confused by this the other day).
. ../../Applications/Racket v7.3/share/pkgs/gui-lib/mred/private/snipfile.rkt:324:2: open-input-file: cannot open module file module path: /Users/metapict.rkt path: /Users/metapict.rkt system error: no such file or directory; rktio_err=3 no package suggestions are available .
The racket logo file doesn’t yet exist i.e. I haven’t saved it.
Wait. Did you update all of metapict or just the logo file?
I’ve only installed metapict, and then I copied/pasted your example into DrRacket to try it out.
From github or through the package server?
copied/pasted from github
I installed metapict via raco pkg install, but I copied/pasted the logo example from github
Okay. I don’t think the package server knows I have updated on Github yet.
so when you referred to your commit of 3 minutes ago, I only grabbed the new example - did you change metapict code also? If so, how do I update the package?
Yes, I changed a lot !
Ah :slightly_smiling_face:
I just wanted to try an example, I tried @spdegabrielle’s example first, but it failed on blue-gradient, so I thought I’d try yours.
“The results will be available after the next index refresh, which is scheduled for Tuesday, August 20th, 2019 3:11:26pm (UTC)”
ok
You can clone the repo, if you don’t want to wait.
I don’t mind waiting - I didn’t realize it was being developed so actively.
Oh!
I am not sure whether I forgot to commit the logo, or whether I changed it now.
My bad - I forgot to commit the “path.rkt” file.
I have added user definable path operators.
I.e. a user can define “operators” to connect points like the tikz operators |- and -| which connects points with horizontal/vertical lines.
Sorry for the confusion.
I’m getting permissions - maybe tomorrow
Pushed the forgotten file to github.
Thanks. Sort of works now. I have a black background, so at first I couldn’t see the rendered logo until I selected it to get reverse highlighting
:slightly_smiling_face:
Maybe we can create a “racket-users” or other better name origination on github to make this repo, and other future things.
@spdegabrielle I give you permission to package https://github.com/samdphillips/pixel-fish into a standard fish package :slightly_smiling_face:
I can add an explicit LICENSE / add copyright notices as well to the repo if that makes it easier