# Config.pro editor

• posted

Is there a Pro-E config.pro editor available?

• posted

• posted

if you want to use it from inside pro/e, add this to config.pro :

pro_editor_command /path/to/desired/editor/editorname

or just the editor name if it is already in your system's path.

• posted

While config.pro is just a text file and you can use any editor to create or modify it, I much prefer the built in editor, for several reasons. It shows you brief descriptions of the options and often what the different values do to change Pro/e's functioning. This is not available with a text editor and must be looked up separately in the Help files under Pro/E Fundementals, the section on Configuring Pro/e. Another reason I prefer the internal editor is that it shows the available option values and even puts an asterisk by the default which lets you know what Pro/e's default behavior is. Finally, I prefer it because there is a built in Find utility to search on keywords, even letting you search on descriptions. This can give you options grouped for comparison. But, when I want to check and edit this file, without having to load Pro/e, I often use an editor like Notepad.

David Janes

• posted

This doesn't work for editing config.pro. When you specify another editor as the default, it just changes the behavior of part_table_editor, relation_file_editor and drawing_file_editor options when the value is set to 'editor'. I wouldn't change the default behavior anyway as the default editor is the new style one with the enhanced gui functionality. If you want it to be stripped down and junky, just pick protab as the value. You'll either use Pro/TABLE or go back to old Menu Manager interface. But, make sure to also change the value of new_relation_ui and new_parameter_ui to 'no' or it will use this no matter whether you pick 'editor' or 'protab'. Oh, one more thing ~ it's not really necessary to use the pro_editor_command option if you are satisfied with using the default system editor for relations, family tables, etc, probably Notepad, which will load with 'editor' selected.

David Janes

• posted

relation_file_editor

By Jove, you're absolutely right ! Just tried it and it doesn't change the config.pro editor. Since I never edit config.pro from within the program I never noticed that. Just ASSumed that changing the default would change the editor everywhere. Quirky quirky quirky.

Well, i don't think you should call Nedit "stripped down and junky" :-) It's a pretty nice editor. That's why I set the (semi)default to Nedit rather than the Pro/E stuff.

I don't think Notepad will run on my computer :-)

btw, did the op say which version of Pro/E he's running ? If it's an older one he may not have the new config.pro editor, in which case Notepad probably *would* be a better choice !

Learn something new every day. Thanks !

• posted

"hamei" wrote in message news:c1.2c.2rKZWr$snipped-for-privacy@huey.wanlong... : David Janes wrote: : > "hamei" wrote in message news:c1.2c.2rK5h3$ snipped-for-privacy@huey.wanlong... : : > : pro_editor_command /path/to/desired/editor/editorname : : : > This doesn't work for editing config.pro. When you specify another editor as the : > default, it just changes the behavior of part_table_editor, relation_file_editor : > and drawing_file_editor options when the value is set to 'editor'. : : By Jove, you're absolutely right ! Just tried it and it doesn't : change the config.pro editor. Since I never edit config.pro from : within the program I never noticed that. Just ASSumed that changing : the default would change the editor everywhere. Quirky quirky quirky. : You don't really have to assume. The internal editor for config.pro (as of 20, anyway) gives you at least a brief description of what each option does and what effect each option value has on Pro/e's behavior. It's a little help, anyway.

: > I wouldn't : > change the default behavior anyway as the default editor is the new style one with : > the enhanced gui functionality. If you want it to be stripped down and junky, just : > pick protab as the value. You'll either use Pro/TABLE or go back to old Menu : > Manager interface. : : Well, i don't think you should call Nedit "stripped down and junky" :-) : It's a pretty nice editor. That's why I set the (semi)default to Nedit : rather than the Pro/E stuff. : What I said was junky was Pro/TABLE. From day one, junky junky junky crap shit trash. They used that shit for everything, they never changed it, it was an insult to any programmer that ever lived and to every user that ever fumbled with it trying to get a job done. They had the gall to call it proprietary. WTF, who'd copy that crap!?! Copy it? No, unh unh, no man, just destroy it. Surpass it. Give a couple talented programmers a week and the job of coming up with something along the lines of dBase for Pro/e. They could have made a start on that 15 years ago and we'd have something today *not* to be ashamed of. NEdit is not my concern, it is just another text editor. Why make the problem the editor, just to promote OSF software. Anyway, it doesn't matter what wonders the editor can perform if it doesn't 'understand' Pro/e config files and they are numerous. Can NEdit tell me what propagate_change_to_parents means? Or what effect the different settings will have? Well, the internal editor gives at least some hints, so I'm sticking with that until there's something with some actual help built in.

David Janes

• posted

Oooo... Go David Go... Now how many people would have the guts to say: "This is a strange question!!!" Well, I still say there are CAD systems around that are worse... But that's why we get frustrated. Pro/E could be even better... Have you found that Enhancement request page?

Could you clue me in here... what's NEdit? Are we talking Linux here? There's a piece of my brain that still knows vi....scary!

Could someone give me a list of all the configuration files and where you put them? I've got a config.pro and a config.win in PTC_apps\proewildfire\text and a tree.something somewhere and a couple of .dtl's floating around and who knows whatall else....

-meld

• posted

Look for the _dir settings when in Tools-Options (config.pro). Set them to different store your files.

• posted

Agreed, Pro/Table is a Hoover :-)

I don't think you want an editor tho ... There's a program someone wrote to mess with OS/2's config.sys that sounds like it fits your desires exactly. It's sort of an editor but a very basic one - go to one line, rem it, change it, save it or whatever. That's in the top half of the window. In the bottom half are comments on that particular instruction, suggestions, remarks sent in by other users and so on. Basically it's a very simple database with an equally simple editor. It wouldn't be very hard to create ... maybe I'll ask the author if he'd be willing to part with the source. Another option would be to simply use a config.pro database rather than the config.sys database. You'd have to run it in OS/2 tho :-) Maybe I'll play with this a little ...

• posted

Nedit is a pretty nice ...mmm, 'programmer's' editor ? It's like a text editor on steroids. There may be Linux binaries around but it's basically an X-Window editor. Lemme see ....