All drawing titleblocks are is a bunch of lines with text inserted. The basic sizes are defined by ASME Y14.1M (metric) or Y14.1 (inches).
The information in the titleblocks is usually company specific so my titleblocks won't do you any good.
I do have 4 formats (C & D sizes in english and metric) that are generic that I developed for a sample GRIP program that will fill in the title blocks and store the information in the part file as attributes.
Send me an e-mail if you want them. E-mail is in my profile.
Ben,
This brings up another question... I understand you are pretty knowledgeable with GRIP, but is there a way to use Grip in a GUI? For example, I would like to press a button, and have a UG Styler GUI (or anything else - Java?) open, presenting me with all the attributes that you would set in the grip program - Drawn By, Date Drawn, Eng Signoff, MFG Signoff, related ERN, related ECN... - but in a gui format like this:
Is this done in Grip, Ufunc, or KF? And where is a good resource for finding out how to perform these programming operations? Any help here
Ben,
This brings up another question... I understand you are pretty knowledgeable with GRIP, but is there a way to use Grip in a GUI? For example, I would like to press a button, and have a UG Styler GUI (or anything else - Java?) open, presenting me with all the attributes that you would set in the grip program - Drawn By, Date Drawn, Eng Signoff, MFG Signoff, related ERN, related ECN... - but in a gui format like this:
Is this done in Grip, Ufunc, or KF? And where is a good resource for finding out how to perform these programming operations? Any help here is very much appreciated. Thanks very much
-Derek
That would have to be done in UI_Styler, which I think only interfaces with UG/Open API (Ufunc) programs, not GRIP.
I have thought of using TCL/Tk for the menu boxes using xspawn, write the data to a text file and then have the GRIP code create the part attributes from the data in the text file. Thinking about and getting a book on TCL/Tk it is as far as I have gotten, since I am busy working on the implementation of Pro/E and PDMLink to replace UG at our site. (Management decision, not mine!)
"Wildfires are dangerous, hard to control, and economically catastrophic."
I made the dialog in UI styler, but of course I have no idea how to link actions to any object in there.
I'm not real busy myself right now, but I wouldn't know where to begin learning to program TCL/Tk or much less grip. I think it would be benefitial to make a easy to use link into UG, allowing easy things like editing parameters, attributes, etc. I know KF will perform much of thsi, but that too is foriegn to me. Are there any books on grip or Ufunc available?
-Derek
Only the on-line documentation. CAST may have training modules. I am not sure if CadPo has any in their i.get.it training.
The thing to remember about GRIP is that it is like a cross between Basic and early Fortran. the other thing is that you have to try real hard to corrupt your data. Send me an e-mail if you want some sample GRIP programs. I have been know to write special ones on request. I find they are great for repetative types of functions. I don't like macros because they are menu dependent and the menus change at every version. I don't know why the Pro/E users love mapkeys so much, since they are the same as UG macros. It must be because they only have mapkeys or C programs.
UG/Open API (Ufunc) is VisualC or C++ and you can destroy the data in the file if you program something wrong. Also, almost all of the data structures have to be addressed by pointers. Everytime I try to learn C, this where I get stuck. I understand the purpose of the pointers, but I have a hard time figuring out all of the references needed to make them work, especially with UG.
"Wildfires are dangerous, hard to control, and economically catastrophic."
