VERICUT Users' Forum

DaveF

Senior Member

From: Valencia, CA

Registered: 2005-08-20

Posts: 304

TIP: A way to blank components without changing mch file

TIP: A way to change component visibility without changing mch file

I found programmers were saving machines only because they wanted to blank components. They have a valid reason because the components like base, and X, were in not in danger of ever colliding.

I got around the need to change the .mch file, by using sub-programs
I also needed to define words and have the words call the MACRO "SetComponentVisibility"

I gave each programmer a unique sub-programs by name
For example my file is called DAVE_F_PREFS (1st name_last initial)

The sub-programs looks like this

O0102
N1 VERICUT_BLANK_BASE
N2 VERICUT_BLANK_X
N3 VERICUT_BLANK_Z
N9 VERICUT_BLANK_SPECIAL_ATTACH_PLATES_LOWER
N10 VERICUT_BLANK_SPECIAL_ATTACH_PLATES_UPPER
N12 VERICUT_BLANK_MIRRORED_X_WAY_COVER
M99

they can edit, add delete components as they like

This is the regisers

    WORD_VALUE "VERICUT_BLANK_X" {
        MACRO "SetComponentVisibility" {
            OVERRIDE_VALUE 0 TEXT_OVERRIDE_VALUE "X"
        }
    }
    WORD_VALUE "VERICUT_BLANK_Y" {
        MACRO "SetComponentVisibility" {
            OVERRIDE_VALUE 0 TEXT_OVERRIDE_VALUE "Y"
        }
    }
    WORD_VALUE "VERICUT_BLANK_Z" {
        MACRO "SetComponentVisibility" {
            OVERRIDE_VALUE 0 TEXT_OVERRIDE_VALUE "Z"
        }
    }
    WORD_VALUE "VERICUT_BLANK_A" {
        MACRO "SetComponentVisibility" {
            OVERRIDE_VALUE 0 TEXT_OVERRIDE_VALUE "A"
        }
    }
    WORD_VALUE "VERICUT_BLANK_B" {
        MACRO "SetComponentVisibility" {
            OVERRIDE_VALUE 0 TEXT_OVERRIDE_VALUE "B"
        }
    }
    WORD_VALUE "VERICUT_BLANK_BASE" {
        MACRO "SetComponentVisibility" {
            OVERRIDE_VALUE 0 TEXT_OVERRIDE_VALUE "BASE"
        }
    }
    WORD_VALUE "VERICUT_BLANK_MIRRORED_X_WAY_COVER" {
        MACRO "SetComponentVisibility" {
            OVERRIDE_VALUE 0 TEXT_OVERRIDE_VALUE "MIRRORED_X_WAY_COVER"
        }
    }
    WORD_VALUE "VERICUT_BLANK_HEAD_CHANGER_TABLE" {
        MACRO "SetComponentVisibility" {
            OVERRIDE_VALUE 0 TEXT_OVERRIDE_VALUE "HEAD_HOLDER_TABLE"
        }
    }

Yes, I could have also used CGTECH_MACRO

:oops:

But I am a control rookie, (2005) and wanted to walk before I run, and also try different things.

:twisted:

---

Dave Frank
Aerospace Dynamics International, PCC
Valencia Ca
"Where else can you have this much fun,.......and get paid???."

tri

Member

From: MA

Registered: 2005-11-28

Posts: 17

Re: TIP: A way to blank components without changing mch file

hey dave,

there's a better way which you don't need to define all the macro::
such as ::: Vericut_blank_x, Vericut_blank_base, and so on...

Define one macro named
Vericut_bank   typed: macro     alpha-numeric

In word address
WORD_VALUE "Vericut_blank" {
MACRO "SetComponentVisibility" {
OVERRIDE_VALUE 0
}

you can blank any component in the .mch file by

Vericut_blank x
Vericut_blank y
Vericut_blank base
and so on..........

So, what do you think?

DaveF

Senior Member

From: Valencia, CA

Registered: 2005-08-20

Posts: 304

Re: TIP: A way to blank components without changing mch file

That sounds good.

I will give it a shot the next time I need to dink with the machine.

dave

ps.

speaking of Mass., I have a cousin with a house, right on the bay, in provinectown.

That made for a lot of fun growing up.
Yes, I'm from New Jersey, and I used to work in a chemical plant

---

Dave Frank
Aerospace Dynamics International, PCC
Valencia Ca
"Where else can you have this much fun,.......and get paid???."