New Post: Controlling Parameter and iProperty Values - We can use iLogic to help us enforce standards and other values I like to refer to as “tribal knowledge”. Having customized code trap errors in design to help prevent (or at least flag) those “freelance” design changes is a powerful and effective way of managing the expense of change at the earliest stages of the process and turning your 3D models into true knowledge assets.
 |
 |
 |
 |
 |
Search
Contributors
- Alex Karan
- Anthony Dull
- Caleb Funk
- Carl Smith
- Cassie Mulcahey
- Ed Gillman
- Hal Carruthers
- Harpreet Waraich
- Hunter Norrgard
- Jason Johnson
- Jason Pfeiffer
- Mark Cloyed
- Mark Flayler
- Paul Hamonic
- Randall Mabery
- Rob Taylor
- Rusty Belcher
- Stan Wile
- Thayne Wickam
- Tim Strandberg
Recent Posts
- Blank Parts in Inventor or Virtual Components
- Inventor Task Scheduler – Sequential Tasks
- Inventor Task Scheduler Tips
- Inserting iProperties into Annotations
- Fusion 360 - Center Line Hack
- Content Center Part 1: Basic Configuration
- Sketch Object Properties
- Passing Model iProperties to Drawing iProperties
- Saving Inventor CAM Stock for Secondary Operations
« If This Then That: Compare values with iLogic–MinofMany and MaxOfMany | Main | First Post of 2012...Taking Time to Look Back to Move Forward »
01/03/2012
The comments to this entry are closed.
Comments