Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X
I know Pro/E keeps track of interdependencies it doesn't make any sense
that I can't save something that doesn't have a Parent/Child relation to
the manikin.
Hi folks
When I first saw the Manikin functionality, I realised it would have no benefit to our general users, so removed it from our installer files and deleted Manikin from our menus via config.win... so we've gladly avoided these issues, though there are several other Wildfire 4 "bugs" that we're still not happy with, mainly the inadvertent(?) removal of Wildfire 3 drawing functionality.
I agree with Doug, PTC seems to be getting sloppy lately in software quality and tech support... and our maintenance payments are not justified in my humble opinion, following a number of issues, calls, SPRs, contacts direct with PTC.
Regards
Edwin Muirhead
CAD Manager, Weatherford
In Reply to Doug Schaefer:
<rant alert=">
The clarity of the message isn't the issue, it's clear enough (at least
your version is, Chris' is less so), it's that this functionality was
approved at all. I'm certain that this was the easy way to implement a
no-save version of Manikin, but at what cost? You've already cost one
customer lost time and productivity because of this decision. Whose
ease of use is more important, your programmers' or your customer's?
This is yet another example of UI and functionality decisions made in
Pro|E that defy logic. In what universe does having a change to item A
necessarily prevent the save of unrelated items B, C, D, E, F, G, H, I
and J? If Microsoft changed Word so that inserting an image in a
document prevented the save of any and all other documents open if the
user hadn't purchased the full version of the 'insert image' module,
we'd ridicule them until the end of time, and rightfully so. Regardless
of the message's clarity, some (many?) will still assume that it only
applies to the assembly in question, since that's logical, and not to
unrelated objects.
I'm being hard on PTC here, but I've been a fan and supporter for years
but I'm getting sick of decisions like this that are hostile to your
customers. The UI continues to show a lack of attention to detail and a
lack of understanding of user's workflow. To top it off, maintenance
costs are high while return for that dollar is low (tech support is
frequently painful, releases only come every other year instead of 2 per
year like it used to be).
You are free to make your own product decisions and I understand the
idea of providing a tease of the Manikin functionality, but if that
tease costs me money and lost work, when I had no reasonable expectation
that it would (even if I was warned), I'll never sample again and I'll
certainly not consider buying.
Now I have to educate my users on the proper way to use Manikin to avoid
loosing work. Probably easier and less risky to simply disable it, if
that's possible.
Doug Schaefer
Has PTC come up with a way to shut off this Pro/Manikin in Wildfire 4.0? Unless you have bought the license it is completely worthless. It puts a menu at the top and another button in assembly mode. It makes a distraction for the users and disables their ability to save.
I’m not sure what advantage this gives Pro/E over the competition. Maybe we should call it “Pro/ManCan’tSave”? This like buying a car with no headlights and when you flip the headlight switch the engine shuts off because you didn’t get the “headlight option.”
Dave Engel