Please uninstall older versions of this software before installing a new version.
Your configuration won't be deleted if you have already version greater than 1.3.1 installed on your machine.
Change log:
New features:
You can use the sticker generator for rectangular sticker templates.
"Unificator.exe" is included in the post process.
The post process is customizable.
You can load/save the colour toolbar settings.
The 2D engine is improved and faster.
The colours from the colour replacer are sorted.
The superfast triangulation is improved.
You can show vertex information of primitive/group vertices by clicking on it in vertex mode.
A dynamic primitive list "Primitives.cfg" is stored in the application directory.
Fixed Bugs from 1.3.X:
The LPC-Unificator creates triangles with same points.
Primitive matrix manipulation enables "Cut", "Copy" and "Paste" when "Add Vertex" is enabled.
A primitive is movable in the vertex/triangle-mode.
The template editor does not read from the "\template" directory.
LPC crashes if you take a hex-colour from a primitive/group.
* Every time I launch LDPC I get a User Account Control request in Win 7 - "Do you want the following program to allow changes to this computer?". I get the request even if I launch the prog as Admin. LDPC is installed in C:\Program Files (x86)\LDraw Author Tools\LDPatternCreator
* Though I just File > Save(d) before File > Exit the prog I get a request if I wanna save 'cos there are unsaved changes!
Willy Tschager Wrote:* Every time I launch LDPC I get a User Account Control request in Win 7 - "Do you want the following program to allow changes to this computer?". I get the request even if I launch the prog as Admin.
The LPC is a .NET application, which require access to your local file system. The application has no certificate and as a result, Windows 7 have to show the request. You can disable the UAC warnings with your local administrator account, but you will never be notified by the OS when programs try to install software or make changes to your computer.
In a long term perspective, I am not going to buy a certificate for this program.
Willy Tschager Wrote:* Though I just File > Save(d) before File > Exit the prog I get a request if I wanna save 'cos there are unsaved changes!
I don't know which file access causes this (prob. cfg?), but you could probably avoid all nagging by installing the application in your "my documents" folder or some other none system location.
Just the vertices show up. Pretty useless. Hopefully there is a way to fix it. When I try to save the corrupt version in a new file I get the following error:
Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.
************** Ausnahmetext **************
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei LDPatternCreator.MainForm.SaveToolStripMenuItem_Click(Object sender, EventArgs e)
bei System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
bei System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
bei LDPatternCreator.MainForm.SaveAsToolStripMenuItem_Click(Object sender, EventArgs e)
bei System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
bei System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
bei System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
bei System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ToolStrip.WndProc(Message& m)
bei System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.
Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.
Many thx, Nils. Everything is back to normal. The only missing part was the x/y offset + scaling of the background pattern. I recovered it via notepad from an older version.
I'm sure one day (after your exams, for which I wish you the best) you're gonna tell us a little bit more of the Pattern Creator 1.3 Unicode File syntax and its column of numbers.
