Happy New Year to all.
Just wondering, does anyone have any useful ProE related commands that they use at the system window? I get the feeling it's a hangover from the good old days when people occasionally used a command prompt. The only time I use it is to purge the current folder, which I find useful, but are there any other commands in ProE?
"Gra-gra" wrote in message news: snipped-for-privacy@posting.google.com... : Happy New Year to all. : : Just wondering, does anyone have any useful ProE related commands that : they use at the system window? I get the feeling it's a hangover from : the good old days when people occasionally used a command prompt. The : only time I use it is to purge the current folder, which I find : useful, but are there any other commands in ProE?
Whatever you can do with the system window, it is still a holdover from the 'good ole daze'. If it's worth doing, it ought to be integrated into the main program. Purge: aside from the fact that the whole file menu needs reworking and the file stucture simplifying, this function, basic to good file management, ought to long ago, have been made a file menu function, not a stinky batch file. Another one which missed the gui boat over the last 10 years is Pro/BATCH, also in the /bin directory (which points to the executable in my i486/obj directory called pro_batch.exe). Even if one wished to run this as a standalone tsr, it should start from the File menu and use a common gui interface with the main program. It reminds one that Pro/e has been around for the last 20 years, but seems to have entirely missed the GUI revolution of the last ten. Another one that you can run standalone from the command prompt is Pro/TABLE. Yet this program component, which was an insult to amateur, much less professional, programmers in the 80s and should have been dumped or fixed long ago, is somehow a mainstay of Pro/e. What you find through the system window is a trailer park garage sale, running under the banner of 'Estate Sale: Antiques'.
David Janes
Yep, that Pro/TABLE was a pain in the butt back when I started on ProE
8 years ago. What does Pro/BATCH do though? Something to do with plotting, isn't it?: > Whatever you can do with the system window, it is still a holdover from the 'good : > ole daze'. If it's worth doing, it ought to be integrated into the main program. : > Purge: aside from the fact that the whole file menu needs reworking and the file : > stucture simplifying, this function, basic to good file management, ought to long : > ago, have been made a file menu function, not a stinky batch file. Another one : > which missed the gui boat over the last 10 years is Pro/BATCH, also in the /bin : > directory (which points to the executable in my i486/obj directory called : > pro_batch.exe). Even if one wished to run this as a standalone tsr, it should : > start from the File menu and use a common gui interface with the main program. It : > reminds one that Pro/e has been around for the last 20 years, but seems to have : > entirely missed the GUI revolution of the last ten. Another one that you can run : > standalone from the command prompt is Pro/TABLE. Yet this program component, which : > was an insult to amateur, much less professional, programmers in the 80s and : > should have been dumped or fixed long ago, is somehow a mainstay of Pro/e. What : > you find through the system window is a trailer park garage sale, running under : > the banner of 'Estate Sale: Antiques'. : >
: > David Janes : : Yep, that Pro/TABLE was a pain in the butt back when I started on ProE : 8 years ago. What does Pro/BATCH do though? Something to do with : plotting, isn't it?
Yeah, you know how, with Windows, you can tag a bunch of files, do Ctrl P and get them all to print. That's what Pro/BATCH does, with some added goodies, like scheduling. I think it's even gotten a gui interface in the last couple revs. Before, it was a pain just to create the list. Or you had to set up special directories, yada yada. I'm not sure if it was ever any use on Unix systems since they have their own way of queing plot jobs. The batch plot utility just made it possible to plot without the program loaded, supposing you could be confident enough of the system to have a reasonable hope of coming back in the morning and finding everything printed.
David Janes
That sounds very optimistic to me!
The only usefull thing with the system window, i think, is programming. Since the standard versions of pro and wildfire have no programming utilities at all (unlike Solid Works for instance...), the only way of programming in pro is calling batch or some other script files that creates trail files, in the system window, which you call with mapkeys.
Grts, Gerard
"Gra-gra" schreef in bericht news: snipped-for-privacy@posting.google.com...
Gerard,
Alex
Tnkx Alex, but programming in java isn't quite as easy, adjustable, and it's more time consuming compared with a script file. That's what i mean with it. (I haven't figured it out also...)
Gerard
"Alex Sh." schreef in bericht news:tWSPb.3103$ snipped-for-privacy@nwrddc03.gnilink.net...
I find it a quick way to double check what my working directory is, but you'd think by this time they could just report the path in the same bar all other prompts are shown :-)
PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.