Eyeshot 2024.3 released
Alberto Bencivenni
Bologna, Italy — September 20, 2024. devDept Software S.r.l., leading provider of software development tools to the engineering industry, today announces the release of Eyeshot 2024.3, the CAD control for .NET
Available on our private NuGet server: http://nuget.devdept.com (Setup instructions)
What's New
- Added support for material texture rotation to Surface and Brep.Face classes
- Removed tolerance parameter from ICurve.Offset() methods
- Improved Surface and BRep filleting
- Enhanced Surface.Gordon() method
- Added the Rebuild() method to Curve and Surface classes
- Added keepTessellation parameter to most of the clone and copy methods to improve geometry duplication performance
- Added Offset() method to PolyRegion2D class
- Added print all sheets in a Drawing feature
- Added support for Intel ARC GPUs
- Added refPlane constructors to RadialDim and DiametricDim classes
- Improved ReadNastran and added WriteNastran class
Code Samples
You get these changes with setup download only
- Added Dimensioning code sample (Video)
- Revamped DragControlPoint code sample (Video)
- Improved CustomData code sample for EntityData cloning and serialization
- Improved Shaders code sample
To learn more about this update, please check the Changelog.
0
Comments
Hi there!
It would be really nice to also note the breaking changes in new versions. For example, there is a new abstract "CloneWithTesselation" method that Entity subclasses must implement and the Offset method signature has changed.
Best regards
Matthias
Hi Matthias,
I’ve added the CloneWithTessellation breaking change, while the Offset signature change is already included in the list. You can find the complete list of breaking changes here.
Just out of curiosity, are you directly inheriting from the `Entity` class?
Best regards,
Simone
Hi Simone,
we have classes inheriting from Entity and we also have classes inheriting from other Entity subclasses, such as Brep, Mesh, PointCloud etc. For now, I have just added dummy CloneWithTessellation implementations, but I will change those as soon as I can. So far, I have not run into any issues with that "wrong" approach. Can you tell me in what situations CloneWithTessellation will actually be called by Eyeshot or is it just something we can use instead of Clone for performance reasons?
Is there a reason why you make your copy ctors protected instead of public?
Best regards
Matthias
Hi Matthias,
The method is called in the Workspace.CopyTo() or BlockReference.Explode() methods when the keepTessellation flag is true.
The copy constructor is protected because there are already the public Clone() and CloneWithTessellation() methods available for use.
Best regards,
Simone
Please sign in to leave a comment.