Matt Overton

  • Content count

  • Joined

  • Last visited

Community Reputation

29 Great

About Matt Overton

  • Rank
  1. I've found with slab modifiers it's generally more productive to go cut the one you need to modify out of the slab. Fix it in context then reapply the resulting polygon(s) to the slab again. Especially given so many standard edit operations send the slab into error.
  2. Even better if the content of the sheet could be a single viewport that auto split its self across the sheets needed. By split I mean not just tiling across pages but putting break lines on each edge with "refer page xxx" and making sure the next none of the content is lost to page margins.
  3. Yes it's annoying, as you have to ask them to release, but they can't at the moment as they are you know working. So down the track they release a sing out across the office. To the point that the talk in the office is not the project architecture but cad stuff so the boss comments we seem to be having lots of issues with the new software. When 95% of those time the change is not going to effect the work the other person is doing. Most of these cases are like what you say small nuggets of pure data, reference tag updates, class settings or new layers that effect a bunch of veiwports. The sorts of changes we don't need to attend but can't put off without effecting work flow. Why can't the system just inject the new data in to the database and be done with it so neither user has to checkout or release.
  4. Could just get the staff member to put their iPhone in something like this and just use facetime.
  5. If you use the "Plug-in Manager" to set a default class for the drawing label then they insert in that class even when created inside a viewport*. *wasn't sure if "Create Detail Viewport" but after checking it seems to. Now it would be great if the installer had an option set empty default class to None without needing to go through everyone.
  6. I take it then that this should be considered a bug in the wall, slab and roof styles that they don't respect the users choice to Use class attributes at creation not a wishlist item?
  7. Pining None and say the half a dozen of the most recent user selected classes at the top of list could be very handy. Like it is with other very long lists like Fonts.
  8. This and I Agree with Jim Smith. The number of classes generally increases with the complexity of the project, we work hard to keep it down but it happens. The number of line styles is generally static to project size (5 solid various dashed, would be under a dozen 80% of projects). Being able to control lines from one spot would be a massive improvement. Some version of line styles would make it easier to tweak line weights to different scale drawings. We could keep heavy line the same weight while making the lighter lines relatively more bold. In a way not possible with a single scale factor. Oh so left field - Even better would be to embed behaviours in them so we can leave it to the Computer Automated Draftsperson to handle the complexity the computer needs. If we had line styles then part of the style could be a control how that line diminishes with distance from viewing plane (section cut, perspectives and elevations)? So super heavy lines for ground plane could fade really quickly. While say a bold line used for Solid elements might not fade at all and stock and light lines for window details could have linear fade. Bingo - nice looking elevations/sections every time.
  9. In the hopeful case that the engineers are building a system that can auto-display and dimension Storey Levels in veiwports. Would it be worth considering that building grids should also be an organisation system similar to storey levels and layers instead of a graphic element we place? - Then the same code would take care of drawing them on page for us. - Like levels we could then define object relative to a grid or offset from grid (like a column could be X= grid A , Y=grid 1 + 200 , Z = storey 3 slab) Might help with the rounding issues as well. Given this is how we always avoid the problem in large drawings anyway. Dimension critical stuff off the grid allow the float to occur between.
  10. I wonder if the objections to "drawings" would be a lot less if the double handling of information the computer already knows was lessened to significant extent and we could mostly concentrate on telling the story.
  11. Might take a bit of tweaking to get the density of tags right but I can see how we would make use of this. Would be useful if class over rides allow it to be turned off on selected viewports.
  12. In that case I'd still use layers. Lots of layers keeps most classes on by default and easier to manage. So, isolate the effected wall(s) on to new layer and then generate the options as duplicate layers. Once the options are presented and decided you can save an archive copy of file then clean house in the working file. I wouldn't call it best practice it feels like there is a better solution. With new xml text files, project sharing system and the like it feels like we should be in line to tools like GIT that the engineers to handling versioning in the code they use to write the software.
  13. Also, the interaction of project sharing and Layer creation could use some work. The operation shouldn't fail and revert just because one of the affected sheets/Viewports is currently checked out.
  14. Better still use the section viewport checkbox so we don't need to hunt multiply places to find why it hasn't worked.
  15. Yes very much in support of a clean slate set of shortcuts. Move common commands to easy shortcuts. Also, like your suggestion of a category shortcut with refining key. Would help create a fairly logical set of shortcuts. I'd add it would be great if the computer could maybe get the right secondary key based off context. Thinking for commands for clip, join,... where there is a different command for solids vs 2d planes.