Fórum Cadtutor

I added a note in the file where to change to keep PowerShell open. ; ---------------------------------------------------------- ; Wait until PowerShell finishes. ; ---------------------------------------------------------- (vlax-invoke-method shell "Run" cmd 0 ; <=== Change 0 to 1 if you want PowerShell to stay open. :vlax-true ) (vlax-release-object shell) ) ) I was running some tests at work to see if there was a method to determine if PowerShell was blocked to give a message... (princ "\nPowerShell access is blocked.") (princ "\nPowerShell access is allowed.")) Right now all I get on the commandline is... error: Automation Error. Description was not provided. Though I had to get to some of my "paid to do" work done yesterday. This is probably above my pay grade. I just realized who the OP is, a big time Guru over at Autodesk forums and AUGI.

I've actually used the attached lisp function BurstAttrBlock to run through a bunch of dwgs looking for a specific (non dynamic) block with attributes to convert them to text using accoreconsole. BurstAttrBlock.lsp

@GLAVCVS thanks for the feedback. I assume to use a single Powershell session you would have to run a batch file that launches Powershell first before starting autocad? Then when autocad closes or crashes out that session of Powershell also closes.

Yes: as SLW20 says, it seems to work well. On the other hand: Have you considered having the script written only if it does not already exist in the expected directory, and keeping PowerShell running from the initial load? This would make the dialog box load faster on subsequent calls. In this regard, the script check/creation could be done when the code is loaded. This would also improve the speed of the first execution slightly.

Have you ever received a drawing where a block contains attribute text. You need to edit the text as normal objects?of exploding the block with EXPLODE and losing the attribute values BURST can be useful. BURST breaks the block into objects while preserving the attribute values as text. For example if you have a title block or equipment tag with attributes and need to make edits BURST can save some extra work. Just remember that after bursting the result is no longer a block. Do you use BURST, for attribute blocks. Do you normally handle them another way?

I think AI is definitely part of the reason, but probably not the whole story. A lot of questions that used to become forum threads can now be answered quickly with ChatGPT or Copilot, especially when the problem is a small piece of code or a common error. The interesting part is exactly what you mentioned: when the AI-generated solution fails, people still need somewhere to ask a human who understands the bigger context. AI can produce working-looking code very quickly, but debugging someone else's real project is a different problem. I also think newer users are less attached to forums than they used to be. Many will try a search, ask an AI, or post in a Discord/Reddit community before they ever find a specialist forum. So the drop in posts doesn't necessarily mean people have stopped needing help; the questions may simply be going elsewhere.

I'll probably do more tweaking, that's the 2nd version, I might go back to the first version.

Yes you can have custom buttons Ok_Cancel_Width. Have to go back to my R12 paper manual for details.

Nice job on the vector images. Like the highlite option.

@BIGALOr another option would be to provide a button to click on so that the selected item on the list box will open up into another dcl written on the fly with an Edit Box having a set edit_width attribute greater than the length of the selected item.

@Paul Li another way may be to check the strlen of the selected item in the list and do a child dcl that has correct width press Ok to keep else Cancel and go back to list.

@SLW210 Your revised version works beautifully and can now support older versions of AutoCAD...thanks a bunch!!!