Working with multiple versions of Wildfire

[rayjohnring]

I find myself using different versions of Pro/E (Wildfire 2, Wildfire 3, and Wildfire 4), and I'd like to use the same config.pro for all of them. I know I could just put it in the startup directory, but is there any way to have all versions reference the same text folder?

 

[hydromech]

It doesn't work!

Wildfire 4 will open the first suitable text file that it comes across. When you save and close Wildfire 4 the config file will be saved in the later format and wildfire 3 will be able to read the config file but wildfire 2 will not.

I run all 3 versions at work and have to use three seperate start up folders.

Adrian

 

[robertib]

The only way to make them all use the same config.pro, is to create 3 batch files, essentially copying the config.pro from a standard directory (config file only holds the non-default changes), with each batch file opening up a different version of widlfire.

Unfortunately, this will be problematic since Wildfire will try to update all parts to the latest version (ie your standard parts library), which doesn't open in previous versions - this means that you will need a separate library for each version of Wildfire.

 

[jeff4136]

I don't run multiple versions so ...

Pro/E (this is documented in Help) will automatically read, in sequence,
any config.pro found in ...
1. loadpoint/text
2. login directory
3. startup directory
... the login directory would be the place to try a 'common' file.

-Jeff Howard (wf2)
Sure it's true. I saw it on the internet.

 

[rayjohnring]

Thanks for the responses so far. I think the login directory is only for Unix, and I use Windows. Not a change I'm willing to make just to solve this problem.

It sounds like whatever my solution, I might have a problem with WF2 and WF4 reading the same config.pro. That's not terrible since I don't use WF4 yet, but I expect to in the near future.

Has anyone experimented with making the loadpoint/text directory the same for all versions? Could I just move some folders around or would this necessitate reinstalling everything?

 

[jeff4136]

The login directory is for Windows. homedrive:homepath
That's where I put my 'main' config.pro to avoid having it
overwritten if I ever reinstall.

I bet if you start shuffling files around between loadpoints you'll wish you hadn't. ;^)

-Jeff Howard (wf2)
Sure it's true. I saw it on the internet.

 

[rayjohnring]

Thanks Jeff, that was exactly what I was looking for--a config location that can be shared with all versions of Wildfire, but that isn't the startup directory.

For anyone else who's wondering, the login directory for my computer (which has more or less default settings) is the directory that has the "Desktop" and "My Documents" folder: C:\Documents and Settings\username

 

[jeff4136]

Cool. Let us know how it pans out; workable or too problematic to be practical.

-Jeff Howard (wf2)
Sure it's true. I saw it on the internet.

 

[rayjohnring]

So far, sticking the config file in the login directory seems to be working without a hitch. There are still mapkeys that don't always work, but that's expected. Thanks for all the help!

One additional problem I've discovered is that Wildfire 2 can't open files that have been modified in Wildfire 3, no matter which version originally created them. Usually it's not a problem, but it means I can't modify templates or startparts in WF3. Anyone have a good solution to this problem? Is there a config setting in WF3 to warn me when I'm opening a WF2 file?

 

[jeff4136]

> sticking the config file in the login directory
> seems to be working without a hitch

Thank you for the feedback.

> Is there a config setting in WF3 to warn me when I'm opening a WF2 file?

Still without a clue, just feeling chatty and meandering ...

Not that I'm aware of. It would be handy.

Would putting a big version note in all files help? I ~think~ it might be possible put it on a layer and have that layer shown (via config option) when opening a file.

That would surely annoy everyone and, at least, give you the satisfaction of saying; "Well, if you'd just ...". ;^)
_ _ _

Re opening of files that have been saved in a later version; are you aware of

http://www.ptc.com/products/granite/gcri/

(cross release interop)?

There's a good description of use and limitations document link on the page. Sorta surprisingly(?); I've never seen any discussion among users that have actually implemented it and use it regarding practical aspects.
_ _ _

-Jeff Howard (wf2)
Sure it's true. I saw it on the internet.