Grip: Std Notes on new dwg...

[Shadowspawn]

Howdy,
I'd like to develop a grip for adding our canned standard notes to new drawings, based upon what 'kind' of drawing is being created (simple machined, machining w/comps, casting & machining, top level assy or outline, etc). I'd like some suggestions or input as to the various approaches that I could take. If you have an existing routine such as this, what do you like about it and what's the general logic behind it? Is there something about it that could be changed or enhanced? Any suggestions would be appreciated.
I'm assumming that the notes would be in seperate .txt files for calling by the routine btw... Thanks in advance for any inputs...

SS

 

[J-C]

We just create a UTD file for the dialogue that link to recorded macros for the inserted notes.

Jason

UG NX2.02.2 on Win2000 SP3
SolidWorks 2005 SP5.0 on WinXP SP2
SolidWorks 2006 SP1.0 on WinXP SP2

 

[looslib]

My notes GRIP program has the text of the notes in the GRIP source file. User selects note descriptionthey want and then the upper left location for the note.


"Wildfires are dangerous, hard to control, and economically catastrophic."
"Fixed in the next release" should replace "Product First" as the PTC slogan.

Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand

 

[J-C]

Hey Ben, are you allowed to share?

Jason

UG NX2.02.2 on Win2000 SP3
SolidWorks 2005 SP5.0 on WinXP SP2
SolidWorks 2006 SP1.0 on WinXP SP2

 

[Shadowspawn]

Ben,
I thought about that route, but am leaning towards having the notes in seperate text files for several reasons; 1) once completed, the std librarians would then be responsible for maintaining the note verbage (and I wouldn't be!)... 2) for every flavor of dwg different notes are wanted, but there are common notes among several of the flavors. This way, I'm reducing my efforts... 3) looping through a 'note list' of the desired notes would be easier to change and/or maintain... 4) adding another 'note list' in the future would be a snap...
We also have the first 5 "canned" notes that are part of the UG seed files, with the 5th note being the part marking note. I'll be using this note for the initial note origin (replacing this note if needed...), and then using our company standard spacing between each note. This way, there's less user input and assures a uniform spacing and alignment between the notes. My philosophy is that if a user can do it wrong, they probably will... so why give them the opportunity if it can be easily coded out?
Thanks for your input, it's always appreciated. I might be poking you in the near future for some UFUNC stuff. It seems coding in UFUNC/C++ is more agreeable to the other enterprises in my company, since their starting to see the benefits of the programs I've written so far but feel that grip is going the way of the dodo...


SS

 

[looslib]

When it comes to UG Grip code, I am willing to share any that I have. We are moving to Pro/E, so the GRIP stuff hasn't been enhanced in 5+ years. We are still on V18.

There are a lot of things in my GRIP programs that I would update if we were staying with UG. My drawing format program still puts the attribute string values into the format location instad of using the attribute directly. I did modify the program, but never finished debugging it to put it into production.

UFUNC is something that I never got the chance to learn. I have looked at it and C/C++ code, but never took any classes to understand the full application.

Yes, UG/Open API code is more agreeable to IT types, especially if you want to integrate TeamCenter data into other applications. It is also cleaner that using SQL to get the data through the backdoor.


"Wildfires are dangerous, hard to control, and economically catastrophic."
"Fixed in the next release" should replace "Product First" as the PTC slogan.

Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand

 

[J-C]

They don't like us posting email addys here but I you don't mind.

gildashard at yahoo

thanks

Jason

UG NX2.02.2 on Win2000 SP3
SolidWorks 2005 SP5.0 on WinXP SP2
SolidWorks 2006 SP1.0 on WinXP SP2