C/R character for ATTSYNC

[bababarghi]

Hi all,

 

I am using Wscript to run a script on bunch of files.

 

(Again, wonderful application Lee. I use it a lot )

 

I need to add a C/R character at the of my block name in ATTSYNC command. The SPACE does not work simply because it would be considered as part of block name (ATTSYNC needs a hard c/r keystroke at the end of the block name) and I can't use c/r on the other hand because wscript is a single line mode application.

 

 

I also tried "" around the block name and (Command "") but they were both failure attempts.

 

I was wondering if there is any work around tip for my issue ...

[bababarghi]

Just for those who may have same issue later on, the solution I found was another freeware by cadig called AutoScript. Unlike ScripPro, it is a 64bit application

 

 

Using AutoScript, you do not have the 'single-line code' limitation.

 

Additionally, if you want to spend some money on more fancy tools, here is another one:

http://www.cadfx.com/batchscr/

[Tuns]

Maybe put the block name in quotes? I've never used that program before so I'm assuming the script is written like a normal one.

[dbroada]

I use a semi colon on Tool palettes, would they work here?

[Tyke]

Just for those who may have same issue later on, the solution I found was ...

 

Can you post the (part of) script file produced so we can all see how the problem was solved. Or is the script run from within AutoScript?

[bababarghi]

Maybe put the block name in quotes? I've never used that program before so I'm assuming the script is written like a normal one.

 

I also tried "" around the block name and (Command "") but they were both failure attempts.

 

I think AttSync specifically looks for c/r character as an indication to recognize block name. Anything before c/r will be interpreted as part of the block name. I have not tried '' though.

 

---

 

I use a semi colon on Tool palettes, would they work here?

 

No chance.

---

 

Can you post the (part of) script file produced so we can all see how the problem was solved. Or is the script run from within AutoScript?

 

There is no rocket science behind the script per se. It is more changing the question rather than solving it. You install AutoScript and then, in AutoCAD command line, type AutoScript. The rest is purely like ScriptPro from Autodesk.