![]() ![]() ![]() But a few initgets, command prompts, and an undo marker of some sort would be fairly trivial program additions. Of course, there's no need to go overboard programming. Some of my comments have been made with that thought in mind. It appears that some effort has been expended on making the program bullet proof (storing system variables, layer names, etc.). If more user interaction was desired, I would agree that the approach you described would be more appropriate here.ĪFAICT, the intent appears a quick and dirty routine to cover a very frequently used (and very specific) hatching function. Just pick a single point (with no prompting at that) inside the area to be hatched, and the routine immediately processed the info (without pausing to show the hatch boundary). Agreed to a point, but there was no attempt in the original routine to accommodate that kind of user interaction, let alone reviewing the boundary or picking additional areas for hatching. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |