fling has quit [Remote host closed the connection]
gonkulator has joined #openscad
fling has joined #openscad
J24k54 has joined #openscad
J24k19 has quit [Ping timeout: 250 seconds]
kintel has joined #openscad
snaked has joined #openscad
hyperair has quit [Remote host closed the connection]
<gbruno>
[github] kintel synchronize pull request #4822 (Rename --render=cgal to --render=force to force-convert to the current backend-specific geometry) https://github.com/openscad/openscad/pull/4822
hyperair has quit [Read error: Connection reset by peer]
hyperair has joined #openscad
mmu_man has quit [Ping timeout: 264 seconds]
<JordanBrown>
DroidGee - in case you pick this up from the log, remember that if you started with OpenSCAD and generated a DXF, the DXF only has the resulting shape, not the OpenSCAD logic that yielded that shape. You might be able to recover a set of points suitable for use in a polygon() call, but nothing will know that those four points were originally a square centered around the origin.
snaked has quit [Read error: Connection reset by peer]
<Scopeuk>
we get that a surprisingly large amount although normally it is scad script rather than java
cart_ has joined #openscad
mmu_man has joined #openscad
mmu_man has quit [Ping timeout: 256 seconds]
pca006132 has joined #openscad
mmu_man has joined #openscad
cart_ has quit [Ping timeout: 255 seconds]
cart_ has joined #openscad
snaked has quit [Remote host closed the connection]
cart_ has quit [Ping timeout: 264 seconds]
cart_ has joined #openscad
pca006132 has quit [Remote host closed the connection]
pca006132 has joined #openscad
califax has joined #openscad
fling has joined #openscad
erectus has joined #openscad
TheAssassin has joined #openscad
teepee has joined #openscad
aiyion2 has joined #openscad
TheAssassin has quit [Remote host closed the connection]
TheAssassin has joined #openscad
califax has quit [Remote host closed the connection]
califax has joined #openscad
pca006132 has quit [Remote host closed the connection]
pca006132 has joined #openscad
J24k has joined #openscad
mmu_man has quit [Ping timeout: 264 seconds]
mmu_man has joined #openscad
otsakir has joined #openscad
erectus has quit [Ping timeout: 260 seconds]
bozo16 has joined #openscad
erectus has joined #openscad
erectus has quit [Remote host closed the connection]
erectus has joined #openscad
pca006132 has quit [Remote host closed the connection]
pca006132 has joined #openscad
otsakir has quit [Quit: Client closed]
erectus has quit [Ping timeout: 260 seconds]
b34r_dev has joined #openscad
adigitoleo has quit [Ping timeout: 258 seconds]
adigitoleo has joined #openscad
otsakir has joined #openscad
<b34r_dev>
I am getting "ERROR: Rendering cancelled by exception Vec out of range" using Manifold, but can't find any issue mentioning it. Is this issue worthy as is? The error log doesn't give any more detail than that.
<teepee>
b34r_dev: I think generally it's know, not sure about an actual issue. If you have a simple enough test case which produces this, it's probably still worth posting that as issue if that's with the latest build
<J24k>
Just need to change the links too .. i wonder if we could automate this as it happened in the past and you are also not the only one
<JordanBrown>
I see one of the edits introducing a {{anchor}} tag. It seems best to use that (with a simple tag) rather than assume that titles will stay constant.
omegatron has quit [Quit: Power is a curious thing. It can be contained, hidden, locked away, and yet it always breaks free.]
<J24k>
That would be the better way - i wasn't aware you could use anchor in wiki makeup
<JordanBrown>
I'm not surprised, but I didn't happen to know about it.
<JordanBrown>
But until we update the cheat sheets, we need the book to match the cheat sheets.
<JordanBrown>
I just fixed $fs et al.
<J24k>
the headlines automatically create anchors but making new anchors could solve this or better allow verbose headlines while having short links
<J24k>
Maybe putting the anchor below the heading - else if you move a section you will move the anchor from the section below
<JordanBrown>
Right, the reason that I think we should use {{anchor}} is that it allows us to pick stable names for the anchors, while having good words and style for the headings.
<JordanBrown>
As for before and after, I first tried putting the anchor after the heading, but when I do that Firefox (at least) jumps to that point, with the heading not visible.
<JordanBrown>
With the anchor just before the heading, FF jumps to a perfect place.
<J24k>
Hm can we add the anchor in the heading line?
<JordanBrown>
OK, here's the right answer: put the anchor *inside* the heading.
<J24k>
yes
<JordanBrown>
I just ran through several variations. Beginning and ending of the line don't work - it isn't recognized as a heading - but inside the heading works.
<J24k>
hopefully people will not change the anchor if changing the heading - cuz they likely will do that
<J24k>
So now we just need to add anchors for all cheatsheet topics - Ü
<JordanBrown>
at least if there is an explicit {{anchor}} it gives you a hint that something might depend on it.
<JordanBrown>
If we really want to do better, we might be able to add {{cheatsheet|key}} to make it more obvious.
<JordanBrown>
Yes, at some point somebody (not me right now :-) should check all of the links and maybe replace some.
<J24k>
I am glad you found a better option
<J24k>
cheatsheet|key would require to create a anchor template name .. can we define templates only for openscad in wikibooks?
<JordanBrown>
I think I created one a while back for examples, but didn't move over to it because there was something subtle that I couldn't figure out how to do.
<JordanBrown>
We would just make a {{cheatsheet}} that expands to {{anchor}}.
<JordanBrown>
But now I need to go pretend to do real work.
<J24k>
why did you put {{anchor|circleres}} .. you also could add multiple anchors |two|three .. i thought |$fn|$fs|$fa}} would be good so we can separate them in the cheatsheet