Autodesk, Inc. · NASDAQ:ADSK

Autodesk — Technical Presentation (2016)

59 slides from Autodesk's technical presentation, 2016

  1. Slide 1: Perfect Plots, Every Time, Every User

    IT21765 Perfect Plots, Every Time, Every User Frank Mayfield CAD Administrator, Benham - a Haskell Company Twitter: @theMadCadr © 2016 Autodesk Join the conversation #AU2016

  2. Slide 2: Class summary

    Class summary Ensure that the hard work you put into developing your project page setups are preserved. Take the guess work out of plotting for your users. They’ll love being able to simply select a Page Setup, and know that it’s always right! © 2016 Autodesk

  3. Slide 3: Key learning objectives

    Key learning objectives At the end of this class, you will be able to:  Learn the workflow and application of autolisp coding to take back and apply at their office.  Understand the need for setting and adhering to standard naming conventions.  Consider other applications based on this programmin

  4. Slide 4: About Me

    About Me  CAD Manager with Benham in Tulsa, Oklahoma  AutoCAD user since v2.61 (1986)  15 years of CAD Management experience  5 years as a software developer utilizing Object Oriented Common Lisp (CLOS)  AutoCAD All-Star Mentor  14th Autodesk University @theMadCadr https://www.linkedin.com/in/

  5. Slide 5: © 2016 Autodesk

    WwW AUTODESK UNIVERSITY 2016 A\ AUTODESK.

  6. Slide 6: Page Setups: The Problem

    Page Setups: The Problem  DISCLAIMER: Named Page Setups are great! They’re a vast improvement over the old system (pre-AutoCAD 2005).  Page Setups are saved in the .dwg file.  Page setup HPLaserJetPro in drawing A, may not match HPLaserJetPro in drawing B. © 2016 Autodesk

  7. Slide 7: Plotting Controls

    Plotting Controls © 2016 Autodesk

  8. Slide 8: My Scenario

    My Scenario  Multiple projects / Multiple clients  Most use our Title Block and standards, some don’t.  Different .ctb’s per discipline or drawing type, plus client .ctb’s  Four printers to choose from, plus a plotter, plus PDF or DWF © 2016 Autodesk

  9. Slide 9: My Scenario

    My Scenario  Embraced and used Sheet Set Manager  Used a Page Setup Override file for printing (a .dwt)  This was the method our users trusted.  Soon the disconnect between the override file and the page setups in the sheets happened. © 2016 Autodesk

  10. Slide 10: What to do?

    What to do?  In a perfect world, page setups wouldn’t live in .dwg files.  I needed to create a near perfect world. Where the page setups in the drawings would always match those in the override file.  I wanted the whole thing to be transparent to the user, and require no interaction on their par

  11. Slide 11: © 2016 Autodesk

    © 2016 Autodesk

  12. Slide 12: The Concept

    The Concept  It needs to load every time a drawing file is opened.  ACADDOC.lsp  Analyze the file being opened. What is it? Where is it?  Essential that you have a standardized folder and file naming convention  Based in the analysis, find your master page setup.  Manage the synchronization of

  13. Slide 13: Breaking down the steps (1)

    Breaking down the steps (1)  ACADDOC.lsp = Every time a file is opened.  ACAD.lsp = When a new AutoCAD session is started. © 2016 Autodesk

  14. Slide 14: Breaking down the steps (2)

    Breaking down the steps (2)  Analyze the file © 2016 Autodesk

  15. Slide 15: Example file paths

    P:\FDB\1650-TUL\IND\ClientName\316363 AU_CLASS\20_DESGN\40_CAD\PIPING L:\Industrial\Projects\33841 Large Mart\201 Design\20 AutoCAD\Arch B:\2016\Retail\Buy More\Burbank\91501\Eng\CAD\MEP W:\ … G:\ … Z:\Davids team\zombie apocalypse1 E:\USB20FB\My Files C:\Users\mayfieldf\Documents\Work Stuff\CAD\ ©

  16. Slide 16: Breaking down the steps (3)

    Breaking down the steps (3)  Build a path to your master page setups.  This could be very easy or quite complex.  You situation will be different! © 2016 Autodesk

  17. Slide 17: Breaking down the steps (3)

    Breaking down the steps (3)  Build a path to your master page setups.  This could be very easy or quite complex.  You situation will be different! © 2016 Autodesk

  18. Slide 18: Breaking down the steps (3)

    Breaking down the steps (3)  Build a path to your master page setups.  This could be very easy or quite complex.  You situation will be different! © 2016 Autodesk

  19. Slide 19: Breaking down the steps (3)

    Breaking down the steps (3)  Build a path to your master page setups.  This could be very easy or quite complex.  You situation will be different! © 2016 Autodesk

  20. Slide 20: Example file paths

    P:\FDB\1650-TUL\IND\ClientName\316363 AU_CLASS\20_DESGN\40_CAD\PIPING L:\Industrial\Projects\33841 Large Mart\201 Design\20 AutoCAD\Arch B:\2016\Retail\Buy More\Burbank\91501\Eng\CAD\MEP W:\ … G:\ … Z:\Davids team\zombie apocalypse1 E:\USB20FB\My Files C:\Users\mayfieldf\Documents\Work Stuff\CAD\ ©

  21. Slide 21: Breaking down the steps (3)

    Breaking down the steps (3)  Build a path to your master page setups.  This could be very easy or quite complex.  You situation will be different! © 2016 Autodesk

  22. Slide 22: Breaking down the steps (3)

    Breaking down the steps (3)  Build a path to your master page setups.  This could be very easy or quite complex.  You situation will be different! © 2016 Autodesk

  23. Slide 23: Breaking down the steps (4)

    Breaking down the steps (4)  Finally, simply delete the existing page setups, and import the good. © 2016 Autodesk

  24. Slide 24: © 2016 Autodesk

    my UTODESK UNIVERSITY 2016 € AUTODESK.

  25. Slide 25: Interlude: Organizing your code

    Interlude: Organizing your code  ACADDOC.lsp © 2016 Autodesk

  26. Slide 26: Interlude: Organizing your code

    Interlude: Organizing your code  ACADDOC.lsp © 2016 Autodesk

  27. Slide 27: Interlude: Organizing your code

    Interlude: Organizing your code  GLOBALS.lsp Sets variables and functions that are used in other routines. © 2016 Autodesk

  28. Slide 28: Interlude: Organizing your code

    Interlude: Organizing your code  GLOBALS.lsp Sets variables and functions that are used in other routines. © 2016 Autodesk

  29. Slide 29: © 2016 Autodesk

    AUTODESK UNIVERSITY 2016 A\ AUTODESK.

  30. Slide 30: Real World Examples - or - What you might run into…

    Real World Examples - or - What you might run into… © 2016 Autodesk

  31. Slide 31: Easy Peasy

    Easy Peasy  Every drawing will always use the same page setup or set of page setups.  No need to analyze anything.  Simply delete and replace every time. © 2016 Autodesk

  32. Slide 32: Easy Peasy

    Easy Peasy  Loop to delete all Page Setups:  Import all Page Setups from a file: © 2016 Autodesk

  33. Slide 33: The Next Best Thing…

    The Next Best Thing…  Multiple clients or programs, but each always uses a single set of page setups.  The client page setup file resides in a dedicated support folder.  Your analysis may simply be a drive letter:  Where “B” is the “Buy More” client and “L” is Large Mart. © 2016 Autodesk

  34. Slide 34: The Next Best Thing…

    The Next Best Thing…  Multiple clients or programs, but each always uses a single set of page setups.  The client page setup file resides in a dedicated support folder.  Or you may need to find a key string in the path:  Anything more than two, use a cond statement. © 2016 Autodesk

  35. Slide 35: The Next Best Thing…

    The Next Best Thing…  Tip: Group conditions by most probable to least probable  Anything more than two, use a cond statement. © 2016 Autodesk

  36. Slide 36: A Bit More Complicated

    A Bit More Complicated  Multiple projects, multiple clients – company and client page setups.  As the CAD Mgr, you know what folder the master page setup file should be in. In our examples above… “\CAD\” © 2016 Autodesk

  37. Slide 37: A Bit More Complicated

    A Bit More Complicated  Simply parse the path down to where you page setup file resides. © 2016 Autodesk

  38. Slide 38: Welcome to My World

    Welcome to My World  Wherein you have any or all of the previous scenarios, along with further complications.  Much more detail in the handout 1. You may need to bypass or load a different set of page setups for certain types of files or disciplines. 2. There may be page setups you don’t want to d

  39. Slide 39: 1 – Bypass or load something different.

    1 – Bypass or load something different.  You may need to bypass a certain file type or discipline… © 2016 Autodesk

  40. Slide 40: 1 – Bypass or load something different.

    1 – Bypass or load something different.  You may need to bypass a certain file type or discipline…  Based on the file, you may just load a different set… © 2016 Autodesk

  41. Slide 41: 1 – Bypass or load something different.

    1 – Bypass or load something different.  You may need to bypass a certain file type or discipline…  Another example © 2016 Autodesk

  42. Slide 42: 2 – You can’t just delete all the existing Page Setups.

    2 – You can’t just delete all the existing Page Setups.  Analyze each page setup on the fly… three examples © 2016 Autodesk

  43. Slide 43: 2 – You can’t just delete all the existing Page Setups.

    2 – You can’t just delete all the existing Page Setups.  Analyze each page setup on the fly…  Example two © 2016 Autodesk

  44. Slide 44: 2 – You can’t just delete all the existing Page Setups.

    2 – You can’t just delete all the existing Page Setups.  Analyze each page setup on the fly…  Example three © 2016 Autodesk

  45. Slide 45: 3 – The Outlier.

    3 – The Outlier. Again, ‘cause there’s always one.  A typical project folder structure – expanded… © 2016 Autodesk

  46. Slide 46: 3 – The Outlier.

    3 – The Outlier. Again, ‘cause there’s always one.  The Outlier © 2016 Autodesk

  47. Slide 47: 3 – The Outlier.

    3 – The Outlier. Again, ‘cause there’s always one. Normal Project Projects within a project © 2016 Autodesk

  48. Slide 48: 3 – The Outlier.

    3 – The Outlier. Again, ‘cause there’s always one. © 2016 Autodesk

  49. Slide 49: © 2016 Autodesk

    LIEBE SILION bn.

  50. Slide 50: Thinking outside the box …

    Thinking outside the box …  Our focus today has been on Page Setups.  Maintaining them, and importing them is the easy part.  The key is analyzing the file.  What else can you learn about the it?  What else can you do when you know what it is? © 2016 Autodesk

  51. Slide 51: Thinking outside the box …

    Thinking outside the box …  What is the extension?  DWG  DWT  DWS  You may only want to run your code on DWGs and bypass the others.  Does the file name tell you anything?  Is there anything embedded in the file itself? © 2016 Autodesk

  52. Slide 52: Thinking outside the box …

    Thinking outside the box …  What discipline does it belong to?  We’ve already used Isometrics as an example.  What else?  Architectural  Structural  Electrical  Plumbing  Mechanical  Civil  Etc.  You may write code to return the discipline… © 2016 Autodesk

  53. Slide 53: Thinking outside the box …

    Thinking outside the box …  Now you know the discipline… what can you do?  Verify or load the proper .DWS standards file  Load the corresponding Tool Palette  Load or verify layers  Load or verify styles  Text  Dimensions  Multi Leaders  Tables  Set defaults in custom program’s dialog © 20

  54. Slide 54: Thinking outside the box …

    Thinking outside the box …  A case study in… a particular project, and lazy users.  The problem: 3D piping models saved with elements turned off.  3rd party software tools.  Visual style for performance  Multiple MS viewports  In addition to being a pain for others, it affected our Navisworks

  55. Slide 55: Thinking outside the box …

    Thinking outside the box …  The solution: a custom CLOSE command in ACADDOC.lsp © 2016 Autodesk

  56. Slide 56: Conclusion

    Conclusion AUTODESK UNIVERSITY 2016 Q\ AUTODESK.

  57. Slide 57: How did I do?

    How did I do?  Your class feedback is critical. Fill out a class survey now.  Use the AU mobile app or fill out a class survey online.  Give feedback after each session.  AU speakers will get feedback in real-time.  Your feedback results in better classes and a better AU experience. © 2016 Auto

  58. Slide 58: More Questions? Visit the AU Answer Bar

    More Questions? Visit the AU Answer Bar  Seek answers to all of your technical product questions by visiting the Answer Bar.  Open daily from 8am-6pm Tuesday and Wednesday; 8am-4:30pm Thursday.  Located outside Hall C, Level 2.  Meet Autodesk developers, testers, & support engineers ready to hel

  59. Slide 59: Autodesk trademark notice

    Autodesk is a registered trademark of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specific

Autodesk — Technical Presentation (2016) on 6ix