Jef! Posted September 14, 2018 Share Posted September 14, 2018 On 9/12/2018 at 6:47 PM, vanowm said: In my case the boundary being created successfully (creates POLYLINE on top of LWPOLYLINE) Well here is your problem: boundary either creates a region or a pline/lwpline. Difference between pline/lwpline is controled by the var 'plinetype. Change it to 2 (setvar 'plinetype 2), and your boundary will generate lwpline instead of plines. LWpline only have sets of 2 coords in assoc 10, and everything will work as it used to(as long as a boundary can be created successfully of course)! If my reply help you solve your problem, please consider marking it accordingly. Thanks and have a nice week end! 1 Quote Link to comment Share on other sites More sharing options...
vanowm Posted September 14, 2018 Share Posted September 14, 2018 19 minutes ago, Jef! said: Well here is your problem: boundary either creates a region or a pline/lwpline. Difference between pline/lwpline is controled by the var 'plinetype. Change it to 2 (setvar 'plinetype 2), and your boundary will generate lwpline instead of plines. LWpline only have sets of 2 coords in assoc 10, and everything will work as it used to(as long as a boundary can be created successfully of course)! That's it! Thank you very much, it's working now. I guess it would not hurt change this var in the script, to avoid such issue. Quote Link to comment Share on other sites More sharing options...
Jef! Posted September 14, 2018 Share Posted September 14, 2018 That would indeed be a good idea and make it more robust... and you are very welcome. Quote Link to comment Share on other sites More sharing options...
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.