Script or macro capability with the UI.

vhubbard · 2007-11-05 22:29:43

We want to be able to capture a series of UI commands in a script or macro and be able to execute them. Similar to how Word or Excell macros work.

Store the definitions in the .vcproject file.

This would allow us to set up a few "macros" commands to allow us to quickly change the settings in Vericut for:

1. Quick processing,
2. More accurate processing with collision check.
3. Precision processing.
4. Document/picture creation.
5. Avi creation.

Currently changing Vericut for these tasks takes many UI commands under many Icons or menus. Allowing us to script a macro would make it so we could configure Vericut quickly for the various modes.

stpendl · 2007-11-06 07:02:00

Did you already try to create separate VCproject files for those situations ?

vhubbard · 2007-11-06 13:50:21

We have about 30+ machine variations, that is 30+ .vcproject files now. Multiply it by 4 or more for all the setup variations. It becomes 120+ .vcproject files to maintain, integrate into startup utilities and train everyone how to use them. Too complex for the majority of people to use or for us to maintain with time and resources available.

Macros, mapkeys etc are used by many software packages to add automation to software for common tasks. Seems like something Vericut should have to be up to date.

DaveF · 2007-11-06 19:28:44

This Idea has a lot of Merit

I used the be the king of batch, many moon ago. version 2, I guess that was 1992?, where multiple views of a part with different zooms were required to check the part. Accuracy was view dependent back then.

I use a UNIX command called SED, a stream editor, to automatically create adduser files with the names of the files I saved using autosave. I would que up Vericut to run overnight , and over weekend.

Each program run created an IP, IMG, and SS (shapshot)

But each part had a adduser for each program, times each view
so 8 programs, and 6 views is .. 48 adduser files

So Yes, there are lots of tools with the Vericut we have today, BUT, Macro functionality is a great idea.
8)

Spanky · 2007-12-15 13:59:53

Has anything come out of this discussion?

There are some tasks (okay, I only have one example for now) in VERICUT that can not currently be stored in a project file. For example, turning on the Min. Cutter Extension calculation is not stored in the project file and takes 5 button clicks to activate. This would be a good candidate for a mapkey.

VERICUT Users' Forum

#1 2007-11-05 22:29:43

Script or macro capability with the UI.

#2 2007-11-06 07:02:00

Re: Script or macro capability with the UI.

#3 2007-11-06 13:50:21

Re: Script or macro capability with the UI.

#4 2007-11-06 19:28:44

Re: Script or macro capability with the UI.

#5 2007-12-15 13:59:53

Re: Script or macro capability with the UI.

Board footer