6/16/2023 0 Comments Tomtom home dll not foundSo, as in your example, the instance of the public VesselShape class, declared from a referenced DLL, is 'controlled" within SolveInstance(…) scope once the class is instanced. As such, any types created within a protected method are only accessed from within that methods scope. The code states that SolveInstance(…) is a protected method of the GH_Component class. My confusion is perhaps regarding access modifiers. I would like to use components to fetch the data I want to visualize/evaluate from classes maintained in the external DLL without 'wires" and the associate delay of “Gooing” the inputs. (Resize the vesselShape to fit inside the rough material block, or view the meshing density/correctness of each rough cut layer Brep) and, 3) For the intervening steps toward the generation of GCode (meshing, interference testing, Axis rotation, kinetic evaluation, etc) to view and evaluate the computations for reasonableness. My goal is to use custom components to: 1) enter and validate job parameters, 2) visualize the result of those parameter settings. In the journey to solidify my understanding C#, I am sure that I have missed fundamentals along the way. You should always be able to use whenever and whereever you need that code. The Validator and VesselShape class is part of your dll. Var validator = new Validator(string arg1 …) You should never be in need to what you do: Lets assume your SolveInstance is only in charge of receiving and sending data from and to other components. dll without any need to run and rely on Rhino. Especially if you manage to get rid of any Rhino or GH references, you can completely develop, test and maintain the. It is totally right to do the computation in a separate dll. I do work on multiple solutions with multiple projects inside, but I was never in need to create a static interface just for the purpose of exchanging data inbetween my dependencies. I do have the feeling you missed something fundamental when working with multiple projects. My goal is to forward jobparams for use by the DLL in subsequent processing without the inefficiencies of outputs. Initial tests show that when a class definition resides in an external DLL and that DLL is referenced to the Validate component, an instance of the jobparams class is created as a local variable in the component. Later, I would like to pass class(s) from an external DLL back into custom components allowing for visualization of processed data. My initial question involves passing a number of component input values by first packaging the data within a class. In my case, GH_Components better serve to visualize/evaluate the results of intermediate steps and not be required to input or output the massive computational data needed for the final GCode. The generation of tool paths is an expensive computation that includes large volumes of data - points, transforms, offsets, meshes, etc.īased on my Forum research, it is suggested that the custom component(s) should be kept light as far as processing burden, and push the heavy lifting to a separate DLL. The CAM step - that of reducing a block of raw material to a desired shape, requires parameters and computations that produce tool path instructions. I have been learning C# over the past few years and am now developing a set of custom components that will produce GCode for a specialized 5 AXIS CNC machine.
0 Comments
Leave a Reply. |