Thank you so much for creating this series! These are the best and most up to date videos for learning AutoLISP that I have came across. Looking forward to more videos in this series.
Thank you so much for taking your time to make an video about this ! I would never be able to figure this out my own. Now I will share this video with my coworkers too
@@ATCCAD you’re welcome ! If you would like to hear more ideas, I could share some problems that I’m facing that I feel like it could potentially be a video for the channel. Thank you
Great video! I'm starting on LISP programming and I just found your channel. Great content. I believe you could do the same to attributes on a block, right? Maybe for a future video, it could help a lot. Or maybe you can add numbers to strings, like, it would add the text "Block Number 1", "Block Number 2"... Thank you!
Nicely explained. Can you add these inputs (Starting number and Interval) as options to the command and use the capital letter of the option word to choose them?
Wow! I didn't expect anyone to reach the end of the integer range! While integers can be larger (+/-2,147,483,647) the getint function is limited to 16 bits, a range of -32767 - 32767. In order to ask the user for an integer larger than that, you need to use getreal or getstring and then convert the value into an integer inside the function using something like (setq myInteger (atoi userString)) Using this means you'd have to check for a failed conversion in case the user typed "Bob" instead of 1,234,567
This video is fantastic, but how do you avoid the error when using the ESC key? I did find some hints of using visual lisp commands, such as vl-catch-all-apply, but I'm not really sure how to implement it in this code exactly.
This requires using the * error * function - which was outside the scope of this video. I have a video planned for this topic - but this error is an easy one to deal with. Here is a way you can do it. In the main body of the program - at the top where you initialize the other variables - add the following two lines (setq tmperror * error *) ; saves the old * error * function so it can be restored after the user cancels the command (setq * error * errorfunc) ; sets the name of the new *error* function so LISP can find it Finally you'll add a new function - at the bottom would be good (defun errorfunc (errmsg) (setq * error * tmperror) ; Set the *error* function back to the old one (princ) ; Print a blank line )
@@ATCCAD Oh wow, thank you super much. You would think that this would be a simple 1 line command to stop all the errors, but I guess the Autodesk guys really like jumping through a lot of hoops. Can't wait to see that future video, have a fantastic day ^_^
Nicely explained.
Thank you 🙂
Glad you liked it
Thank you so much for creating this series! These are the best and most up to date videos for learning AutoLISP that I have came across.
Looking forward to more videos in this series.
Than you very much! The next video in this series should be out at the end of the month (or the first week of next month)
Thank you so much for taking your time to make an video about this ! I would never be able to figure this out my own. Now I will share this video with my coworkers too
I'm glad it helped! Thanks for the video idea 😄
@@ATCCAD you’re welcome ! If you would like to hear more ideas, I could share some problems that I’m facing that I feel like it could potentially be a video for the channel. Thank you
I definitely welcome comments like that!
Great video! I'm starting on LISP programming and I just found your channel. Great content.
I believe you could do the same to attributes on a block, right? Maybe for a future video, it could help a lot. Or maybe you can add numbers to strings, like, it would add the text "Block Number 1", "Block Number 2"...
Thank you!
Absolutely! Part two of this video will add blocks and various other options
Nicely explained. Can you add these inputs (Starting number and Interval) as options to the command and use the capital letter of the option word to choose them?
Yes, that can definitely be done. That'll be in part 2!
Very useful!! However is there any way to implement bigger numbers? It says that the biggest number is 32767
Wow! I didn't expect anyone to reach the end of the integer range! While integers can be larger (+/-2,147,483,647) the getint function is limited to 16 bits, a range of -32767 - 32767.
In order to ask the user for an integer larger than that, you need to use getreal or getstring and then convert the value into an integer inside the function using something like (setq myInteger (atoi userString))
Using this means you'd have to check for a failed conversion in case the user typed "Bob" instead of 1,234,567
This video is fantastic, but how do you avoid the error when using the ESC key? I did find some hints of using visual lisp commands, such as vl-catch-all-apply, but I'm not really sure how to implement it in this code exactly.
This requires using the * error * function - which was outside the scope of this video. I have a video planned for this topic - but this error is an easy one to deal with. Here is a way you can do it.
In the main body of the program - at the top where you initialize the other variables - add the following two lines
(setq tmperror * error *) ; saves the old * error * function so it can be restored after the user cancels the command
(setq * error * errorfunc) ; sets the name of the new *error* function so LISP can find it
Finally you'll add a new function - at the bottom would be good
(defun errorfunc (errmsg)
(setq * error * tmperror) ; Set the *error* function back to the old one
(princ) ; Print a blank line
)
(All of these error statements should have a * before and after it. RUclips comments isn't displaying it right!)
* error * (without the spaces)
@@ATCCAD Oh wow, thank you super much. You would think that this would be a simple 1 line command to stop all the errors, but I guess the Autodesk guys really like jumping through a lot of hoops. Can't wait to see that future video, have a fantastic day ^_^
@inkscapepanda Ehh, like most things in CAD, if it's flexible, then it's complicated!
I had a bit of a weird problem with this. I set up a text style and it broke the counter. now the counter only puts up the number 0.
In the next video in this series I found this potential bug and fixed it!
Auto lips Default setting explain 🤔
Default setting? What do you mean?
@@ATCCAD lips file one time app load don't again again app load
Ahh! Check out my previous video ruclips.net/video/fhV0Gx7qUmA/видео.html