With the CrossView implementation is it possible to only go a set distance across the part, or is it just infinitely long?
We get a lot of "External component has thrown an exception" which kills the application with no chance of catching it.
One issue we may be facing is having meshes too complicated for the control to handle, but unsure. The kcad object doesn't seem to use threads or asychronous operations to complete its task, so when an action is too big, the application will freeze until it finishes, if it ever does, which most of the time it doesn't and just ends up consuming all available memory.
Problems with control
Re: Problems with control
Hello
Sorry about the bugs. Normally almost every project has issues initially. Geometry can be so different. We are here to help. Once it gets going it will work for years
1. Yes. The CrossView shows intersection with planes, which are assumed to be infinite. Once intersection is calculated it is pretty easy to access the resulting curve. It is basically one or more arrays of points. You can easily trim away the points you do not need.
If you just need only to show part of it on the screen you can use clipping planes as demonstrated in the Clip sample.
If the object is large or there are some problems with the surface I strongly recommend reducing the object size using clipping planes or other method like described here: http://www.dynoinsight.com/phpBB3/viewt ... f=2&t=2876
2. The exception. In cases like that the first thing to do is to reduce the problem by removing irrelevant objects and reducing the size of the object as I just described. If nothing works, prepare a small test and upload it here or send to us directly with the reduced model and instructions explaining the way to reproduce
3. Performance. KC does not have limits on size of the mesh. Some operations will be slow with any software. Boolean operations with large fine meshes would be always slow. This is always the problem with meshes. Consider fitting a spline like in the Diff Surface sample.
You also need to feel how the soft handles load. Start with small and nice models and increase the complexity gradually
Generally operations are not thread safe. But if you need to do some background calculations without rendering you can try setting up a thread in the application. Often it will work if you do not use the same functionality on several threads.
For really heavy lifting consider a custom project. We would be happy to make some operations thread-safe or optimise it internally. Quite often it is just matter of work.
Nick
Sorry about the bugs. Normally almost every project has issues initially. Geometry can be so different. We are here to help. Once it gets going it will work for years
1. Yes. The CrossView shows intersection with planes, which are assumed to be infinite. Once intersection is calculated it is pretty easy to access the resulting curve. It is basically one or more arrays of points. You can easily trim away the points you do not need.
If you just need only to show part of it on the screen you can use clipping planes as demonstrated in the Clip sample.
If the object is large or there are some problems with the surface I strongly recommend reducing the object size using clipping planes or other method like described here: http://www.dynoinsight.com/phpBB3/viewt ... f=2&t=2876
2. The exception. In cases like that the first thing to do is to reduce the problem by removing irrelevant objects and reducing the size of the object as I just described. If nothing works, prepare a small test and upload it here or send to us directly with the reduced model and instructions explaining the way to reproduce
3. Performance. KC does not have limits on size of the mesh. Some operations will be slow with any software. Boolean operations with large fine meshes would be always slow. This is always the problem with meshes. Consider fitting a spline like in the Diff Surface sample.
You also need to feel how the soft handles load. Start with small and nice models and increase the complexity gradually
Generally operations are not thread safe. But if you need to do some background calculations without rendering you can try setting up a thread in the application. Often it will work if you do not use the same functionality on several threads.
For really heavy lifting consider a custom project. We would be happy to make some operations thread-safe or optimise it internally. Quite often it is just matter of work.
Nick
Re: Problems with control
One of the errors that can be produced easily, which maybe by design, but an oversight, is that when you create a VB.NET project targeting .NET Framework 4, even though the application compiles and loads, right clicking the control and clicking to open the Model Viewer, and the applications immediately crashes with one of these uncaught exceptions
Re: Problems with control
Hi atrev
I have moved this to a new thread as it is another topic.
http://www.dynoinsight.com/phpBB3/viewt ... f=3&t=2877
Pls see my answer there
Nick
I have moved this to a new thread as it is another topic.
http://www.dynoinsight.com/phpBB3/viewt ... f=3&t=2877
Pls see my answer there
Nick