Magnum Z Posted December 29, 2020 Posted December 29, 2020 I've run into an issue with trying to use intersectwith as a logic check. I believe the issue lies in the fact that while one object is a line and extendable, the other is not. I think the line is possibly not extending in the correct direction. Does this matter with this method? In other words, does obj1's (i.e. - line) "direction" matter in (vlax-invoke obj1 'intersectwith obj2 acextendthisentity) where obj2 is a non-extendable object? Quote
Jonathan Handojo Posted December 30, 2020 Posted December 30, 2020 It depends on what the other object is. If the other object doesn't support the intersectwith method, then the function can't return anything. You are right with using acextendthisentity. You can test for that method by using vlax-method-available-p function: (vlax-method-available-p obj2 'intersectwith) Quote
Magnum Z Posted January 4, 2021 Author Posted January 4, 2021 Thanks for that explanation, but it doesn't really answer my question. I have certain success without running a check with vlax-method-available-p on obj2. But I will try to incorporate it to make sure that every object assigned to obj2 is passing and not some fluke difference between them. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.