This page lists the important behavior and API changes introduced in this version. If you already have projects using devDept products, you will need to peruse this list to understand the changes you might need to make to your source code to support this new release.
2024.3
BC-263 | Added Entity.CloneWithTessellation() abstract method | Check this article on how to clone a custom entity |
BC-262 | Resolved conflict between Viewport.InitialView and Viewport.Camera properties in WPF designer settings | Fixed an issue in the WPF designer settings where Viewport.InitialView and Viewport.Camera properties were conflicting when both were defined in XAML. Now, you must specify either the Viewport.InitialView property or the Viewport.Camera property, but not both simultaneously, as they interfere with each other’s functionality. |
BC-261 | Changed RenderContextBase.DrawRichSmoothTriangles() method signature | RenderContextBase.DrawRichSmoothTriangles() and RenderContextBase.DrawRichSmoothInvTriangles() methods need an additional rotation parameter |
BC-260 | Changed ICurve.Offset() and OffsetToRegion() methods signatures | Removed the tolerance parameter because it is not necessary anymore |
BC-259 | Changed RenderToBitmap() method signature | Changed the parameters drawScale and lineWeightFactor type from double to float |
BC-258 | Changed Label.Draw() method signature | Added double drawScale parameter |
BC-257 | Removed Workspace tooltip-related methods | Some public/protected methods related to tooltips have been removed and are now for internal use only.
|
BC-256 | Changed signature of Document.CopyTo() method | Added keepTessellation parameter to Document.CopyTo method. |
BC-255 | Removed Surface.Gordon(IList<ICurve>, IList<ICurve>, Point3D[,]) method overload | From now on, you need to call Surface.Gordon(IList<ICurve>, IList<ICurve>), the intersections will be calculated within this method. |
BC-253 | New prerequisites for Eyeshot.x64 and Eyeshot.x86 | The ODA libraries have been upgraded from version 23.11 (v14) to 25.7 (v17) and now include native assemblies for .NET. This means we have different DLLs for .NET Framework, .NET 6, .NET 7, and .NET 8. Please note that you must install the latest Microsoft Visual C++ Redistributable version. |
BC-251 | SystemSolved event | SketchEntity.SystemSolved event is now raised by SketchEntity.UpdateAndInvalidate() |
BC-250 | Removed SelectedSketchPoint class | Keeping both SelectedSketchCurve and SelectedSketchPoint classes was unnecessary since we now have a single list of curves (SketchEntity.CurveList) with both points and curves. |
BC-249 | SketchCurveLinked and SketchCurveDeleted events | Previously, the SketchCurveLinked and SketchCurveDeleted events were not raised for the points attached to a curve. Now, the handler will be invoked once for the sketch curve and once for every point liked to it, for example, after calling SketchEntity.AddLine(), SketchCurveLinked will be raised free times: once for the line, once for the start point, and once for the endpoint. |
BC-247 | AddedSketchCurve and DeletedSketchCurve properties | SketchCurveLinkedEventArgs.AddedSketchCurve and SketchCurveDeletedEventArgs.DeletedSketchCurve are now of type ICurve. Instead of containing the geometrical sketch entity SketchCurve, the event arguments now store the graphical ICurve. |
2024.2
BC-248 | Removed IsolateAvailable property |
Removed Workspace.IsolateAvailable property. Isolate feature is now always available. |
BC-246 | ReadSTEP class refactor |
What has changed:
When you can't find your entities, in most cases you need to change this:
like this:
|
BC-245 | Changed SymbolSize property |
Changed PlanarEntity.SymbolSize property type to double |
BC-244 | Changed CompileInternal() method signature |
The EntityGraphicsData parameter has been removed from the RenderContextBase.CompileInternal() method. Use the CompilingEntity property instead. |
BC-243 | Renamed GetAllEnclosedEntities() method |
Renamed Workspace.GetAllEnclosedEntities() method as GetEnclosedEntities() |
BC-242 | Changed GetCrossingEntities() method signature |
Removed accParentTransform parameter from Workspace.GetCrossingEntities() method |
BC-241 | Removed GetAllCrossingEntities() method |
Removed Workspace.GetAllCrossingEntities() method, use GetCrossingEntities() with firstOnly parameter to false instead. |
BC-240 | Obsolete selection methods |
Removed obsolete selection methods |
BC-239 | ZBufferBase.IsInvalidRange() method |
ZBufferBase.IsInvalidRange() method has been changed to property |
2024.1
BC-254 | Removed labels GDI drawing methods |
All GDI drawing methods for labels have been removed, standard drawing methods can be used instead. |
BC-238 | Renamed Transformation.IsScaled |
Renamed |
BC-237 | Entity.TransformBy() |
The behavior of Entity.BoxMin/BoxMax properties after entity transformation was inconsistent across entity types. For some entity types, those properties were updated, for others they were not. In Eyeshot 2024, this is uniform. |
BC-236 | GetAssembly() method |
Since there is a unified installer for all the editions (Pro, Ultimate, Fem), the method Workspace.GetAssembly() does not return the info about the edition anymore. You can use Utility.ProductEdition instead. |
BC-235 | XRefPath, FullPath, FileName properties |
Block.XRefPath, Block.FullPath, ReadFileAsync.FileName, WriteFileAsync.FileName, HiddenLinesView.FileName properties were renamed to FilePath. |
BC-234 | Removed small object culling feature |
The feature has been retired in Eyeshot 2024. Removed |
BC-233 | Removed Turbo feature altogether |
Turbo feature has been retired in Eyeshot 2024 |
BC-232 | Changed GetVisualRefinementDeviation() method |
|
BC-231 | Removed LicenseManager class |
Removed |
BC-230 | Renamed InitializeScene event |
Renamed |
BC-229 | PrintSimulationMesh and MultiFastMesh classes |
|
BC-228 | Removed Leaf suffix from code selection method names | Renamed GetAllCrossingEntitiesLeaf() method to GetAllCrossingEntities() Renamed GetCrossingEntitiesLeaf() method to GetCrossingEntities() Renamed GetAllEnclosedEntitiesLeaf() method to GetAllEnclosedEntities() Removed protected overload Workspace.GetCrossingEntities(Rectangle, bool , out List<SelectedItem>, bool)
|
BC-227 | IFC properties |
Removed Removed the |
BC-226 | WPF Toolbar color properties |
Changed WPF |
BC-225 | Removed SketchManager class |
Please check this article. |
BC-224 | ProgressBar class |
Closed some ProgressBar class methods:
|
BC-223 | Removed ResizeBegin() | Removed the obsolete Workspace.ResizeBegin() method |
BC-222 | DWG/DXF import | Extruded surfaces and curves with a defined thickness are now imported from ReadAutodesk class as Brep entities. |
Eyeshot version 2024 is based on NET6/NET7/NET8 and Framework 4.7.2
Previous versions of this article: Eyeshot 2023, Eyeshot 2022
Comments
By that do you mean it should still be possible to build an app against .net framework 4.7.2 ?
Other notes released along the year seems to point to the fact it wouldn't be supported on anything else than .NET 6 and up
Hi - i would also like to now whether 4.7.2 is still supported? Our software is still a few years from being upgraded
Hello,
I can confirm that Eyeshot 2024 still offers support for .NET Framework 4.7.2.
Eyeshot is now delivered through NuGet packages that are compatible with .NET Framework 4.7.2, .NET 6, .NET 7 and .NET 8.
We would like to clarify that in some of our release notes when we mentioned Visual Studio 2022 and .NET 6, we were referring to source sample codes included with the installer. These codes are designed to target .NET 6, and to work with them and get the full experience of Eyeshot 2024, it is necessary to use Visual Studio 2022.
We apologize for any confusion that may have arisen due to the way our message was phrased. We plan on revising those notes to provide better clarity.
I appreciate your understanding.
Hello
I just want to let you know that devDept.Geometry.Transformation IsScaled was renamed to HasScaling (according to properties description) and there is no BC entry. Isn't reported by migration tool too.
Hello Matteo,
Thank you for reporting the missing item, I have updated the article and we will also update the migration tool.
Can a developer without license continue to develop without a license? After upgrading to Eyeshot 2024, I am seeing an "invalid developer license" while trying to run in debug. Please advise.
Hello Ron,
You should see that error message only if you interact with Eyeshot. If you need to interact with Eyeshot, you need to purchase a license.
LeaderAndText.ComputePositionsGDI has been renamed too.
Please sign in to leave a comment.