Release notes 0.19/it

 Are features missing? Mention them in the Release notes for v0.19 forum thread.

See Help FreeCAD for ways to contribute to FreeCAD.

FreeCAD 0.19 was released on DD Month 2020, get it from the Download page. This is a summary of the most interesting changes. The complete list of changes can be found in the MantisBT bugtracker FC 0.19 changelog.

Le note di rilascio delle versioni precedenti di FreeCAD sono disponibili in Funzioni di FreeCAD.



Simpson and Shipton short stroke steam engine circa 1845, using horizontal rotating piston, by "un1corn", Users Showcase.

Punti salienti


This assembly was made by "Zolko", author of the new Assembly4 Workbench, which uses the new powerful App Link object to import thousands of different parts and subassemblies, arranging them in specified positions by means of mathematical expressions. See Users Showcase.

For this model, the parts were not designed in FreeCAD, they were just imported in STEP format, and subsequently arranged with Assembly4.
 * }

Aspetti generali
Con oltre 2000 commit nel ramo master dalla versione 0.18, questa è una delle versioni più estese di sempre, con diversi nuovi componenti come il nuovo oggetto "App::Link", oltre a molti nuovi strumenti nell'ambiente TechDraw che rendono FreeCAD ancora più potente per la modellazione e l'assemblaggio di solidi 3D. Inoltre, l'ecosistema di FreeCAD ha continuato a crescere con ulteriori ambienti di lavoro esterni specializzati.

Python 3 e Qt5
Lo sforzo di migrare da Python 2 e Qt4 a Python 3 e Qt5 è sostanzialmente completo e la maggior parte degli sviluppatori è passata agli strumenti di Python3 e Qt5.

Indubbiamente ci sono bug imprevisti; questi saranno affrontati man mano che vengono segnalati. Qualsiasi dipendenza esistente da Python 2 o Qt4 non sarà supportata oltre il 1 ° gennaio 2020, data in cui Python 2 diventerà ufficialmente non più supportato dalla Python Foundation. Notare che alcuni componenti aggiuntivi non sono stati ancora portati su Python3 e Qt5. Ciò può essere dovuto a diversi motivi tra cui la mancanza di tempo da parte dei loro sviluppatori o dipendenze interrotte che potrebbero non essere facilmente risolvibili o semplicemente perché l'addon è considerato obsoleto. Le persone interessate alla migrazione di un particolare ambiente di lavoro o strumento sono incoraggiate a partecipare al forum di FreeCAD; vedere anche Python3 and Qt5 Compatible Addon Workbenches (in preparazione per 0.18).

Alcuni problemi
Fixed issue with Std Part containers visibility when the viewport is displayed in full screen in Qt5:
 * Set for Qt 5.9 and above; forum discussion, commit 2a1dd8415, and commit 57b3ca6f77.
 * Disabled button support in  for Qt5 to avoid MDI view mode-related rendering artifacts; forum discussion, commit 960d612547.
 * Fixed bug in to avoid a crash when returning from full screen; forum discussion, commit c4e34ed9b.
 * Fixed issue #4088 about the visibility of the origin of a Part changing when undocking the 3D view; forum discussion, commit 1e19ef5be.
 * Fixed issue #3130 about Qt5 bugs when using a high resolution external monitor; forum discussion, commit 2f2d505359.

Sviluppo

 * New Libpack for Windows with Qt 5.12, OCC 7.3, and Python 3.6; forum discussion.
 * New Libpack for Windows with Qt 5.12.6, OCC 7.4; forum discussion, pull request #2944.
 * There is a new Docker container to build FreeCAD, see Compile on Docker; forum discussion.
 * The infrastructure of the bug tracker as well as wiki was moved to a dedicated server, so that it is easier to manage by the project administrators; forum discussion.

Documentazione

 * La pagina Compilare su Linux/Unix è stata rivista per spiegare meglio i requisiti per compilare su diverse distribuzioni Linux. Poiché molti sviluppatori utilizzano sistemi basati su Debian, questa sezione ha ricevuto la massima attenzione. Gli utenti di altre distribuzioni Linux sono incoraggiati a mantenere la documentazione per la loro particolare distribuzione. Anche Compilare su Windows è stato riscritto per spiegare come usare il LibPack per la compilazione.
 * La pagina Documentazione del codice sorgente è stata ripulita per spiegare meglio come produrre la documentazione di programmazione (API) partendo da C++ e Python.
 * La pagina Doxygen è stata rivista ed estesa per fornire maggiori dettagli sulla sintassi utilizzata nei file C++ per produrre la documentazione di programmazione.
 * Anche la pagina Gestione del codice sorgente è stata rielaborata con descrizioni ed esempi migliori sull'uso di per gestire i rami e contribuire al codice.
 * La pagina Ambienti di lavoro esterni è stata riorganizzata, in modo da elencare tutti gli ambienti ricchi di funzionalità e disponibili al pubblico. Se si desideri aggiungere un workbench a questa pagina, comunicarlo nel forum e fornire le informazioni di supporto come il manuale dell'utente, le pagine wiki e un link al suo repository. Quindi spingere per includerlo in Addon Manager.

Limitazioni note

 * Black screen due to video card drivers, while running FreeCAD inside a virtual machine; issue #3939.
 * Logitech Wingman USB joystick can cause erratic behavior when spinning and zooming in the view; forum discussion.
 * Gesture navigation is fully supported for Windows but yet to be maintained in Linux and MacOS. Problem: the developer, DeepSOIC, doesn't have a MacOS machine with its special trackpad, and hasn't tested it on Linux either; forum discussion.

App::Link e assemblaggio


Dopo 2,5 anni di sviluppo, l'oggetto "Link", o più formalmente, è stato introdotto in FreeCAD. Questo è un tipo speciale di con alcune proprietà che, si spera, consentiranno di semplificare gli assemblaggi.

Un "Link" consente agli oggetti di utilizzare i dati di un altro oggetto, come la geometria o anche la loro rappresentazione visiva 3D, negli stessi file o in file diversi. Può essere pensato come un leggero clone assoluto o come lo stesso oggetto che vive in due "istanze" diverse. Alcune funzionalità offerte da un "Link" sono già presenti in alcuni ambienti come Arch e BIM (cloni, riferimenti esterni ), ma l'implementazione di "Link" è al livello principale e può quindi essere utilizzato da tutti gli ambienti in diversi modi.

Il componente "Link" è stato pensato e sviluppato quasi interamente dall'utente. Le motivazioni e le implementazioni progettuali alla base di questo progetto sono descritte nella sua pagina GitHub, Link. Per realizzare questa funzione, sono state apportate diverse modifiche fondamentali a FreeCAD; queste modifiche sono ampiamente documentate in Core-Changes.

La storia di "Link" può essere rintracciata tramite alcune discussioni essenziali del forum:
 * Why an object can only be inside one App::Part? (March 2017)
 * Introducing App::Link/XLink (March 2017)
 * Links (May 2017)
 * Realthunder Link implementation: Architecture discussion (June 2017)
 * PR #876: Link, stage one, context aware selection (July 2017)
 * Preview: Link, stage two, API groundwork (July 2017)
 * Assembly3 preview (December 2017)
 * Merging of my Link branch (June 2018)

Finally, the pull request and merge happened:
 * App::Link: the big merge, old thread (July 2019), pull request #2350 (the BIG merge), LinkMerge branch.
 * App::Link: the big merge, main thread (July 2019)
 * A simple path description of Link, 019, Link stage, Asm3, merge? (August 2019)
 * PR#2559: expose link and navigation actions, an introduction to the Link feature in 0.19 (September 2019).

The "App Link" object prepares FreeCAD for the phase that was scheduled to happen after the redesign of PartDesign in FreeCAD 0.17, which is working with assemblies.

Assembly3 is an assembly workbench written in Python by realthunder, that makes use of the "App Link" functionality. The workbench served as a testbed for this component during its development. While Assembly3 is still not officially part of FreeCAD, with the inclusion of "App Link" in the master branch, it is a matter of time for Assembly3 to be provided as an installable add-on, just like A2plus and Assembly4 are provided currently.

Core system, App, Base, and Gui namespaces
Beside the introduction of App Link, the "LinkMerge" branch also introduced some changes visible to the user with regards to object properties, expressions, visual selection, and the tree view. These are described in the Core-Changes page.


 * Added support for existing Python virtual environments; pull request #2021.
 * Pre-select name filter in the import/export dialog; forum discussion, commit e239994,
 * Fixed missing application ID and icon on GNOME/Wayland; pull request #2466.
 * Added support for Hertz as a physical unit, and added the Frequency property; forum discussion, commit 3500451a0, commit d7ca604c9.
 * Added Std TextDocument tool to insert an object to store arbitrary text in the document; commit 13db5b0560, commit 53b01f08f9.
 * Added support for further units, Gauss, Weber, Oersted; forum discussion, pull request #2863.

Ambiente Arch
Keep with the latest developments in architecture and BIM by following the main author of this workbench; BIM/Arch development news articles from Yorik's blog.

Altro

 * The Draft Wire tool now is called "Polyline" in the menu, instead of "DWire"; all options and functionality remain the same, so this doesn't break compatibility; commit 39e748229e.
 * A "DraftEditPickRadius" preference was added to control the area of influence of the pointer when picking vertices in edit mode Draft Edit; forum discussion, pull request #2642, issue #4162.
 * Undergoing efforts to document the Python source code (adding complete docstrings), in order to produce better programming documentation that can be used by both users and developers. See Source documentation for instructions on generating the documentation with Doxygen.
 * The "Toolbar mode" when launching the Draft tools has been removed. This was an interface that was used in the past but became obsolete as the task panel became the predominant interface; forum discussion, pull request #2973.

Altro

 * Updated coding standards that strive for PEP8 compliance with Python; forum discussion, commit ad03ee9bdf, commit 27cb54009b.
 * The Elmer project has developed a library for handling batch type pre-processing for the ElmerSolver, using the FEM Workbench. This includes creating mesh objects for FreeCAD, manipulating the mesh sizes of solids, creating finite element meshes using Gmsh, running ElmerGrid and exporting the mesh for ElmerSolver, and selecting and naming bodies and boundaries for ElmerSolver; forum discussion, elmerfem repository (Elmer main repository), FreeCADBatchFEMTools repository (library to interact with FEM Workbench, LGPL 2.1).
 * The integration of the OOFem solver, which started in 2018, is progressing, so it is now another option that can be used for structural analysis in FreeCAD. This solver is interesting in that it has interface elements, as well as arc-length control, in addition to many non-linear material models. The integration of OOFEM into FEM has been carried in various commits that together serve as documentation on how to integrate similar solvers; forum discussion, femoofem branch, OOFEM main website, oofem repository (LGPL 2.1).

Import

 * Improved import/export compatibility with proprietary CAD systems, when using compressed STEP, or STPZ; forum discussion, pull request #2323, commit 7de89cf62e.

Further improvements

 * It is now possible to take an OpenInventor mesh file, and export it to STL; forum discussion, commit 601ac707b207c6.

Further improvements

 * Fixed broken support for "INCH" units when exporting to STEP/IGES formats; forum discussion, commit 1b26173580.
 * New Face method: to cut holes into a face. The face usually needs to be validated after operation.
 * The App Link merge introduced two new commands, Part TransformedCopy and Part ElementCopy. These commands create non-parametric copies of a body with a transformed placement, and of an element (vertex, edge, or face); commit 6da72b9859. These operations essentially make the Macro Repro Wire obsolete.

Ambiente Path

 * Tool manager support for multiple tool tables


 * Added Path DressupBoundary for excluding parts of a path


 * PathPocket: Extensions (For milling open pockets).
 * ProfileEdges: Open Edges support.
 * First attempt of 4th-axis support: Contour, PathFaces, PathPocket, and Drilling

Altro

 * Fixed issue #3993, Python 3 memory leak; forum discussion, commit 3c205946e.
 * Ability to use an arbitrary number of an object as the base model for a Path.Job, each one being positionable individually; pull request #2056.
 * PathDeburr: Added direction selection. Fixed DressupLeadInOut problem.
 * MillFace: Clear edges.
 * MillFace: Exclude raised areas; forum discussion, pull request #2367.
 * Update of some Post Processors (Mainly GRBL and LinuxCNC).
 * Adaptive Clearing improvements.
 * 3D Pocket: Reduction of air-milling above inclined pockets; forum discussion, pull request #2366.
 * 3D Surface: Improvements to both the OCL DropCutter and the Waterline algorithms
 * 3D Surface: Initial 4th-axis support; forum discussion, pull request #2114.
 * 3D Surface: Selection of individual faces; pull request #2849.
 * Post: Mach3/Mach4 Post Processor; pull request #3195.
 * Post: Support tool height offset in the LinuxCNC Post Processor; pull request #2479.

Ambiente Render
Added support for Blender's standalone "Cycles" renderer; commit 759067912f; FreeCAD-render repository. The Cycles standalone renderer usually needs to be compiled from source, as the binary is normally not provided by itself in a complete Blender distribution.

Besides this, the Render Workbench already has support for Pov-Ray, Luxrender and Appleseed.

Ambiente Spreadsheet
The introduction of App Link also brought some improvements to the expressions capabilities of FreeCAD, which are visible in the property editor, and the Spreadsheet Workbench. These are described in Core-Changes and this forum thread.
 * A new expression syntax is introduced to unambiguously reference a property of the owner object, by omitting the object reference and starting with a leading dot, similar to Python relative import syntax. So instead of , now you can use.
 * You can refer to an object by its or by its . In the case of a, it must be enclosed in  and  symbols, such as . For example,.
 * Improved spreadsheet recomputation logic, and cell copy and paste functions. Pull request #2350, #2475.

The previous commits changed the way the autocompletion works with expressions, particularly when used with Sketcher constraints, which was seen as a regression for many use cases. A new set of commits were proposed to restore this functionality; forum discussion, pull request #3062.

Altro

 * There has been discussions about changing the standard behavior of TechDraw. Instead of keeping the drawing pages updated automatically, they would be updated only on demand; this would mitigate the effects of TechDraw slowing down the rest of FreeCAD when modelling. Moreover, now that App Link is included in FreeCAD, TechDraw pages may be stored in a separate file, and loaded on demand; forum discussion (main discussion), forum discussion (alternatives).
 * Fixed font size issues when exporting to SVG; forum discussion, pull request #2219.
 * Fixed regression in caption handling and hide caption property where not applicable; pull request #2228.
 * Added options for page size, line width and background when saving to SVG; this improves Draft/Arch and TechDraw integration; pull request #2455.
 * New panning of the page using the middle mouse button; forum discussion, pull request #2458.
 * Finer control of drawing updates; forum discussion, pull request #2468, commit 5bed53f858, commit b2d8eeeb65.
 * Also new TechDraw Redraw tool to force a drawing page update while ignoring the state of the options "Update with 3d", "Allow page override", or "KeepUpdated". This tool disappeared in 0.18, but was re-implemented for 0.19; forum discussion.
 * The new App Link object is now supported as a source for creating views; forum discussion, commit 37b578bf49.

Web

 * QtWebEngine support for Qt 5.7 and above, and fallback to QWebkit for Qt 5.6 and below; pull request #1937.

Macro
See Macros recipes for many more macros.

Moduli aggiuntivi
these are the new workbenches created in this development cycle, or older workbenches that received updates. See external workbenches for more workbenches that can be installed, and which cover a wide variety of topics. If you want to see your workbench added, join the forum and present your code.