cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

config.sup vs .pro

SOLVED
Highlighted
Regular Member

config.sup vs .pro

Alright so I am having some problems with my Mapkeys. I have recently inherited the role of ProE Admin and I have been working with Mapkeys on it for quite some time now. I thought I had them all nailed down and then ran in to a small issue.

 

I used to have all my mapkeys in the config.pro and it was working great. Well then someone decided to include mapkeys with the same name in their config.win and so it would over ride mine. Then they call and say the mapkeys aren't working right and its just getting old.

 

What I am trying to do is create a config.sup with some of the mapkeys that are company wide so that they don't get changed. Now the issue I am running into is when I take half the mapkeys out of the .pro and put them in the .sup... they are the only ones that will show when I start ProE. It's like it is completely ignoring anything that is in the config.pro now. If I remove the config.sup then all the mapkeys will show back up.

 

Can someone please help me with this issue? Any insight is much appreciated as I have limited knowledge about this.

 

On the attached picture the left box is without a config.sup.... The right box is with the attached config.sup

Tags (3)
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: config.sup vs .pro

Okay... here's the definitive answer I promised using the trail file technique. I have verified that this technique works and will consistently enforce your standard mapkeys EVEN when the user attempts to overwrite them.

1) Save your company mapkeys to a standalone file. Your current config.sup file (the one you originally posted for us) will do just fine. However, you should rename it to use the ".pro" suffix. You can call it config.pro, mapkeys.pro, or what-ever-you-want.pro.

2) Place your mapkeys file somewhere everyone can read it... but no one can modify it (except an admin or trusted user). You can make this a network drive or a local folder locked down so users can't modify the contents. This prevents users from messing with your mapkeys.

3) Start a fresh session of Creo Elements/Pro (Wildfire 5). Know in advance where your trail files are written. Once the session starts, do nothing except the following:

  • Go to Tools->Options and select the Browse icon.
  • Browse to the network drive (or local folder) containing your mapkey file (the one you named in step 1)
  • Load the file and select OK to exit the options tool.
  • Close Creo Elements/Pro (Wildfire 5).
  • Browse to the location where your trail files are stored.
  • Open the last trail file created and remove the last few lines (where you closed and exited the application). If you don't understand which lines closed the application, I'll explain this later.
  • Save the modified trail file as "my_trailfile.txt" (or another reasonable name... but keep the .txt suffix)
  • Move the modified trail file to the same location as your mapkey file (network drive or local folder)

4) Modify your Pro/ENGINEER startup command by appending the full path name of the trailfile from step 3. Most people launch Pro/E from the proe.exe command. If your trail file was called my_trailfile.txt and it was located on a mapped network drive (for instance the "M" drive), the modified launch command might look similar to this:

proe.exe M:\company_standards\configs\my_trailfile.txt

5) Relaunch Creo Elements/Pro and test. When the application launches, it should immediately run the trail file you specified. If you're running Windchill or Pro/INTRALINK 9.x+ you'll have to log in to your server before the trail file will run... but this is normal. If you're paying attention carefully, you'll see the options menu pop open and load the mapkey file.

If any user has already set ANY of the mapkeys in your company-wide mapkey file, they will be overwritten thus enforcing your company standards.

Of course, an industrious user could always make a mapkey that would RELOAD their own custom mapkey file AFTER the trail file runs... thus overwriting yours. But at some point the user has to take responsibility if they're going to go to such lengths to circumvent your standards.

This should completely resolve your problem. The toughest parts are editing the trail file and removing the useless parts without destroying the necessary commands. I've attached my own trail file to show you what it should look like.

A brief explaination of the trail file is below... click the image for a larger, more readable version.

trailfile_help.png

I hope this helps! if you get stuck, write back!!

Thanks!

-Brian

View solution in original post

21 REPLIES 21
Highlighted

Re: config.sup vs .pro

Hi Erik...

Hmm... I don't think I've ever tried adding mapkeys to the .sup before. I'll check it out and see if I can replicate the problem. I'm assuming you're using WF5, is this correct?

Thanks!

-Brian

Highlighted

Re: config.sup vs .pro

Yes we are on Wildfire 5 build M080.

I should have included that in my previous post. Thanks

Highlighted

Re: config.sup vs .pro

Wow Erik... I tried it on WF5 M130 (the latest) and that's the way it works.

It seems like an "error" but it's probably always been that way. Imagine that every keyword (or "token") in the config.pro and config.sup works the same way. If the token appears in the .sup, it's ignored in the .pro.

For example, if save_objects is set in the config.sup, it's completely ignored in the config.pro.

The "mapkey" keyword must be just like any other keyword. I guess I always just assumed it was somehow "special" but this proves it really isn't. I am certainly surprised but I guess I shouldn't be. This is always how the .sup has worked... perhaps I should have known better. Either way, I think this should be submitted as an enhancement request. I'll double check Creo 1.0 to see if it still works this way.

In the meantime, you still have a problem with users overwriting your mapkeys. I used to get around this by starting all my "company-wide" mapkeys with some oddball character like - or . but I see you've already tried this.

I do have an idea for you. I'm not 100% sure this will work and I usually don't post solutions without checking them first... but I'll make an exception. You can specify the name of a trail file to run when Pro/ENGINEER starts up. This is sometimes used in "batch mode" to execute commands without launching a graphical version of Pro/E. I believe you just append the trail file (full path) to the end of the Pro/E launch command. As soon as Pro/E loads, the trail file runs.

The idea would be to create a small trail file that loads your company's default config.pro or just the mapkeys saved off into a separate file. You could call it mapkey.pro or whatever. If this file were loaded LAST, it would override the users' config.pro settings. This would "undo" any changes they made... and they'd probably be perplexed at how you did it.

Like I said... I might be wrong but I think this will work. If I recall correctly, I used this technique to automatically overwrite some very annoying mapkeys one employer put in place. Of course, you can use it for the opposite purpose... to enforce company standard mapkeys and prevent users from overwriting them.

I hope that helped. Let me know if you have any troubles...

Thanks!

-Brian

Highlighted

Re: config.sup vs .pro

Tried it in Creo... didn't work.

Hopefully the trail file idea will give you some relief.

Highlighted

Re: config.sup vs .pro

I will give this a shot and let you know. It may be a couple days before I get it set up as they currently have a workaround so I need to address some other issues. Thanks you for the VERY FAST response!

Highlighted

Re: config.sup vs .pro

It might help if I knew what command you need to use to load a different config.pro. I have my startup pulling and reading the trail.txt file but I can't seem to get it to actually load the config.pro.

Sorry I have so many questions...

Highlighted

Re: config.sup vs .pro

Hi Erik...

No problem at all... you should simply be able to go into Tools->Options and load the file there. This action should be saved within your trail file.

Your message seems to indicate this isn't working for you. I seem to recall that I may have needed to DELETE the mapkey before reassigning it but I can't be sure. I have been trying to verify this all day but time has gotten away from me. I'll give it another shot tonight and get back to you with a more comprehensive answer.

Thanks!

-Brian

Highlighted

Re: config.sup vs .pro

What do get when you look at the config.sup only in the configuration options dialog? When I view your config.sup that way I see half of your map keys being marked as invalid (red circle with a slash through it).

Highlighted

Re: config.sup vs .pro

I am guessing that the reason they show invalid on yours is that most of them are for printers that I have set up and you have to click "More Printers" to get to them. They aren't there by default so it doesn't know where to go on yours.

Highlighted

Re: config.sup vs .pro

The best way to keep from stepping on mapkey's toes is to keep ALL mapkeys out of the company-wide config.pro at the initial loadpoint, and let the users have their own local config.pro that includes whatever they want. You can store a config.pro that contains nothing BUT mapkeys on a network drive, and tell people to use that and THEN customize it and have a local loadpoint for it.

Highlighted

Re: config.sup vs .pro

Ok well then I will ask this... How do I edit a users config.win to get Mapkeys out of there that keep screwing everything up?

Highlighted

Re: config.sup vs .pro

Mapkey definitions are in the config.pro. The config.win is the screen's appearance. If user's have their own mapkeys, you'll have to monkey with their local config.pro files.

Highlighted

Re: config.sup vs .pro

I agree with Frank... the mapkey definitions should be in their config.pro files. However, there are several locations a user can put config.pro files (maybe that's contributing to the issue)?

The config.win controls the layout of the icons on the users' menus. Way back when there used to be a file called menudef.pro that allowed users to set default menu picks for certain menu groups but that's fallen into disuse with the Wildfire dashboard controls and the Creo ribbon.

We should be able to overcome your problems with users' overwriting the company default mapkeys. DHLewis (below) correctly notes that most companies simply advise their users not to overwrite company mapkeys. If the users don't comply, they have to deal with the consequences. They can't have it both ways... overwrite the defaults and then complain that the defaults don't work anymore.

There are some instances when a company exercises bad judgment in setting up mapkeys. For instance, I used to have several mapkeys that began with the letter "f". I had "frd", "frr", and "frs". All of these were 3-character mapkeys. They stood for old Pro/E commands. My employer decided to make a "company wide" mapkey. They called their's simply "f". This destroyed all of my mapkeys.

Using a single character in this way is an example of a poorly contructed mapkey. I could see users revolting if they had to endure poor choices like that. However, it doesn't seem like you're doing that. Users shouldn't have a problem choosing alternate mapkeys. Of course... there's always one or two guys that insist on monkeying around.

I'm confident we can figure out a way to prevent them from circumventing the system. I'll write back when I have some better information to share about the trail file solution.

Thanks and best regards,

-Brian

Highlighted

Re: config.sup vs .pro

Erik,

You are not the only one with this problem. These very topics have been raised multiple times in the Technical Committees. And we keep brining it up. I would strongly suggest that you start an Idea in the Community and we can all chime in on that.

We leave them in the system config.pro and just educate the users that they don't want to use the same shortcut keys as an existing mapkey. If they do it is their time to clean it up.

Highlighted

Re: config.sup vs .pro

Okay... here's the definitive answer I promised using the trail file technique. I have verified that this technique works and will consistently enforce your standard mapkeys EVEN when the user attempts to overwrite them.

1) Save your company mapkeys to a standalone file. Your current config.sup file (the one you originally posted for us) will do just fine. However, you should rename it to use the ".pro" suffix. You can call it config.pro, mapkeys.pro, or what-ever-you-want.pro.

2) Place your mapkeys file somewhere everyone can read it... but no one can modify it (except an admin or trusted user). You can make this a network drive or a local folder locked down so users can't modify the contents. This prevents users from messing with your mapkeys.

3) Start a fresh session of Creo Elements/Pro (Wildfire 5). Know in advance where your trail files are written. Once the session starts, do nothing except the following:

  • Go to Tools->Options and select the Browse icon.
  • Browse to the network drive (or local folder) containing your mapkey file (the one you named in step 1)
  • Load the file and select OK to exit the options tool.
  • Close Creo Elements/Pro (Wildfire 5).
  • Browse to the location where your trail files are stored.
  • Open the last trail file created and remove the last few lines (where you closed and exited the application). If you don't understand which lines closed the application, I'll explain this later.
  • Save the modified trail file as "my_trailfile.txt" (or another reasonable name... but keep the .txt suffix)
  • Move the modified trail file to the same location as your mapkey file (network drive or local folder)

4) Modify your Pro/ENGINEER startup command by appending the full path name of the trailfile from step 3. Most people launch Pro/E from the proe.exe command. If your trail file was called my_trailfile.txt and it was located on a mapped network drive (for instance the "M" drive), the modified launch command might look similar to this:

proe.exe M:\company_standards\configs\my_trailfile.txt

5) Relaunch Creo Elements/Pro and test. When the application launches, it should immediately run the trail file you specified. If you're running Windchill or Pro/INTRALINK 9.x+ you'll have to log in to your server before the trail file will run... but this is normal. If you're paying attention carefully, you'll see the options menu pop open and load the mapkey file.

If any user has already set ANY of the mapkeys in your company-wide mapkey file, they will be overwritten thus enforcing your company standards.

Of course, an industrious user could always make a mapkey that would RELOAD their own custom mapkey file AFTER the trail file runs... thus overwriting yours. But at some point the user has to take responsibility if they're going to go to such lengths to circumvent your standards.

This should completely resolve your problem. The toughest parts are editing the trail file and removing the useless parts without destroying the necessary commands. I've attached my own trail file to show you what it should look like.

A brief explaination of the trail file is below... click the image for a larger, more readable version.

trailfile_help.png

I hope this helps! if you get stuck, write back!!

Thanks!

-Brian

View solution in original post

Highlighted

Re: config.sup vs .pro

I believe that this is working perfectly for me! I have it implemented and in testing right now to make sure that it didn't mess up anything else.

I will report back in a couple days on what I see.

Thank you very much!!!

Highlighted

Re: config.sup vs .pro

Excellent! I'm glad this seems to be working for you.

Let us know if you need anything else!

Regards,

-Brian

Highlighted

Re: config.sup vs .pro

Alright so now I am just confused...

The Mapkeys load in perfectly, show up in Tools>Mapkeys, and work when you click on them. But they aren't showing the correct label under the Publish Tab. I don't understand how this can halfway work?

If I click on the Mapkey under the Publish tab it still works and does everything that it's supposed to. I have no idea what is going on.

Below is what's showing on the Publish tab and Tols>Mapkeys for the same session.

Publish Tab

Mapkey.PNG

Tools>Mapkeys screen

MapkeyLabel.PNG

Highlighted

Re: config.sup vs .pro

Hi Erik...

I see 8 mapkey definitions in your Tools->Mapkeys and 10 in your Publish tab.

Go back and make sure you have the correct mapkeys added to that Publish tab. Is pltd_on_b supposed to be a mapkey? If so... it doesn't appear to be.

The simple answer is... it cannot "halfway" work. Chances are something else is haywire. I'd look at customizing the Publish tab and seeing if the other mapkeys aren't still sitting there in your mapkeys not being used.

You have to drag those mapkeys from the mapkey area into the publish drop-down... and it seems like that's where the problem is. For instance, I don't see pdfouta, pdfoutb, pdfoutc or pdfoutd on that menu either. Are you sure they've been added correctly?

Highlighted

Re: config.sup vs .pro

Alright I for sure have it working this time. Kinda weird how I had to get to keep the Mapkeys under th Publish Tab though.

1. I had to keep the Mapkeys in the old config.pro that we have been using.

2. Made the Mapkeys.pro and loaded them via trail file with the proe.exe Z:....

3.Made a config.win that has the Publish Tab on it and distributed to users.

4. Launched via old config.pro and then ran trail file to load Mapkeys.pro after launch.

If I didn't have the Mapkeys in my config.pro that I loaded from it would show the key name and say Mapkey isn't loaded in this session. But once i put the old config.pro in there and still loaded the mapkeys.pro after launch, everything shows up correctly. The Mapkeys all work and they show their "LABEL" instead of the "KEY SEQUENCE"

This ihas just been a crazy sequence of events and if you can follow it then I hope it might help someone else out too. Thanks Brian for all the help and patience!

Highlighted

Re: config.sup vs .pro

Ah... good news then!

I was just pouring through your config file (the original one) trying to figure out why the labels weren't working properly. I'm glad you got it working because I was striking out!

Take care..

-Brian

Announcements