But, they are constantly getting tripped up by all of the extra garbage that gets thrown into the macro. I work with a couple of guys that are trying to write their own macros and I encourage them to use the macro recorder to try and learn some of the basic commands. The recorded macro ends up getting so long, and so filled with useless lines of code, it becomes nearly impossible for new macro writers to discern between what is needed and what is garbage.Īgain, this is not a pressing issue. Now imagine someone recording a macro with multiple commands. This is about as simple as a macro command can get and powermill produces a macro with twice the number of lines of code necessary. If I right click the toolpath and left click activate, powermill records the right click and the left click and produces something like this:ĮXPLORER SELECT Toolpath "Toolpath\CHAMFER" NEW For example, lets say i want to activate a toolpath. mac file is saved.Įvery mouse click gets recorded currently and you end up with a lot of useless lines of code. I am simply suggesting that the macro produced by the macro recorder gets "cleaned up" before the. I am not suggesting that Autodesk remove any functionality from the macro recorder.
0 Comments
Leave a Reply. |