TP
Terry Pinnell
Wed, Feb 9, 2022 12:49 PM
Probably an embarrassingly obvious answer, but..
When building a model, say a shaft for a spindle, suppose I start with
subtracting a smaller cylinder from another. Developing that, the code can
soon get quite messy. Differences of differences and the like. Is there a
simple way to name my model, say 'Shaft', and then use that name in all
further editing?
--
Terry
Probably an embarrassingly obvious answer, but..
When building a model, say a shaft for a spindle, suppose I start with
subtracting a smaller cylinder from another. Developing that, the code can
soon get quite messy. Differences of differences and the like. Is there a
simple way to name my model, say 'Shaft', and then use that name in all
further editing?
--
Terry
NH
nop head
Wed, Feb 9, 2022 12:53 PM
Yes, make it a module called shaft and use shaft().
On Wed, 9 Feb 2022 at 12:50, Terry Pinnell terrypingm@gmail.com wrote:
Probably an embarrassingly obvious answer, but..
When building a model, say a shaft for a spindle, suppose I start with
subtracting a smaller cylinder from another. Developing that, the code can
soon get quite messy. Differences of differences and the like. Is there a
simple way to name my model, say 'Shaft', and then use that name in all
further editing?
--
Terry
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
Yes, make it a module called shaft and use shaft().
On Wed, 9 Feb 2022 at 12:50, Terry Pinnell <terrypingm@gmail.com> wrote:
> Probably an embarrassingly obvious answer, but..
>
> When building a model, say a shaft for a spindle, suppose I start with
> subtracting a smaller cylinder from another. Developing that, the code can
> soon get quite messy. Differences of differences and the like. Is there a
> simple way to name my model, say 'Shaft', and then use that name in all
> further editing?
>
> --
> Terry
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
T
terrypingm@gmail.com
Wed, Feb 9, 2022 1:52 PM
Thanks nop head. Although I understand the greater fexibility of modules, I naively had in mind something much simpler. While still editing my code, say that subtraction on my two cylinders is done. I’d like to bracket that code, place my cursor at the start and type something like ‘Define shaftxyz:’ So that any future use of the string ‘shaftxyz’ (apart from this specific statement) would effectively replace that code. No decisions about future use, no decision whether parameters needed and if so what to call them. Just like my abbreviation ‘=tp’ to type my full name and address.
--
Terry
On 9 Feb 2022, at 12:53, nop head nop.head@gmail.com wrote:
Yes, make it a module called shaft and use shaft().
On Wed, 9 Feb 2022 at 12:50, Terry Pinnell terrypingm@gmail.com wrote:
Probably an embarrassingly obvious answer, but..
When building a model, say a shaft for a spindle, suppose I start with subtracting a smaller cylinder from another. Developing that, the code can soon get quite messy. Differences of differences and the like. Is there a simple way to name my model, say 'Shaft', and then use that name in all further editing?
--
Terry
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
Thanks nop head. Although I understand the greater fexibility of modules, I naively had in mind something much simpler. While still editing my code, say that subtraction on my two cylinders is done. I’d like to bracket that code, place my cursor at the start and type something like ‘Define shaftxyz:’ So that any future use of the string ‘shaftxyz’ (apart from this specific statement) would effectively replace that code. No decisions about future use, no decision whether parameters needed and if so what to call them. Just like my abbreviation ‘=tp’ to type my full name and address.
--
Terry
> On 9 Feb 2022, at 12:53, nop head <nop.head@gmail.com> wrote:
>
>
> Yes, make it a module called shaft and use shaft().
>
>> On Wed, 9 Feb 2022 at 12:50, Terry Pinnell <terrypingm@gmail.com> wrote:
>> Probably an embarrassingly obvious answer, but..
>>
>> When building a model, say a shaft for a spindle, suppose I start with subtracting a smaller cylinder from another. Developing that, the code can soon get quite messy. Differences of differences and the like. Is there a simple way to name my model, say 'Shaft', and then use that name in all further editing?
>>
>> --
>> Terry
>> _______________________________________________
>> OpenSCAD mailing list
>> To unsubscribe send an email to discuss-leave@lists.openscad.org
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
RW
Rogier Wolff
Wed, Feb 9, 2022 1:54 PM
On Wed, Feb 09, 2022 at 12:53:01PM +0000, nop head wrote:
Yes, make it a module called shaft and use shaft().
Indeed.
Terry might need a bit more help to figure out the actual syntax:
module pipe (length, inner_diameter, wall_thickness)
{
rotate ([0,90,0])
difference () {
cylinder (d= inner_diameter + 2 * wall_thickness, h= length, center=true);
cylinder (d= inner_diameter + 0 * wall_thickness, h= length+2, center=true);
}
}
pipe (80, 10, 1);
rotate (90) pipe (60, 6, 1);
(For the record, I think of a shaft being solid. so I called it "pipe").
Roger.
Probably an embarrassingly obvious answer, but..
When building a model, say a shaft for a spindle, suppose I start with
subtracting a smaller cylinder from another. Developing that, the code can
soon get quite messy. Differences of differences and the like. Is there a
simple way to name my model, say 'Shaft', and then use that name in all
further editing?
--
Terry
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 **
** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 **
f equals m times a. When your f is steady, and your m is going down
your a is going up. -- Chris Hadfield about flying up the space shuttle.
On Wed, Feb 09, 2022 at 12:53:01PM +0000, nop head wrote:
> Yes, make it a module called shaft and use shaft().
Indeed.
Terry might need a bit more help to figure out the actual syntax:
module pipe (length, inner_diameter, wall_thickness)
{
rotate ([0,90,0])
difference () {
cylinder (d= inner_diameter + 2 * wall_thickness, h= length, center=true);
cylinder (d= inner_diameter + 0 * wall_thickness, h= length+2, center=true);
}
}
pipe (80, 10, 1);
rotate (90) pipe (60, 6, 1);
(For the record, I think of a shaft being solid. so I called it "pipe").
Roger.
> On Wed, 9 Feb 2022 at 12:50, Terry Pinnell <terrypingm@gmail.com> wrote:
>
> > Probably an embarrassingly obvious answer, but..
> >
> > When building a model, say a shaft for a spindle, suppose I start with
> > subtracting a smaller cylinder from another. Developing that, the code can
> > soon get quite messy. Differences of differences and the like. Is there a
> > simple way to name my model, say 'Shaft', and then use that name in all
> > further editing?
> >
> > --
> > Terry
> > _______________________________________________
> > OpenSCAD mailing list
> > To unsubscribe send an email to discuss-leave@lists.openscad.org
> >
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
--
** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 **
** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 **
f equals m times a. When your f is steady, and your m is going down
your a is going up. -- Chris Hadfield about flying up the space shuttle.
TP
Terry Pinnell
Wed, Feb 9, 2022 1:56 PM
Thanks nop head. Although I understand the greater fexibility of modules,
I naively had in mind something much simpler. While still editing my code,
say that subtraction on my two cylinders is done. I’d like to bracket that
code, place my cursor at the start and type something like ‘Define
shaftxyz:’ So that any future use of the string ‘shaftxyz’ (apart from this
specific statement) would effectively replace that code. No decisions about
future use, no decision whether parameters needed and if so what to call
them. Just like my abbreviation ‘=tp’ to type my full name and address.
--
Terry
On 9 Feb 2022, at 12:53, nop head nop.head@gmail.com wrote:
Yes, make it a module called shaft and use shaft().
On Wed, 9 Feb 2022 at 12:50, Terry Pinnell terrypingm@gmail.com wrote:
Probably an embarrassingly obvious answer, but..
When building a model, say a shaft for a spindle, suppose I start with
subtracting a smaller cylinder from another. Developing that, the code can
soon get quite messy. Differences of differences and the like. Is there a
simple way to name my model, say 'Shaft', and then use that name in all
further editing?
--
Terry
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
LargePrefPlaceholder-XKUz1MEJBwkOM
But of course without actually entering the code! just the abbreviation
'shaftxyz'
On Wed, 9 Feb 2022 at 13:52, terrypingm@gmail.com <terrypingm@gmail.com>
wrote:
> Thanks nop head. Although I understand the greater fexibility of modules,
> I naively had in mind something much simpler. While still editing my code,
> say that subtraction on my two cylinders is done. I’d like to bracket that
> code, place my cursor at the start and type something like ‘Define
> shaftxyz:’ So that any future use of the string ‘shaftxyz’ (apart from this
> specific statement) would effectively replace that code. No decisions about
> future use, no decision whether parameters needed and if so what to call
> them. Just like my abbreviation ‘=tp’ to type my full name and address.
>
> --
> Terry
>
> On 9 Feb 2022, at 12:53, nop head <nop.head@gmail.com> wrote:
>
>
> Yes, make it a module called shaft and use shaft().
>
> On Wed, 9 Feb 2022 at 12:50, Terry Pinnell <terrypingm@gmail.com> wrote:
>
>> Probably an embarrassingly obvious answer, but..
>>
>> When building a model, say a shaft for a spindle, suppose I start with
>> subtracting a smaller cylinder from another. Developing that, the code can
>> soon get quite messy. Differences of differences and the like. Is there a
>> simple way to name my model, say 'Shaft', and then use that name in all
>> further editing?
>>
>> --
>> Terry
>> _______________________________________________
>> OpenSCAD mailing list
>> To unsubscribe send an email to discuss-leave@lists.openscad.org
>>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
>
--
LargePrefPlaceholder-XKUz1MEJBwkOM
RW
Rogier Wolff
Wed, Feb 9, 2022 1:59 PM
Thanks nop head. Although I understand the greater fexibility of
modules, I naively had in mind something much simpler. While still
editing my code, say that subtraction on my two cylinders is
done. I’d like to bracket that code, place my cursor at the start
and type something like ‘Define shaftxyz:’ So that any future
use of the string ‘shaftxyz’ (apart from this specific
statement) would effectively replace that code. No decisions about
future use, no decision whether parameters needed and if so what to
call them. Just like my abbreviation ‘=tp’ to type my full name
and address.
You're still asking for a subset of what modules do.
module mypipe () pipe (80, 10, 1);
In computer languages, it is best to make things general enough and
then let users decide if they want to use all features or not.
Roger.
On 9 Feb 2022, at 12:53, nop head nop.head@gmail.com wrote:
Yes, make it a module called shaft and use shaft().
On Wed, 9 Feb 2022 at 12:50, Terry Pinnell terrypingm@gmail.com wrote:
Probably an embarrassingly obvious answer, but..
When building a model, say a shaft for a spindle, suppose I start with subtracting a smaller cylinder from another. Developing that, the code can soon get quite messy. Differences of differences and the like. Is there a simple way to name my model, say 'Shaft', and then use that name in all further editing?
--
Terry
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 **
** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 **
f equals m times a. When your f is steady, and your m is going down
your a is going up. -- Chris Hadfield about flying up the space shuttle.
On Wed, Feb 09, 2022 at 01:52:04PM +0000, terrypingm@gmail.com wrote:
> Thanks nop head. Although I understand the greater fexibility of
> modules, I naively had in mind something much simpler. While still
> editing my code, say that subtraction on my two cylinders is
> done. I’d like to bracket that code, place my cursor at the start
> and type something like ‘Define shaftxyz:’ So that any future
> use of the string ‘shaftxyz’ (apart from this specific
> statement) would effectively replace that code. No decisions about
> future use, no decision whether parameters needed and if so what to
> call them. Just like my abbreviation ‘=tp’ to type my full name
> and address.
You're still asking for a subset of what modules do.
module mypipe () pipe (80, 10, 1);
In computer languages, it is best to make things general enough and
then let users decide if they want to use all features or not.
Roger.
> --
> Terry
>
> > On 9 Feb 2022, at 12:53, nop head <nop.head@gmail.com> wrote:
> >
> >
> > Yes, make it a module called shaft and use shaft().
> >
> >> On Wed, 9 Feb 2022 at 12:50, Terry Pinnell <terrypingm@gmail.com> wrote:
> >> Probably an embarrassingly obvious answer, but..
> >>
> >> When building a model, say a shaft for a spindle, suppose I start with subtracting a smaller cylinder from another. Developing that, the code can soon get quite messy. Differences of differences and the like. Is there a simple way to name my model, say 'Shaft', and then use that name in all further editing?
> >>
> >> --
> >> Terry
> >> _______________________________________________
> >> OpenSCAD mailing list
> >> To unsubscribe send an email to discuss-leave@lists.openscad.org
> > _______________________________________________
> > OpenSCAD mailing list
> > To unsubscribe send an email to discuss-leave@lists.openscad.org
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
--
** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 **
** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 **
f equals m times a. When your f is steady, and your m is going down
your a is going up. -- Chris Hadfield about flying up the space shuttle.
RW
Rogier Wolff
Wed, Feb 9, 2022 2:00 PM
On Wed, Feb 09, 2022 at 01:56:16PM +0000, Terry Pinnell wrote:
But of course without actually entering the code! just the abbreviation
'shaftxyz'
That's what a library does.
include <poly.scad>
Roger.
--
** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 **
** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 **
f equals m times a. When your f is steady, and your m is going down
your a is going up. -- Chris Hadfield about flying up the space shuttle.
On Wed, Feb 09, 2022 at 01:56:16PM +0000, Terry Pinnell wrote:
> But of course without actually entering the code! just the abbreviation
> 'shaftxyz'
That's what a library does.
include <poly.scad>
Roger.
--
** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 **
** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 **
f equals m times a. When your f is steady, and your m is going down
your a is going up. -- Chris Hadfield about flying up the space shuttle.
TP
Terry Pinnell
Wed, Feb 9, 2022 2:02 PM
Agreed, Roger, 'pipe'!
See also my reply to nop head which passed in the ether before I saw yours.
I certainly do intend to make more use of modules. But for my pretty modest
designs I'd still like something simpler as explained.
I might try a second best solution of using my Macro Exoress Pro
application.
On Wed, 9 Feb 2022 at 13:54, Rogier Wolff R.E.Wolff@bitwizard.nl wrote:
On Wed, Feb 09, 2022 at 12:53:01PM +0000, nop head wrote:
Yes, make it a module called shaft and use shaft().
Indeed.
Terry might need a bit more help to figure out the actual syntax:
module pipe (length, inner_diameter, wall_thickness)
{
rotate ([0,90,0])
difference () {
cylinder (d= inner_diameter + 2 * wall_thickness, h= length,
center=true);
cylinder (d= inner_diameter + 0 * wall_thickness, h= length+2,
center=true);
}
}
pipe (80, 10, 1);
rotate (90) pipe (60, 6, 1);
(For the record, I think of a shaft being solid. so I called it "pipe").
Roger.
Probably an embarrassingly obvious answer, but..
When building a model, say a shaft for a spindle, suppose I start with
subtracting a smaller cylinder from another. Developing that, the code
soon get quite messy. Differences of differences and the like. Is
simple way to name my model, say 'Shaft', and then use that name in all
further editing?
--
Terry
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
LargePrefPlaceholder-XKUz1MEJBwkOM
Agreed, Roger, 'pipe'!
See also my reply to nop head which passed in the ether before I saw yours.
I certainly do intend to make more use of modules. But for my pretty modest
designs I'd still like something simpler as explained.
I might try a second best solution of using my Macro Exoress Pro
application.
On Wed, 9 Feb 2022 at 13:54, Rogier Wolff <R.E.Wolff@bitwizard.nl> wrote:
> On Wed, Feb 09, 2022 at 12:53:01PM +0000, nop head wrote:
> > Yes, make it a module called shaft and use shaft().
>
>
> Indeed.
> Terry might need a bit more help to figure out the actual syntax:
>
> module pipe (length, inner_diameter, wall_thickness)
> {
> rotate ([0,90,0])
> difference () {
> cylinder (d= inner_diameter + 2 * wall_thickness, h= length,
> center=true);
> cylinder (d= inner_diameter + 0 * wall_thickness, h= length+2,
> center=true);
> }
> }
>
> pipe (80, 10, 1);
> rotate (90) pipe (60, 6, 1);
>
>
> (For the record, I think of a shaft being solid. so I called it "pipe").
>
> Roger.
>
>
> > On Wed, 9 Feb 2022 at 12:50, Terry Pinnell <terrypingm@gmail.com> wrote:
> >
> > > Probably an embarrassingly obvious answer, but..
> > >
> > > When building a model, say a shaft for a spindle, suppose I start with
> > > subtracting a smaller cylinder from another. Developing that, the code
> can
> > > soon get quite messy. Differences of differences and the like. Is
> there a
> > > simple way to name my model, say 'Shaft', and then use that name in all
> > > further editing?
> > >
> > > --
> > > Terry
> > > _______________________________________________
> > > OpenSCAD mailing list
> > > To unsubscribe send an email to discuss-leave@lists.openscad.org
> > >
>
> > _______________________________________________
> > OpenSCAD mailing list
> > To unsubscribe send an email to discuss-leave@lists.openscad.org
>
>
> --
> ** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110
> **
> ** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 **
> f equals m times a. When your f is steady, and your m is going down
> your a is going up. -- Chris Hadfield about flying up the space shuttle.
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
--
LargePrefPlaceholder-XKUz1MEJBwkOM
TP
Terry Pinnell
Wed, Feb 9, 2022 2:05 PM
Thanks for both follow ups. On iPad but I'll get back to PC shortly and
experiment further with modules and includes.
On Wed, 9 Feb 2022 at 14:00, Rogier Wolff R.E.Wolff@bitwizard.nl wrote:
On Wed, Feb 09, 2022 at 01:56:16PM +0000, Terry Pinnell wrote:
But of course without actually entering the code! just the abbreviation
'shaftxyz'
That's what a library does.
include <poly.scad>
Roger.
--
** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110
**
** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 **
f equals m times a. When your f is steady, and your m is going down
your a is going up. -- Chris Hadfield about flying up the space shuttle.
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
LargePrefPlaceholder-XKUz1MEJBwkOM
Thanks for both follow ups. On iPad but I'll get back to PC shortly and
experiment further with modules and includes.
On Wed, 9 Feb 2022 at 14:00, Rogier Wolff <R.E.Wolff@bitwizard.nl> wrote:
> On Wed, Feb 09, 2022 at 01:56:16PM +0000, Terry Pinnell wrote:
> > But of course without actually entering the code! just the abbreviation
> > 'shaftxyz'
>
> That's what a library does.
>
> include <poly.scad>
>
> Roger.
>
> --
> ** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110
> **
> ** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 **
> f equals m times a. When your f is steady, and your m is going down
> your a is going up. -- Chris Hadfield about flying up the space shuttle.
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
--
LargePrefPlaceholder-XKUz1MEJBwkOM
FS
FF Systems
Wed, Feb 9, 2022 2:58 PM
Hmmmm... at the risk of being less than helpful, all the "pipes" in my
house are hollow...
On Wed, Feb 9, 2022 at 7:55 AM Rogier Wolff R.E.Wolff@bitwizard.nl wrote:
On Wed, Feb 09, 2022 at 12:53:01PM +0000, nop head wrote:
Yes, make it a module called shaft and use shaft().
Indeed.
Terry might need a bit more help to figure out the actual syntax:
module pipe (length, inner_diameter, wall_thickness)
{
rotate ([0,90,0])
difference () {
cylinder (d= inner_diameter + 2 * wall_thickness, h= length,
center=true);
cylinder (d= inner_diameter + 0 * wall_thickness, h= length+2,
center=true);
}
}
pipe (80, 10, 1);
rotate (90) pipe (60, 6, 1);
(For the record, I think of a shaft being solid. so I called it "pipe").
Roger.
Probably an embarrassingly obvious answer, but..
When building a model, say a shaft for a spindle, suppose I start with
subtracting a smaller cylinder from another. Developing that, the code
soon get quite messy. Differences of differences and the like. Is
simple way to name my model, say 'Shaft', and then use that name in all
further editing?
--
Terry
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
Hmmmm... at the risk of being less than helpful, all the "pipes" in my
house are hollow...
On Wed, Feb 9, 2022 at 7:55 AM Rogier Wolff <R.E.Wolff@bitwizard.nl> wrote:
> On Wed, Feb 09, 2022 at 12:53:01PM +0000, nop head wrote:
> > Yes, make it a module called shaft and use shaft().
>
>
> Indeed.
> Terry might need a bit more help to figure out the actual syntax:
>
> module pipe (length, inner_diameter, wall_thickness)
> {
> rotate ([0,90,0])
> difference () {
> cylinder (d= inner_diameter + 2 * wall_thickness, h= length,
> center=true);
> cylinder (d= inner_diameter + 0 * wall_thickness, h= length+2,
> center=true);
> }
> }
>
> pipe (80, 10, 1);
> rotate (90) pipe (60, 6, 1);
>
>
> (For the record, I think of a shaft being solid. so I called it "pipe").
>
> Roger.
>
>
> > On Wed, 9 Feb 2022 at 12:50, Terry Pinnell <terrypingm@gmail.com> wrote:
> >
> > > Probably an embarrassingly obvious answer, but..
> > >
> > > When building a model, say a shaft for a spindle, suppose I start with
> > > subtracting a smaller cylinder from another. Developing that, the code
> can
> > > soon get quite messy. Differences of differences and the like. Is
> there a
> > > simple way to name my model, say 'Shaft', and then use that name in all
> > > further editing?
> > >
> > > --
> > > Terry
> > > _______________________________________________
> > > OpenSCAD mailing list
> > > To unsubscribe send an email to discuss-leave@lists.openscad.org
> > >
>
> > _______________________________________________
> > OpenSCAD mailing list
> > To unsubscribe send an email to discuss-leave@lists.openscad.org
>
>
> --
> ** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110
> **
> ** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 **
> f equals m times a. When your f is steady, and your m is going down
> your a is going up. -- Chris Hadfield about flying up the space shuttle.
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>