C:\> How to protect the BricsCad2024selling?
I wish I could use BLADE but I can't.
VLIDE was actually really really good back in its day.and it still is
VLIDE was actually really really good back in its day.and it still is
i'm doing some python programming at the moment and i use Wing Pro as my IDE. although it is overwhelmed with modern features but whenever i switch back to VLIDE there is only one thing that i'm missing - it's automatic highlighting of all occurrences of the selected text
and minimal control over window pane location in the IDE, but that's not a ball breaker really, just an embugerance.
I had a rough time getting started with VS Code & Python. Finally got things setup to where I’m pretty happy with it.
Why not?
In VSCode debugging is launched with <F5>. Doesn't get much easier.Yes, but don't you have to configure it to start AutoCAD?
EDIT:
And stopped with Shift+<F5>
I dont know what `manual configuration` you are talking about. You can just open VSCode, start a new file, save that file as a lisp, then hit <F5> to start debugging. What configuration do you do?
...>%So that means you do not "NEED" the JSON files.
Note: Previously, the AutoCAD Debug Attach and AutoCAD Debug Launch configurations were defined and stored in a launch.json file contained within the working folder.
Slow down! You're not reading.
If you are reading, then what was all the complaining about JSON files about? ...honestly, never mind.
I'm sure Notepad++ will work just fine for you. I hear good things about it. I think I remember there was an AutoLisp syntax file posted here (by MP) but you'd have to search for it. Good luck.
If vsCode plugin had a 'evaluateSelection' option I'd probably never open VLIDE :-)
Thanks for the tip.
@EnM4st3r
Thanks for that information,
I'll have another look :-)
Regards,
I have serious doubts, but I hope VSCode will force AutoLispers to use more or better documentation habits in their code.Good reminder.
For example to get the hover tips on a custom function you have to add a function header which looks like this:Code - Auto/Visual Lisp: [Select]
Backtrace:
[0.47] (VL-BT)
[1.43] (#<SUBR @00000158a9fa6278 -lambda-> "divide by zero")
[2.39] (_call-err-hook #<SUBR @00000158a9fa6278 -lambda-> "divide by zero")
[3.33] (sys-error "divide by zero")
:ERROR-BREAK.28 nil
[4.25] (/ 2 0)
[5.19] (C:BUG)
[6.15] (#<SUBR @00000158a9fa6548 -rts_top->)
[7.12] (#<SUBR @00000158b0659750 veval-str-body> "(C:BUG)" T #<FILE internal>)
:CALLBACK-ENTRY.6 (:CALLBACK-ENTRY)
:ARQ-SUBR-CALLBACK.3 (nil 0)I have serious doubts, but I hope VSCode will force AutoLispers to use more or better documentation habits in their code.I can't seem to get any hover tips working for autolisp in VSCode.
For example to get the hover tips on a custom function you have to add a function header which looks like this:Code - Auto/Visual Lisp: [Select]
I can't seem to get any hover tips working for autolisp in VSCode.
Do you have a specific plugin that finds the function headers to display them as a tip?
Name: AutoCAD AutoLISP Extension
Id: Autodesk.autolispext
Description: This is a vscode extension for AutoCAD AutoLISP
Version: 1.6.2
Publisher: Autodesk
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=Autodesk.autolispext
If debugging is your only problem, you can use `vl-bt` to debug instead of using VLIDE:Expanding on that concept.
... >%
How did you get the panel added to the rt+clk menu? Mine doesn't have it.
If vsCode plugin had a 'evaluateSelection' option I'd probably never open VLIDE :)
isnt that standart built in? Look attachment
Also i really like the 'Rename Symbol' option, the IntelliCode and similar to what BIGAL said the colored Brackets
Did you install the extension to VSCode?I figured it out. You have to have a debug session running, i.e. F5. This is counterintuitive, as I just wanted to load the selected lisp, not the whole form, which F5 does.
File -> Preferences -> Extensions ---> Search for "AutoLisp"
Load the: "AutoCAD AutoLISP Extension"
Did you install the extension to VSCode?I figured it out. You have to have a debug session running, i.e. F5. This is counterintuitive, as I just wanted to load the selected lisp, not the whole form, which F5 does.
File -> Preferences -> Extensions ---> Search for "AutoLisp"
Load the: "AutoCAD AutoLISP Extension"
I can't seem to get any hover tips working for autolisp in VSCode.I'm not getting the inline comment to work either. The hover tip says <undocumented>
Do you have a specific plugin that finds the function headers to display them as a tip?
I guess, if we were coding this connection we would have made: "attach", "load", and "connect" but...*meh*Yes, I try to comment all my code. I got started when I found out about C#'s xml export of comments. Now, I'm trying to implement the lisp comment you showed, but can't find any documentation on the format. All I can find is the use of ;;;. I found some mention of ;/ /; but not how to format it for VS comments.
"Not documented" is the mantra for most Windows developers. Here's a spotlight, do you have documentation/comments for/in your code?! :) :p
But seriously, if you take a look at some good coders, they typically have the good habit of documenting their code.
Try double-clicking a function name, then right-click and choose "Generate Documentation"Aha! I did that and it used a vertical pipe, not a forward slash as shown in your example. At least that's what it looks like in the code window.
Oh?! VSCode has folds too!It works on all functions automatically too. Just hover to the left.
Check the gutter and you get a collapse feature. But it looks like it will also hide any breakpoints collapsed in the region though (Come on MS, give me a symbol in the gutter that there is a hidden breakpoint in the collapsed region!).
BTW, my files will start to look like this now.
>>>> snip
"Counterintuitive" was probably not the right word. It's just that it was not documented I guess and up to you to figure it out. Yeah it's too bad that you can't just attach to acad without loading all the code in your lisp file. If you have a bug in it, you might want to test a piece at a time.
If debugging is your only problem, you can use `vl-bt` to debug instead of using VLIDE:
Define a simple error handler with:Code - Auto/Visual Lisp: [Select]orCode - Auto/Visual Lisp: [Select]Create your code:Code - Auto/Visual Lisp: [Select]debug your code on the command line.
Code: [Select]Backtrace:
[0.47] (VL-BT)
[1.43] (#<SUBR @00000158a9fa6278 -lambda-> "divide by zero")
[2.39] (_call-err-hook #<SUBR @00000158a9fa6278 -lambda-> "divide by zero")
[3.33] (sys-error "divide by zero")
:ERROR-BREAK.28 nil
[4.25] (/ 2 0)
[5.19] (C:BUG)
[6.15] (#<SUBR @00000158a9fa6548 -rts_top->)
[7.12] (#<SUBR @00000158b0659750 veval-str-body> "(C:BUG)" T #<FILE internal>)
:CALLBACK-ENTRY.6 (:CALLBACK-ENTRY)
:ARQ-SUBR-CALLBACK.3 (nil 0)
After your bugs are dead (-i.e. switch to production code), just (setq *error* nil) and/or replace/use your standard error handler.
I found an issue request on Github. This is a known problem since 2021. I posted a reminder that it's still broken and it was acknowledged. So maybe it will be available in a future release."Counterintuitive" was probably not the right word. It's just that it was not documented I guess and up to you to figure it out. Yeah it's too bad that you can't just attach to acad without loading all the code in your lisp file. If you have a bug in it, you might want to test a piece at a time.
For what it's worth I found the documentation to be lacking as well. I was able to get acquainted with Visual Studio (the "big" more complex code editor) quicker than VS Code (for C# programming). That was probably one of the biggest factors in forming my conclusion: VS Code is supposed to be quick, light and easy.