There are currently 243 online users. »3 Member(s) | 234 Guest(s) Applebot, Baidu, Bing, Google, Internet Archive, Yandex, Brett McColl, Mark Kennedy, tom alphin
This is a proposal to add a new !DATA meta-command that can be used to embed texture data into model files (for use with unofficial parts in an OMR model). The proposed specification for the new meta-statement follows. Please discuss.
Purpose
This document describes the !DATA meta-statement, which contains a set of commands for embedding binary data into LDraw files.
New meta-statement token
!DATA
This is the main data-embedding meta-command.
Reuse of existing meta-statement token
!:
This will be used to specify a BASE-64 encoded data stream. This token was introduced with the !TEXMAP meta-statement, and will be reused here for three reasons: its reuse will not interfere with its use in !TEXMAP; it is useful for the same reasons that it was useful in !TEXMAP; and !DATA is only useful right now for embedding texture data for use with !TEXMAP, so the two meta-statements are related to each other.
This meta-statement allows for BASE-64 encoded data to be used inside a multi-part-dat (MPD) file. The decoded binary data replaces of the embedded MPD sub-file.
This meta-statement must come after the 0 FILE meta-statement signifying a sub-file in a multi-part-dat (MPD) file.
The FILE that the DATA belongs to must not contain any geometry.
The FILE must contain one and only one DATA section.
The FILE may contain header information.
All characters after 0 !: that are not valid BASE-64 characters must be ignored. (This is intended to allow white-space characters to be placed in the line, but still applies to all other characters that are not valid BASE-64 characters.)
Each 0 !: line except for the last must contain exactly 76 encoded characters.
The last 0 !: line must contain no more than 76 encoded characters.
I just updated the MLCad.ini file accordingly to the latest LDraw.org parts update 2019-02. The .ini file defines (among other things) the parts available in MLCad's, LEOCad's and Bricksmith's minifigure generator.
75060 - Slave I
OMR Compliant
Missing:
- Minifig patterns documented in the file
- 2 Minifig accessories documented in the file
- Stickers. Oh so many stickers...
Comments: The angles on the side hull plating gave me fits so they are very close best fit.
Missing: Minifig Head, Torso, Hips, and Leg patterns as documented in the file
[color=#333333][size=small][font=Tahoma, Verdana, Arial, sans-serif][color=#333333][size=small][font=Tahoma, Verdana, Arial, sans-serif]Comments: None[/font][/size][/color][/font][/size][/color]
I've been doing some experiments and Roland suggested I shared them in this forum.
I've done some icons and themes in the past for LDCad. They are usually flat design themes, from several colors, with clear monochromatic icons
But I also wanted to be able to change the color of the titlebar of LDCad window from white, in the example above, to match the color of the menubar. I asked Roland about it but unfortunately that option was not available through the regular configuration files. But his reply about objects and windows class put me in the right track! I research a little and found out Autohotkey, a scripting language for Windows.
And what started as a pure cosmetic change turned out into a little addon that creates 4 extra buttons on the menubar, some additional hotkeys and the possibility to toggle on/off completely the window titlebar.
Here is a brief technical explanation. Autohotkey script grabs LDcad class window and creates an overlay GUI, an extension of the menubar, at a certain position. It creates the extra buttons and show/hides them as necessary. Then registers the mouse clicks and position to change images, cursor and run actions. Pressing the new menubar button will maximize the window, remove titlebar and show additional window control buttons on the menubar (min, restore, close window). It will also register new hotkeys to enable/disable the titlebar, show/hide the menubar, reload script, etc. The autohotkey script is called by a new autorun.lua script also included. So once LDCad loads and finishes updating the PartBin, you'll see a CMD window flash briefly (due to limitations of the io.popen function in the lua script) and the new button will appear on the menubar. Feel free to open the autohotkey script and look around.
Features:
1. New Hotkeys
- CTRL+T to toggle titlebar
- F11 to toggle menubar (have to config LDCad hotkey show/hide menubar to F10)
- Left Double Click on menubar will maximize/restore window
8099 - Midi-Scale Imperial Star Destroyer
OMR Compliant
Missing: Nothing
Comments: The hull plate angles are as close as they can be but there is still a small amount of part overlap.
As we are in the progress of amending the Sticker Specifications, what do you think of adding this one:
recently, LEGO started to print numbers next to their stickers to easier identify them, it looks like common sense to include this number as a letter in the part number, i.e. 01 -> "a", etc.
If there are more than 26 stickers on a sheet, they should be numbered as 27 -> aa, 28 -> ab
WOuld it make sense to add this and is it compatible with the library, i.e. was there enough common sense in the past to number the stickers accordingly since they introduced this scheme?
![[Image: 3712.png]](https://www.ldraw.org/library/official/images/parts/3712.png)
![[Image: 3326a.png]](https://www.ldraw.org/library/official/images/parts/3326a.png)
![[Image: 3326b.png]](https://www.ldraw.org/library/official/images/parts/3326b.png)
![[Image: LEGO-Star-Wars-75252-Imperial-Star-Destr...24x538.jpg]](https://s3-us-west-2.amazonaws.com/media.brothers-brick.com/2019/09/LEGO-Star-Wars-75252-Imperial-Star-Destroyer-Review-66-1024x538.jpg)
![[Image: Blue-Theme.png]](https://i.ibb.co/8MkCK59/Blue-Theme.png)
![[Image: Dark-Theme.png]](https://i.ibb.co/Qk8NMMf/Dark-Theme.png)
