Flexible Part Language Extension - Revision history

Steffen at 09:46, 23 February 2019

2019-02-23T09:46:28Z

← Older revision		Revision as of 09:46, 23 February 2019
Line 455:		Line 455:
	For example imagine having a spring of length 100 using 4 section metas. If one of those sections uses a proportion of 2 and the other three use 1 the resulting section lengths will be: 40 (2 5ths), 20 (1 5th), 20 and 20.		For example imagine having a spring of length 100 using 4 section metas. If one of those sections uses a proportion of 2 and the other three use 1 the resulting section lengths will be: 40 (2 5ths), 20 (1 5th), 20 and 20.
	\|}		\|}

			[[Category:LDraw Files Syntax]]

OrionP: /* Spring Content METAs */ Formatting

2018-11-30T19:03:28Z

Spring Content METAs: Formatting

Show changes

OrionP: /* Spring content META */

2018-11-30T18:17:18Z

Spring content META

← Older revision		Revision as of 18:17, 30 November 2018
Line 316:		Line 316:
	\|}		\|}

	=== Spring ~~content META~~ ===		=== Spring Content METAs ===

	Spring content metas are used to define parts which include a movable spring inside a dedicated subfile. Based upon a collection of 0 !~~LDCAD~~ SPRING_ lines ~~LDCad~~ will be able to generate many kinds of spring oriented parts for use in your models. In order to also view those models correctly in other LDraw viewer/editor software a generated meta can be used to add plain LDraw fallback code to the subfile.		Spring content metas are used to define parts which include a movable spring inside a dedicated subfile. Based upon a collection of 0 !SPRING_ lines a LDraw compliant editor will be able to generate many kinds of spring oriented parts for use in your models. In order to also view those models correctly in other LDraw viewer/editor software a generated meta can be used to add plain LDraw fallback code to the subfile.

	==== The ~~spring point~~ META ====		==== The SPRING_POINT META ====

	The spring point meta is used to define at most two points using different group settings. These are the points the generated spring will connect using one or more section metas.		The spring point meta is used to define at most two points using different group settings. These are the points the generated spring will connect using one or more section metas.
Line 328:		Line 328:
	Example		Example

	0 !~~LDCAD~~ SPRING_POINT [group=start] [posOri=0 24 0 1 0 0 0 1 0 0 0 1]		<code><nowiki>0 !SPRING_POINT [group=start] [posOri=0 24 0 1 0 0 0 1 0 0 0 1]</nowiki></code>

	Properties		Properties

OrionP: /* Path content METAs */ Formatting

2018-11-30T18:10:32Z

Path content METAs: Formatting

Show changes

OrionP: /* The path anchor META */

2018-11-30T17:45:29Z

The path anchor META

← Older revision		Revision as of 17:45, 30 November 2018
Line 126:		Line 126:
	\|}		\|}

	==== The ~~path anchor~~ META ====		==== The PATH_ANCHOR META ====

	The anchor meta is (optionally) used to force a custom center using the automatic path content groups. This might be needed for start and or end groups if the containing cap or path point isn't suitable or logically. There can only be one anchor meta per group type inside any path content subfile.		The anchor meta is (optionally) used to force a custom center using the automatic path content groups. This might be needed for start and or end groups if the containing cap or path point isn't suitable or logically. There can only be one anchor meta per group type inside any path content subfile.

OrionP: /* The path cap META */

2018-11-30T17:45:09Z

The path cap META

← Older revision		Revision as of 17:45, 30 November 2018
Line 80:		Line 80:
	\|}		\|}

	==== The ~~path cap~~ META ====		==== The PATH_CAP META ====

	The path cap meta is used to add static (sub)parts to a flexible part. This is usually reserved for the outer endings of the generate part e.g. the studs at both endings of a wire.		The path cap meta is used to add static (sub)parts to a flexible part. This is usually reserved for the outer endings of the generate part e.g. the studs at both endings of a wire.

OrionP: /* The PATH_POINT META */

2018-11-30T17:44:38Z

The PATH_POINT META

← Older revision		Revision as of 17:44, 30 November 2018
Line 36:		Line 36:
	\| Sets the point type, must be ether bezier or circle.		\| Sets the point type, must be ether bezier or circle.
	Bezier points are used to guide the path through the center of this point using two control points, one in front and one behind it using the y axis of the points coordinate system (given by posOri).		Bezier points are used to guide the path through the center of this point using two control points, one in front and one behind it using the y axis of the points coordinate system (given by posOri).

	Circle points are used to guide the path around the center of this point on a 2D plane using a custom radius.		Circle points are used to guide the path around the center of this point on a 2D plane using a custom radius.
	\|-		\|-

OrionP: /* Path content METAs */ Formatting

2018-11-29T23:15:46Z

Path content METAs: Formatting

← Older revision		Revision as of 23:15, 29 November 2018
Line 10:		Line 10:
	=== Path content METAs ===		=== Path content METAs ===

	Path content metas are used to define bendable parts inside a dedicated subfile. Based upon a collection of 0 !~~LDCAD~~ PATH_ lines ~~LDCad~~ will be able to generate many kinds of flexible parts for use in your models. In order to also view those models correctly in other LDraw viewer/editor software ~~a generated meta can be used to add~~ plain LDraw fallback code to the subfile.		Path content metas are used to define bendable parts inside a dedicated subfile. Based upon a collection of 0 !PATH_ lines the LDraw editor will be able to generate many kinds of flexible parts for use in your models. In order to also view those models correctly in other LDraw viewer/editor software that do not support these METAs, plain LDraw fallback code is encouraged to be added to the generated subfile.

	==== The ~~Path Point~~ META ====		==== The PATH_POINT META ====

	The path point meta is used to define a point the generated path must pass through in a certain way. If multiple point metas are present the path will follow the order of line placement.		The path point meta is used to define a point the generated path must pass through in a certain way. If multiple point metas are present the path will follow the order of line placement.
Line 20:		Line 20:
	'''Example'''		'''Example'''

	<code><nowiki>0 !~~LDCAD~~ PATH_POINT [type=bezier] [posOri=-110 0 0 1 0 0 0 1 0 0 0 1] [prevCPDist=25] [nextCPDist=25] [cirR=25] [cirDir=xyCW] [prevYRoll=0] [nextYRoll=0]</nowiki></code>		<code><nowiki>0 !PATH_POINT [type=bezier] [posOri=-110 0 0 1 0 0 0 1 0 0 0 1] [prevCPDist=25] [nextCPDist=25] [cirR=25] [cirDir=xyCW] [prevYRoll=0] [nextYRoll=0]</nowiki></code>

	'''Properties'''		'''Properties'''
Line 87:		Line 87:
	'''Example'''		'''Example'''

	<code><nowiki>0 !~~LDCAD~~ PATH_CAP [group=start] [color=16] [posOri=-170 8 0 1 0 0 0 1 0 0 0 1] [part=165.dat] [extraLen=0mm]</nowiki></code>		<code><nowiki>0 !PATH_CAP [group=start] [color=16] [posOri=-170 8 0 1 0 0 0 1 0 0 0 1] [part=165.dat] [extraLen=0mm]</nowiki></code>

	'''Properties'''		'''Properties'''
Line 100:		Line 100:
	\| enum		\| enum
	\|		\|
	\| Group is used to assign this cap to one of the ~~automatic LDCad~~ groups available for this flexible part. It must be set to one of the following:		\| Group is used to assign this cap to one of the groups available for this flexible part. It must be set to one of the following:
	* start: All things that make up the starting point of a flexible part. This is usually a cap and the first path point.		* start: All things that make up the starting point of a flexible part. This is usually a cap and the first path point.
	* end: All things that make up the end point of a flexible part. This is usually a cap and the last path point.		* end: All things that make up the end point of a flexible part. This is usually a cap and the last path point.
Line 131:		Line 131:
	Anchor metas must only be used in the header and optionally kept grouped together.		Anchor metas must only be used in the header and optionally kept grouped together.

	Example		'''Example'''

	0 !~~LDCAD~~ PATH_ANCHOR [group=start] [posOri=-110 24 0 1 0 0 0 1 0 0 0 1]		<code><nowiki>0 !PATH_ANCHOR [group=start] [posOri=-110 24 0 1 0 0 0 1 0 0 0 1]</nowiki></code>

	Properties		Properties

	Property Type Default Description		{\| class="wikitable"
	group enum		\|-
	Group is used to assign this anchor to one of the ~~automatic LDCad~~ groups available for this flexible part. It must be set to one of the following:		! Property
			! Type
	start: All things that make up the starting point of a flexible part. This is usually a cap and the first path point.		! Default
			! Description
	end: All things that make up the end point of a flexible part. This is usually a cap and the last path point.		\|-
			\| group
			\| enum
			\|
			\| Group is used to assign this anchor to one of the groups available for this flexible part. It must be set to one of the following:
			* start: All things that make up the starting point of a flexible part. This is usually a cap and the first path point.
			* end: All things that make up the end point of a flexible part. This is usually a cap and the last path point.
	It is not allowed to set group to something another anchor is already set to.		It is not allowed to set group to something another anchor is already set to.
			\|-
	posOri ldraw matrix Position and orientation of the anchor.		\| posOri
			\| ldraw matrix
			\|
			\| Position and orientation of the anchor.
			\|}

	==== The path skin META ====		==== The path skin META ====

OrionP: /* Specification */ Added note that this spec is unofficial

2018-11-29T23:03:30Z

Specification: Added note that this spec is unofficial

← Older revision		Revision as of 23:03, 29 November 2018
Line 5:		Line 5:

	'''Revision''': 1, XX-XXX-XXXX		'''Revision''': 1, XX-XXX-XXXX

			Author's Note: This is a unofficial specification, not yet ratified by the LSC

	=== Path content METAs ===		=== Path content METAs ===

OrionP: /* The path cap META */ Formatting

2018-11-29T22:59:05Z

The path cap META: Formatting

← Older revision		Revision as of 22:59, 29 November 2018
Line 89:		Line 89:
	'''Properties'''		'''Properties'''
	{\| class="wikitable"		{\| class="wikitable"
	Property Type Default Description		\|-
	group enum		! Property
	Group is used to assign this cap to one of the automatic LDCad groups available for this flexible part. It must be set to one of the following:		! Type
			! Default
	start: All things that make up the starting point of a flexible part. This is usually a cap and the first path point.		! Description
			\|-
	end: All things that make up the end point of a flexible part. This is usually a cap and the last path point.		\| group
			\| enum
	color ldrawColNr 16 Color to use given LDraw part with.		\|
	posOri ldraw matrix Position and orientation of the cap's part.		\| Group is used to assign this cap to one of the automatic LDCad groups available for this flexible part. It must be set to one of the following:
	part ldrawRef LDraw part to use as a cap.		* start: All things that make up the starting point of a flexible part. This is usually a cap and the first path point.
	extraLen unit 0mm Can be used to state the captions length, can be used to corrected the total path length when the caption parts include e.g. part of the flexible donor structure themselves.		* end: All things that make up the end point of a flexible part. This is usually a cap and the last path point.
			\|-
			\| color
			\| ldrawColNr
			\| 16
			\| Color to use given LDraw part with.
			\|-
			\| posOri
			\| ldraw matrix
			\|
			\| Position and orientation of the cap's part.
			\|-
			\| part
			\| ldrawRef
			\|
			\| LDraw part to use as a cap.
			\|-
			\| extraLen
			\| unit
			\| 0mm
			\| Can be used to state the captions length, can be used to corrected the total path length when the caption parts include e.g. part of the flexible donor structure themselves.
			\|}

	==== The path anchor META ====		==== The path anchor META ====