Skip to main content
1-Visitor
September 13, 2011
Question

Commandments of ProE- 2nd attempt

  • September 13, 2011
  • 16 replies
  • 5518 views
Looks like this went out empty the first time. Second try.

Hi all,

I remember a while ago someone posting something called the commandments of ProE (or something like that), but it had the word commandments in it.
It was basically a best practices document which I recall as being pretty good. Each line started with thou shall (or shall not). I only say that in case it rings a bell for anyone.
I'm working on a best practices document for users at our company. Although I already have a wealth of info (much from this thread), I was curious as to weather or not anyone remembers that particular document, and if they happen to still have it.

Thanks,
Stefan

    16 replies

    1-Visitor
    September 14, 2011

    This one was on my wall for the longest time. *attached*

    In Reply to Stefan Mueller:


    Looks like this went out empty the first time. Second try.

    Hi all,

    I remember a while ago someone posting something called the commandments of ProE (or something like that), but it had the word commandments in it.
    It was basically a best practices document which I recall as being pretty good. Each line started with thou shall (or shall not). I only say that in case it rings a bell for anyone.
    I'm working on a best practices document for users at our company. Although I already have a wealth of info (much from this thread), I was curious as to weather or not anyone remembers that particular document, and if they happen to still have it.

    Thanks,
    Stefan

    2-Explorer
    September 14, 2011
    Brandon,



    Thanks for this - It has been years since I have seen it. And, while God's
    original list won't ever need a refresh, this one does.





    I grew up "religiously" adhering to this one, but now, with the Wildfires
    and likely Creo (haven't seen it yet),

    there ARE NO MISSING REFERENCE WARNINGS!



    This has rubbed me the wrong way since I discovered it. I can only guess
    that PTC thought it was burdensome for the new user to see warnings.
    Ignorance is bliss! (until you have to dissect someone else's model)



    -Nate


    21-Topaz II
    September 14, 2011
    Ignorance is bliss until that missing / alternate reference suddenly
    becomes invalid and the entire house of cards comes tumbling down.
    Maddening when it's a feature that is no way related to the area you're
    working on, but that the assumptions that Pro/E was using finally became
    too tenuous to solve and BAM, you're trying to fix a feature you had no
    idea was broken.



    Doug Schaefer
    2-Explorer
    September 14, 2011
    I never thought of this before - it's a long shot, but a wide audience might
    know something. Is there a config option to control "missing ref" warnings?


    15-Moonstone
    September 14, 2011
    I actually miss the old days when Pro would fail on missing references. They were usually a trivial fix if you caught it when it actually happened. Now you might be trying to track down what happened to a model that was actually changed some time ago. I know the other software vendors used to beat up Pro for this, but I liked it.

    Rob Reifsnyder
    Mechanical Design Engineer/ Pro/E Librarian
    L
    Mission Systems & Sensors (MS2)
    497 Electronics Parkway
    Liverpool, NY 13088
    EP5-Quad2, Cube 281
    1-Visitor
    September 14, 2011
    There's one in every crowd... You can turn on Modelcheck to check for failures on save/check-in/regeneration/etc... That way you're alerted earlier in the process. You can't cure another user ignoring their Modelcheck warnings, but a sys-admin can prevent check-in of the file if the model has errors. At least you limit the exposure.
    1-Visitor
    September 14, 2011
    I've learned to regenerate until I get a green light before saving
    everything; since I started that, I have had no surprises upon opening a
    model.



    efefefefefefef

    Applied Research Labs

    University of Texas at Austin

    Carol Fly

    Mechanical Designer

    (512) 835-3397

    Fax (512) 835-3259

    efefefefefefef

    _____
    1-Visitor
    September 14, 2011
    In Pro/E WildFire 5.0 I actually turned on the config.pro option:
    regen_failure_handling resolve_mode
    This forces WF 5.0 to use the old method of handling problems. Several co-workers have been burned by missing refs due to not properly handling these modeling errors with the new WF-5 way of handling failures, but I have been steady because I am FORCED to correct these issues now, before they go to manufacturing. No regrets.

    I also turned on the Simplified Rep option:
    new_wf5_simp_rep_ui no
    This forces the old selection paradigm, which makes more sense to me. Your mileage may vary.

    Bob Schwerdlin
    Design Engineer,
    Dukane Corp.
    2900 Dukane Dr.
    St. Charles, IL 60174
    630-797-4974 direct
    -


    1-Visitor
    September 15, 2011

    I personally like the new method of handling failures for a number of reasons.


    1. No more Click, click, click, click, click. Feature 1 done. Click, click, click, click, click. Feature2 done.Click, click, click, click, click. Feature3 done.Click, click, click, click, click. Feature4 done...etc...........................................................


    2. I can now see how much pain I have to look forward to. If I see 3 or 4 red features in the tree, I attack! If I see 50, well I take a rest room break, get a fresh coffee, sharpen my sword and then attack.


    3. Moving back and forth between my before failure model and my current model evaluating featuresis much faster.


    🐵

    1-Visitor
    September 16, 2011

    I also prefer the Red Feature and the lack of the Resolve Mode dialogs. I review all models before they are approved for final release, so I can make sure we have good models.


    "Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"