Survey, Do you want to add menus to the File Menu tree? Creo 1.0

[davehaigh]

This is something I've been complaining to PTC about since the beta release of Creo. I seem to be getting nowhere with this complaint, so I thought I'd ask the community if this is something you want.

Creo, doesn't let you add commands to the file menu. I want the ability to add mode independent commands to the file menu. One example is adding to the File, Print menu. But I would like to add to the File, New menu also.

[cid:image001.jpg@01CD0841.8A0D0D20]

Is this something you would like to do?

David Haigh
Phone: 925-424-3931
Fax: 925-423-7496
Lawrence Livermore National Lab
7000 East Ave, L-362
Livermore, CA 94550


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[bfrandsen]

For the Quick Access Toolbar it should be possible define that a command is available in all modes.
I added Erase Not Displayed there and had to open files in each and every possible mode to have it available everywhere.
But it has to be a choice as not all commands are valid in all modes. When that is available it will open up for the modeless File menu as well.

/Bjarne

[dgschaefer]

Yes, that would be very handy for all our print / plot mapkeys.



Doug Schaefer

[DarrinHiebert]

While I WOULD like to have this as well, I think at this moment, my bigger
issue/concern is how we keep/maintain a "corporate" config.(win) file in
Creo.



We have a LOT of custom icons that we must have in a menu somewhere.
These custom icons do a myriad of things like start parts, create output
files, and the list goes on. When we add icons to our current config.win,
it is automatically copied around to everyone the next time that they
start Pro. This is something that we still have to be able to do as we
move forward.



The problem I've seen is that the current .ui settings are buried in a
directory structure that we do NOT have access to. I can't even go to the
directory to see the file, let alone copy it out, and then copy it to
others. These files are stored in the /application/.. directory, and that
is a protected directory (at least here).

[cfly]

For that matter, I'd like to see the line font scales on the screen to match
those of the prints! They dropped that in WF 1.0 and I just went to a CREO
demonstration yesterday and was told that they still don't match. And I bet
they haven't fixed the snap function that broke with WF 1.0, either - such
small things that have been going on for ages, that irritate the (*^#$ out
of me.



One of the things the presenter said yesterday was that CREO 2 is planned to
be the least buggy of all of PTC's releases; my reply was, "So, we'll see it
in 5 years, maybe?" He said they can't put out a release and just say
they've fixed things, without adding anything new, and all I could think
about were the resounding HALLELUJIAs they'd hear from their long-term user
base if they did do that.



efefefefefefef

Applied Research Labs

University of Texas at Austin

Carol Fly

Mechanical Designer

(512) 835-3397

Fax (512) 835-3259

efefefefefefef

_____

[dgschaefer]

Yep, and there's no way to store your person .ui file anywhere else,
unless you want to put in your working directory. Since that changes
every day, that means you get .ui files all over the place.



We store our config files (*.pro, *.sup, *.win) on the server so
whatever workstation we log into (at my desk, in a conference room, on a
shared laptop while away) we have our own personal configs. No way to
accomplish that with Creo 1.0+.



Doug Schaefer

[DarrinHiebert]

OK. I'll bite.



Is there ANYONE out there that has a moderate installation of let's say
more than (5) users that does NOT have some sort of a "corporate" config
system that they want everyone to use?



We have 25 users here. Why would we want to let 25 users create their own
icons and mapkeys to drive things like start parts? Releasing parts?
Creating DXF files? Some of our mapkeys are PROCESSES for
crying-out-loud!, and we DEMAND that everyone do it the same way. By
having a corporate config system, consisting of how ever many files that
needs to be, we can easily control this.



What part of this is not just a HUGE oversight on PTC's part??? Am I
missing something???

[davehaigh]

The .ui file does not get read from the working directory. By the way there is no config.win in Creo 1.0.
(even though the help files talk about the config.win and the menu_def.pro it's not valid in Creo 1.0. I pointed that out to PTC this week.)

Your personal .ui file is stored in the cache folder.
Since my startup script is setting my cache folder to a non-standard location like this:
set PTC_WF_ROOT=%USERPROFILE%\pro\creo_1_home\PDMLink_Cache\PTC\ProENGINEER

My personal .ui is stored here:
%USERPROFILE%\pro\creo_1_home\PDMLink_Cache\PTC\ProENGINEER\.Settings\creo_parametric_customization.ui
If you want to be dictatorial, your startup script could copy a cooperate .ui to that location before starting Creo.

You can rename the .ui and place it in the loadpoint common files directory. For me that's here:
C:\ptc\Creo 1.0\Common Files\M030\text\creo_parametric_admin_customization.ui

Here's the information I got from PTC on how to merge two .ui files.

Title: How to merge a creo_parametric_customization.ui and a creo_parametric_admin_customization.ui into a single *.ui using Creo 1.0

Description :How to merge a creo_parametric_customization.ui and a creo_parametric_admin_customization.ui into a single *.ui Applies To Creo 1.0

* Ribbon customization is automatically save to D:\Users\<user>\AppData\Roaming\PTC\ProENGINEER\Wildfire\.wf\.Settings\creo_parametric_customization.ui
Resolution

* Automatically load D:\Users\<user>\AppData\Roaming\PTC\ProENGINEER\Wildfire\.wf\.Settings\creo_parametric_customization.ui at startup
* Manually load creo_parametric_admin_customization.ui from any location
* Move and rename D:\Users\<user>\AppData\Roaming\PTC\ProENGINEER\Wildfire\.wf\.Settings\creo_parametric_customization.ui to C:\Program Files\PTC\Creo 1.0\Common Files\M020\text\creo_parametric_admin_customization.ui


David Haigh

[DarrinHiebert]

From David:



The .ui file does not get read from the working directory. By the way
there is no config.win in Creo 1.0.

(even though the help files talk about the config.win and the menu_def.pro
it's not valid in Creo 1.0. I pointed that out to PTC this week.)





My experience (just 15 minutes worth), indicates that the .ui file IS read
from the startup directory, or at least the way that we are starting ours.




You are right though, that if you copy it in there, it becomes a
dictatorial type administration. Which works for some and doesn't work
for others.

[emanuelms]

Hi everyone.

Even copying our creo_parametric_customization.ui from one machine to other, it won't fully work. One thing I notice that's for exemple is that our custom "icons" will be lost. all our custom buttons will appear with the funny yelow smile on the new machine...

In Reply to David Haigh:

The .ui file does not get read from the working directory. By the way there is no config.win in Creo 1.0.
(even though the help files talk about the config.win and the menu_def.pro it's not valid in Creo 1.0. I pointed that out to PTC this week.)

Your personal .ui file is stored in the cache folder.
Since my startup script is setting my cache folder to a non-standard location like this:
set PTC_WF_ROOT=%USERPROFILE%\pro\creo_1_home\PDMLink_Cache\PTC\ProENGINEER

My personal .ui is stored here:
%USERPROFILE%\pro\creo_1_home\PDMLink_Cache\PTC\ProENGINEER\.Settings\creo_parametric_customization.ui
If you want to be dictatorial, your startup script could copy a cooperate .ui to that location before starting Creo.

You can rename the .ui and place it in the loadpoint common files directory. For me that's here:
C:\ptc\Creo 1.0\Common Files\M030\text\creo_parametric_admin_customization.ui

Here's the information I got from PTC on how to merge two .ui files.

Title: How to merge a creo_parametric_customization.ui and a creo_parametric_admin_customization.ui into a single *.ui using Creo 1.0

Description :How to merge a creo_parametric_customization.ui and a creo_parametric_admin_customization.ui into a single *.ui Applies To Creo 1.0

* Ribbon customization is automatically save to D:\Users\<user>\AppData\Roaming\PTC\ProENGINEER\Wildfire\.wf\.Settings\creo_parametric_customization.ui
Resolution

* Automatically load D:\Users\<user>\AppData\Roaming\PTC\ProENGINEER\Wildfire\.wf\.Settings\creo_parametric_customization.ui at startup
* Manually load creo_parametric_admin_customization.ui from any location
* Move and rename D:\Users\<user>\AppData\Roaming\PTC\ProENGINEER\Wildfire\.wf\.Settings\creo_parametric_customization.ui to C:\Program Files\PTC\Creo 1.0\Common Files\M020\text\creo_parametric_admin_customization.ui


David Haigh

[davehaigh]

I just did some testing.

Here's the deal. If you have the config option load_ui_customization_run_dir yes Creo will read the .ui from the start in directory.
The default behavior is for it to read it from the local cache .settings folder, and not see a .ui in the start in dir.

However, if you don't have a .ui in the start in directory, Creo still reads the .ui from the local cache .settings folder.

I haven't tested this, but I believe it reads .ui's in this order:

1. <loadpoint version=">\text dir

2. <local cache=">\.settings dir

3. Start in dir <-- if the config option is set

Can anyone confirm this?

David Haigh

[JonathanHodgson]

"And I bet they haven't fixed the snap function that broke with WF 1.0,
either - such small things that have been going on for ages, that
irritate the (*^#$ out of me."



I've got a thread running on Planet PTC about small changes that would
make a big difference:


they might be doing something about it soon.



Regards,

Jonathan