J
jim.klessig
Wed, Mar 7, 2018 5:41 PM
Well it is a grey/gray area.
Sent from my U.S. Cellular® Smartphone
null
Well it is a grey/gray area.
Sent from my U.S. Cellular® Smartphone
null
FV
Frank van der Hulst
Wed, Mar 7, 2018 6:13 PM
Are we talking about colo(u)r now?
On Thu, Mar 8, 2018 at 6:41 AM, jim.klessig jim.klessig@gmail.com wrote:
Are we talking about colo(u)r now?
On Thu, Mar 8, 2018 at 6:41 AM, jim.klessig <jim.klessig@gmail.com> wrote:
> Well it is a grey/gray area.
>
>
>
> Sent from my U.S. Cellular® Smartphone
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
>
G
Gadgetmind
Wed, Mar 7, 2018 6:30 PM
On 07/03/18 18:13, Frank van der Hulst wrote:
Are we talking about colo(u)r now?
That one is fixable in user space and I have done so. I keep musing on
getting my colour () module to also address "grey".
Center, sadly, isn't fixed as easily and it's a shame that (say)
cylinder can cope with many combinations or r, d, r1, r2, d1, d2 but not
centre as well as centre.
Oh, and the other one I'd love to fix is cylinder wanting "h" for height
and linear_extrude wanting "height". I have so many 100mm
linear_extrudes on my 1st pass.
On 07/03/18 18:13, Frank van der Hulst wrote:
> Are we talking about colo(u)r now?
That one *is* fixable in user space and I have done so. I keep musing on
getting my colour () module to also address "grey".
Center, sadly, isn't fixed as easily and it's a shame that (say)
cylinder can cope with many combinations or r, d, r1, r2, d1, d2 but not
centre as well as centre.
Oh, and the other one I'd love to fix is cylinder wanting "h" for height
and linear_extrude wanting "height". I have so many 100mm
linear_extrudes on my 1st pass.
N
NateTG
Wed, Mar 7, 2018 6:56 PM
Center, sadly, isn't fixed as easily and it's a shame that (say) cylinder
can cope with many combinations or r, d, r1, r2, d1, d2 but not centre as
well as centre.
> Center, sadly, isn't fixed as easily and it's a shame that (say) cylinder
> can cope with many combinations or r, d, r1, r2, d1, d2 but not centre as
> well as centre.
Seems like you could make a wrapper:
https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/User-Defined_Functions_and_Modules#Overwriting_built-in_modules
--
Sent from: http://forum.openscad.org/
RP
Ronaldo Persiano
Wed, Mar 7, 2018 10:07 PM
Not in Gadgetmind case:
module cylinder(r, h , centre) {
cylinder(r, h, center=centre) ;
}
would be a improper recursive module.
Em 7 de mar de 2018 15:57, "NateTG" nate-openscadforum@pedantic.org
escreveu:
Center, sadly, isn't fixed as easily and it's a shame that (say) cylinder
can cope with many combinations or r, d, r1, r2, d1, d2 but not centre as
well as centre.
Not in Gadgetmind case:
module cylinder(r, h , centre) {
cylinder(r, h, center=centre) ;
}
would be a improper recursive module.
Em 7 de mar de 2018 15:57, "NateTG" <nate-openscadforum@pedantic.org>
escreveu:
>
> > Center, sadly, isn't fixed as easily and it's a shame that (say) cylinder
> > can cope with many combinations or r, d, r1, r2, d1, d2 but not centre as
> > well as centre.
>
> Seems like you could make a wrapper:
>
> https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/User-
> Defined_Functions_and_Modules#Overwriting_built-in_modules
>
>
>
> --
> Sent from: http://forum.openscad.org/
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
NH
nop head
Wed, Mar 7, 2018 10:45 PM
Yes that is the problem when overriding built in modules you can't use the
original. With cylinder you have to construct it yourself and use
polyhedron. Not to mention handling r, r1, r2, d , d1, d2, etc.
On 7 March 2018 at 22:07, Ronaldo Persiano rcmpersiano@gmail.com wrote:
Not in Gadgetmind case:
module cylinder(r, h , centre) {
cylinder(r, h, center=centre) ;
}
would be a improper recursive module.
Em 7 de mar de 2018 15:57, "NateTG" nate-openscadforum@pedantic.org
escreveu:
Center, sadly, isn't fixed as easily and it's a shame that (say)
can cope with many combinations or r, d, r1, r2, d1, d2 but not centre
Yes that is the problem when overriding built in modules you can't use the
original. With cylinder you have to construct it yourself and use
polyhedron. Not to mention handling r, r1, r2, d , d1, d2, etc.
On 7 March 2018 at 22:07, Ronaldo Persiano <rcmpersiano@gmail.com> wrote:
> Not in Gadgetmind case:
>
> module cylinder(r, h , centre) {
> cylinder(r, h, center=centre) ;
> }
>
> would be a improper recursive module.
>
> Em 7 de mar de 2018 15:57, "NateTG" <nate-openscadforum@pedantic.org>
> escreveu:
>
>>
>> > Center, sadly, isn't fixed as easily and it's a shame that (say)
>> cylinder
>> > can cope with many combinations or r, d, r1, r2, d1, d2 but not centre
>> as
>> > well as centre.
>>
>> Seems like you could make a wrapper:
>>
>> https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/User-Defi
>> ned_Functions_and_Modules#Overwriting_built-in_modules
>>
>>
>>
>> --
>> Sent from: http://forum.openscad.org/
>>
>> _______________________________________________
>> OpenSCAD mailing list
>> Discuss@lists.openscad.org
>> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>>
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
>
R
runsun
Thu, Mar 8, 2018 12:33 AM
This will solve that problem :) :)
module cylindre(r, h , centre) {
cylinder(r, h, center=centre) ;
}
Ronaldo wrote
module cylinder(r, h , centre) {
cylinder(r, h, center=centre) ;
}
would be a improper recursive module.
$ Runsun Pan, PhD $ libs: scadx , doctest , faces ( git ), offline doc ( git ), runscad.py ( 2 , git ), editor of choice: CudaText ( OpenSCAD lexer ); $ Tips ; $ Snippets
--
Sent from: http://forum.openscad.org/
This will solve that problem :) :)
module *cylindre*(r, h , centre) {
cylinder(r, h, center=centre) ;
}
Ronaldo wrote
> module cylinder(r, h , centre) {
> cylinder(r, h, center=centre) ;
> }
>
> would be a improper recursive module.
-----
$ Runsun Pan, PhD $ libs: scadx , doctest , faces ( git ), offline doc ( git ), runscad.py ( 2 , git ), editor of choice: CudaText ( OpenSCAD lexer ); $ Tips ; $ Snippets
--
Sent from: http://forum.openscad.org/
M
MichaelAtOz
Thu, Mar 8, 2018 1:38 AM
Yes that is the problem when overriding built in modules you can't use the
original.
Would it be too hard to allow calling the original (or next scope level
down) module? Ala Lisp, Forth etc.
Admin - PM me if you need anything, or if I've done something stupid...
Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.
The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out!
Sent from: http://forum.openscad.org/
nophead wrote
> Yes that is the problem when overriding built in modules you can't use the
> original.
Would it be too hard to allow calling the original (or next scope level
down) module? Ala Lisp, Forth etc.
-----
Admin - PM me if you need anything, or if I've done something stupid...
Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.
The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out!
--
Sent from: http://forum.openscad.org/
N
NateTG
Thu, Mar 8, 2018 4:35 AM
Yes that is the problem when overriding built in modules you can't use
the
original.
Would it be too hard to allow calling the original (or next scope level
down) module? Ala Lisp, Forth etc.
...
MichaelAtOz wrote
> nophead wrote
>> Yes that is the problem when overriding built in modules you can't use
>> the
>> original.
>
> Would it be too hard to allow calling the original (or next scope level
> down) module? Ala Lisp, Forth etc.
> ...
Can you do that with nested use<> ?
--
Sent from: http://forum.openscad.org/
M
MichaelAtOz
Thu, Mar 8, 2018 5:21 AM
Can you do that with nested use<> ?
Why yes you can smart Sir.
---==========
use <_originals.scad> // has _cube()
module cube(size=[1,1,1],centre=false)
_cube(size=size,center=centre);
color("red") cube(1, centre=true);
translate([2,0,0]) color("blue") _cube(1);
Admin - PM me if you need anything, or if I've done something stupid...
Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.
The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out!
Sent from: http://forum.openscad.org/
NateTG wrote
> Can you do that with nested use<> ?
Why yes you can smart Sir.
===========================================
use <_originals.scad> // has _cube()
module cube(size=[1,1,1],centre=false)
_cube(size=size,center=centre);
color("red") cube(1, centre=true);
translate([2,0,0]) color("blue") _cube(1);
-----
Admin - PM me if you need anything, or if I've done something stupid...
Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.
The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out!
--
Sent from: http://forum.openscad.org/