|
should i learn the api?
ok, i basically use sw to re-create parts/assemblies that customers send drawings for, to machine in our shop. every now and then i have to design something.. my question is, should i learn the api? if i learned it, what could i do with it to make my day to day operations run smoother?
any examples from ppl that are in the same boat that i'm in, as far as what they use to make life easier?
thanks
sw2009 sp3.0
pentium d 840-3.2 ghz
4gb ddr2 667
ati firegl v5600 - driver ver. 8.440.0.0
winxp pro 32bit
an understanding that without any understanding, we would all be misunderstood..
it all depends on the fine details of what you do; the api is there to overcome monotony as a rule. anything that is repeatably similar can be automated through api. on top of that however you have many other useful functions for it.
by the sounds of things though everything you will be doing is going to be a new job and possibly totally different, so it depends.
do you find yourself doing any task over and over that has similarities such as settings custom properties, saving finished drawings to dxf, checking procedures etc...?
if you have a love of programming then go ahead. it isn't trivial though.
i will suggest to to try few basic vb stuff before actually getting into sw macros. i ad a lot of trouble fixing errors. even i'm looking to get some vb classes or may purchase some books and study them.
deepak gupta
sw2007 sp5.0
sw2009 sp2.1
if you need help with the language, debugging, or quirks you can try
we have people that specialize in vba as well. they're volanteer run forums.
~t
quick |
|