[LDPE] 1.8.83 Released (dark theme / swap XYZ / rare bugfix)

[Nils Schmidt]

Hey,

this new version adds colour themes to the editor (default/dark/light and the famous dracula theme).
And you can now swap the XYZ coordinates of a selection (globally and locally) via "Actions..."->"Swap X/Y/Z (for Selection)".
Finally, it fixes an old rare bug, which kept the text-editor as read-only until the file was saved (Thanks to Willy and Magnus for reporting the bug!).

This is the 100th release version from Github by the way...



As always, you can download LDPE from this page:

http://nilsschmidt1337.github.io/ldparteditor/

Changelog:

(3 new features and 1 bug fix)

With this release you will be able to...

• ...change colour themes via "Tools..."->"Options..."->"Customise Colours:"->"Theme" (e.g. to dark mode/dracula theme) to make the software easier on the eyes.
  
• ...use "Swap X/Y/Z (for Selection)".
  
• ...use "Set X/Y/Z (for Selection)" to set the manipulator position, too.
  

The following critical issue is fixed after more than 8 years:

1. Sometimes the text-editor remained read-only until the file was saved (e.g. after Edger2 runs).
   

The program was tested intensively with "real world" files.
However, something can go wrong in about 140.000 lines of code.

Installation on Windows:

1. Download and extract LDPartEditor_win32_x64.zip
   
2. Run LDPartEditor-1.8.83.msi
   
3. Start LDPartEditor from the start menu
   

Installation on Linux:

1. Download and extract LDPartEditor_linux_x64.zip
   
2. Install ldparteditor_1.8.83-1_amd64.deb
   
3. Start LDPartEditor from the menu or via launcher
   

Installation on Mac OS X:

1. Download and extract LDPartEditor_mac_x64.zip
   
2. Mount LDPartEditor-1.8.83.dmg
   
3. Drag LDPartEditor.app to the Applications folder
   
4. Copy ldparteditor.sh to your home folder
       4a. Open a Terminal.app and run ./ldparteditor.sh
       4b. Or open a Terminal.app and run /Applications/LDPartEditor.app/Contents/MacOS/LDPartEditor
   

I listen carefully to your requests and possible complaints. Please leave me a message, with your thoughts and wishes to further improve the software.

LDPE is a 3D CAD application: The overall system requirements are higher. While I recommend to use a powerful 64-bit multicore system, it could be possible, to run LDPE on older machines as well.

System Requirements:

Minimum System Requirements:

• OpenGL 2.1 compatible Graphics Card
  
• Operating System (64-bit): Windows [7 or newer], Linux [e.g. Ubuntu Linux >=14.4], Mac OS X [>=10.6]
  
• CPU: Multicore-Processor e.g. Intel Core 2 Duo or AMD Athlon II (>2.0Ghz)
  
• RAM: 4GB
  
• Video-Memory: 1 GB
  
• Free Disk Space: 150 MB
  

Recommended Requirements:

• Operating System (64bit): Windows 7,8,10,11, Linux [e.g. Ubuntu Linux >=14.4], Mac OS X [>=10.6]
  
• OpenGL 3.3 compatible Graphics Card
  
• CPU: Multicore-Processor with 4 cores (or more)
  
• RAM: >4 GB
  
• Video-Memory: >1 GB
  
• Free Disk Space: 500 MB
  
• For a faster start, LDPartEditor and the LDraw™ library should be installed on an SSD.
  

[N. W. Perry]

And you can now swap the XYZ coordinates of a selection (globally and locally) via "Actions..."->"Swap X/Y/Z (for Selection)".

Another request of mine! Much gratitude. :-)

(I also notice the upside-down startup icon is fixed, too.)

[Rene Rechthaler]

the dark mode is very nice...
but i've noticed that some buttons are hard to read now (for example, the "Reverse the manipulator axis" is a symbol of black text and doesnt get inverted) -> maybe use more text then (for the "Reverse" maybe use text with overline: https://en.wikipedia.org/wiki/Overline)

[Nils Schmidt]

the dark mode is very nice...
but i've noticed that some buttons are hard to read now (for example, the "Reverse the manipulator axis" is a symbol of black text and doesnt get inverted) -> maybe use more text then (for the "Reverse" maybe use text with overline: https://en.wikipedia.org/wiki/Overline)

Yesterday, I already fixed this issue (#1078).
It will be available with version 1.8.84 in 2-3 weeks.

[Magnus Forsberg]

Is there a way to adjust the colour scale on the Coplanarity Heatmap tool?
I find it anyoing that the dark blue for triggering "Quadrilateral near coplanarity" is so close to "Coplanarity is OK"

And when working with that tool I would like to have a way to force/accept the creation of a coplanar quad.
"These two triangles could become a quad, but only if I adjust one vertex. How should I adjust it?"

When I double click on the "Quadrilateral near coplanarity" error line, the text editor jumps to the line of code containing a problem.
Would it be possible to also have the quad in the 3D-view high-lighted?

Or, can I have a quad "auto-created" when I have moved one vertex enough to allow a flat quad?

[Nils Schmidt]

Is there a way to adjust the colour scale on the Coplanarity Heatmap tool?
I find it anyoing that the dark blue for triggering "Quadrilateral near coplanarity" is so close to "Coplanarity is OK"

And when working with that tool I would like to have a way to force/accept the creation of a coplanar quad.
"These two triangles could become a quad, but only if I adjust one vertex. How should I adjust it?"

When I double click on the "Quadrilateral near coplanarity" error line, the text editor jumps to the line of code containing a problem.
Would it be possible to also have the quad in the 3D-view high-lighted?

Or, can I have a quad "auto-created" when I have moved one vertex enough to allow a flat quad?

Thanks, Magnus. I created an issue (#1085).

[Magnus Forsberg]

Activate the move manipulator.
Place the manipulator on a surface by double clicking on it.
Double click on another surface, and the manipulator jumps to that surface.
Press Esc and the manipulator jumps back to the previous position.

Is that an error or an feature?

[Nils Schmidt]

Activate the move manipulator.
Place the manipulator on a surface by double clicking on it.
Double click on another surface, and the manipulator jumps to that surface.
Press Esc and the manipulator jumps back to the previous position.

Is that an error or an feature?

I think it is a bug. I created an issue (#1086).