Just curious NE.COM

That's even funnier....heeheeahaha...

I guess they saw that it was better to distribute it with
autocad...or....they could be planning on getting us hooked and then selling
it later....

 

Ummm ... never mind.

 

You have to laugh, because I bet my pants, thats exactly what they're going
to do...just watch...

Remember the FREE Express Tools....not anymore....

 

I'm sorry but I really don't think peyote agrees with you.

 

I went down a _very_ similar path pc-write --> pedit --> textpad; just got
lucky sooner, I guess. PC-Write was awesome, for its time. Light, fast.
and customizable..

I feel the same way about TextPad, but I admit to using vlide once in a
while to watch variables and break points.

 

You sending smoke signals again?

 

Mike,
Yes, you are correct - was debug.exe (da), been so long.
My brain is fried anyway.
Thanks,
Bob

 

Yeah I hear ya, don't ask me how I remember that ...

Cheers,

M.

 

I think he was talking about this ??
http://xarch.tu-graz.ac.at/autocad/lsp_tools/visual-lisp.html

 

I like VLIDE but do wish it would color code the levels of parenthesis and
give reports similar to the way ALLY did in the DOS days.

 

[waving hand.wav]

I'll certainly second the high praise for Textpad's usefulness. I too never
touch VLIDE, except to make FAS and VLX files, and it's SUCH a huge pain.

There are a few apps that I've used almost on a daily basis since about 1995,
when I got my first real computer, and Textpad was one of them.

Matt

 

So it works ok for you now? I seem to recall it was not
behaving correctly for you on (some of) your system(s),
albeit quite a few years ago.

You know you can compile at the command line right?

(vlisp-compile 'st "foo.lsp" "yoo.fas")

Of course you do; I shad up.

 

I am one of the few who actually purchased the VLIDE editor for Acad14.

 

"One of the few".

Did only a few people buy it? That would surprise me. Every
serious autocad programmer I know bought a copy. It was quite
the buz iirc. Of course, most of them already had Vital LISP
ver 3, so for many, it was annoying to "upgrade" solely for
the benefit of renamed functions, though at about 1/3 of the
original price, it wasn't all THAT painful; but I digreess.

Anyway, I'm guessing, that those who did buy said product bought
it for the compiler, not the editor.

Like me for instance

 

Yep, those problems fixed themselves a while ago. I don't know the source of the
problem, but one day it was gone. Maybe it was because of an upgrade...

Well, yeah, I've read about that, but I don't usually do it for some reason. I
could create a simple "compileall" command that will create the FAS files I
recompile on a daily basis. But I would have to have the VLIDE open anyway, and
my main source files are contained in a few projects that will compile all of
them in one fell swoop.

Here's a realy stupid question: Is there a way to rebuild VLX applications
(prv's) through VLisp? That's what kills me, is having to pick off the many PRV
projects to make the VLXs.

Matt

 

I don't know. If I weren't busy I'd look into this as it's an
interesting question / challenge.

In the interim, if you wish, have a look at these functions:

vlisp-compile
vlisp-compile-list
vlisp-dclres-list
vlisp-dclres-load-dialog
vlisp-drop-project
vlisp-export-symbol
vlisp-fasres-list
vlisp-fasres-load
vlisp-find-project
vlisp-import-exsubrs
vlisp-import-symbol
vlisp-inires-list
vlisp-list-loaded-projects
vlisp-load-project ;; *** hello ***
vlisp-make-file-fas
vlisp-make-project-fas ;; *** hello ***
vlisp-make-project-load-file
vlisp-project-fas-list
vlisp-read-file-xdv-list
vlisp-read-project-xdv-list

Cheers.

I'm busy

 

For my 'master.vlx', which contains all my 'tool box'
funtions. I wrote a lisp to read each of the .lsp files
in certain folders and write the contents of each into
one .lsp file. Then all I have to do is recompile the
one .lsp file and I am done. Not real super speedy
but it is better than nothing.

 

Though I didn't use ALLY for its color-coding, (it just distracted me), I
liked the reporting. TextPad has parenthesis matching, which accomplishes
the same thing without going day-glo on me.

Once you add (vl-load-com) and start using the cool vl-,vlax-, and vlr- fns,
you're pretty much driven to vlide for debugging, since the old vanilla lisp
debugging method of "dump of everything to the text screen starting at the
point of error" is gone. But it's clunky compared with TextPad so I edit
with one and debug with the other.

 

In the early 90's I used a program called wcedit that had color matching for parenthesis. Anybody got something for color matching parenthesis? I took a look at TextPad but can't get colors to work.

 

As always, thanks again, Michael.

This list of undocumented functions (in A2K) prompted to create a symbol name
filtering function to search out and all symbols which may come alive without my
knowledge. Very handy for tracking down errant non-local variables, but it's
REALLY handy for finding hidden gems in all of the various VLisp programs flying
around. I just need to track down the documentation for some of these.

FWIW, I found that the VLISP functions are (for the most part) not defined until
you load the VLIDE, and they are propegated across all current and future
namespaces in the same AutoCAD session.

But, of course you (and probably everyone else here) knew that already

My next step is to see if it's possible to load these functions up without
having to involve the VLIDE.

Matt