Almost all official and unofficial meta-commands that I've seen are written in all-caps (the exceptions being 'Name' and 'Author', presumably for historical reasons). I can't find anything which specifies that this is mandatory when defining new metas, so does anyone know:

- is it in fact mandatory, or just convention?
- should parsers be case-sensitive or case-insensitive when dealing with metas?


(As an aside, 'meta' is not an acronym, so should not be written as 'META' as it seems to be throughout the specs...)

I'm seeing the following:

/usr/www/users/peeron/ldraw/files/lib/smarty/Smarty.class.php:1593 - trigger_error
/usr/www/users/peeron/ldraw/files/lib/smarty/Smarty.class.php:1415 - _fetch_resource_info
/usr/www/users/peeron/ldraw/files/lib/smarty/Smarty.class.php:1261 - _compile_resource
/usr/www/users/peeron/ldraw/files/plugins/function.global_content.php:22 - fetch
/usr/www/users/peeron/ldraw/files/tmp/templates_c/67^%%70^707^707A8977%%content%3Acontent_en.php:114 - smarty_cms_function_global_content
/usr/www/users/peeron/ldraw/files/lib/smarty/Smarty.class.php:1263 - include
/usr/www/users/peeron/ldraw/files/plugins/function.content.php:121 - fetch
/usr/www/users/peeron/ldraw/files/tmp/templates_c/%%B2^B23^B2322195%%tpl_top%3A28.php:9 - smarty_cms_function_content
/usr/www/users/peeron/ldraw/files/lib/smarty/Smarty.class.php:1263 - include
/usr/www/users/peeron/ldraw/files/index.php:268 - fetch
string(63) "Smarty error: unable to read resource: "globalcontent:BadLinks""


It appears just after the list of meta-commands.

Please vote on the proposal below. Please modify the Subject to include your name and vote, in addition to giving your vote in the text.

Quote:This texture will remain in effect until:

• An END is given within the current file
  
• The file in which the START is located ends
  
• A STEP command is reached
  

The texture will remain active when processing an included file unless overridden within that file.

Quote:The END command stops using the current texture and restores the previous texture to current status. This means that nested commands with START will form a stack of textures and the END command will pop those textures. However, END cannot appear in a different file from START. If an END command is given in a sub file without a START having been given in that same file, the END stops the use of a texture specified in a calling file, then that texture will be restored to use when the sub file is exitedhas no effect.

I see a lot of high quality patterns on parts tracker made by Howard Lande and others. How do you make them, and how long it takes? Which programs do you use. I tried LDPatternCreator, but i didn't understand it.

Folks,

I would love to include more OMR files in the LDraw All-In-One-Installer and with MPDCenter published:

http://forums.ldraw.org/showthread.php?t...49#pid6249

you have a fine tool at hand to test for OMR compliance. Making some Technic models posted here fit for the AIOI would be a great starting point. Have a look in the models folder in the AIOI for reference if there are any doubts.

w.

Hello all,

I've released another maintenance update for the 1.1 version of LDCad.

This release is mainly to improve support on pre 2.0 OpenGL implementations in regards with shading related crashes during LDCad startup. See also the 'known issues' section on the website if the improvements don't work for your particular driver/VGA.

You'll find the new version at

www.melkert.net/LDCad


The 1.1 mascot screenshot for closure, enjoy:

This is a staple hair piece in recent sets and I really need it in leocad. It's used on Agent Chase and Fuse, Chase Mcain, several Harry Potter characters, at least one of the minifigures in the Minifigures series, and the list goes on.

-Eagleeyedan2

Since we had only 5 confirmed nominees, no election is necessary. Therefore, without further ado, the 2012/2013 LDraw Standards Committee (LSC) is (in alphabetical order):

Travis Cobbs
Chris Dee
Roland Melkert
Orion Pobursky
Allen Smith

Congratulation to the new LSC!

Willy Tschager
On behalf of the LDraw.org Steering Committee

As per http://www.ldraw.org/article/382/#Procedures:

Quote:Annual Summary

The members of the LSC will be responsible for publishing an annual summary to the community several weeks prior elections for the next year’s term. This summary shall outline the progress of the previous term, note all versions of the spec ratified during the term, and summarize the future goals and ideas of the current LSC members.

This post explains the small history line "BFC rationalisation" which appears
in the bunch of updated official files that Chris just has uploaded to the PT for me, thanks, Chris!

I had recently done a systematic syntax check of all currently official files.
Through this I discovered these files having some common glitches, which I ironed out.
They were:

(a) appearance of header elements throughout the file, mostly due to inlining relicts, e.g. "Name: xyz" or "BFC CERTIFY CCW"
(b) repeated BFC CERTIFY statements throughout the file (probably due to MLCad save operation)
© changing of winding from CW to CCW or vice versa inside the file (usually a result of inlining)
(d) other syntax errors