Chad Hamilton HAarchs

Member
  • Content count

    100
  • Joined

  • Last visited

Community Reputation

15 Good

About Chad Hamilton HAarchs

  • Rank
    Journeyman

Personal Information

  • Occupation
    Architect
  • Homepage
    www.HAArchs.com

Recent Profile Visitors

479 profile views
  1. I second this - and this should include not just door tags but window, plant id, wall tags - anything that is an id symbol should be page-scaled.
  2. Assuming you are talking about VW files - we use both Macs and PCs in our office, and share all files through a server. You can also exchange files from one machine to another if you don't use a server, but VW runs the files as well on each machine. We also use Project Sharing in a multiplatform environment - one thing to note is you must set up file sharing using SMB, not AFP, as PCs cannot read AFP file protocol.
  3. We have been moving towards as little paper as possible, both for long term archiving as well as day-to-day filing, so we keep almost everything on our own server. As paper comes in, we scan most rhings and file them on the server. Here is our hierarchical file system. HA Filing System.pdf
  4. Check out this video - Check known dimensions on a design layer - if all else fails, try scaling your import so that the dimension of an object in the DWG file is correctly dimensioned to the scale of the design layer.
  5. This sounds like a very good idea.
  6. Interesting - we run a local server, with cloud backup every fifteen minutes (I think - some short period of time, anyway). When a file gets corrupted or a user does something unfortunate, we go back to the cloud backup. Day to day, everyone works off the fileserver.
  7. In my opinion, this would not be good. I think it would be better to have the program behave as expected, and in my view the analogy would be between the behavior of data, revisions and viewports in a shared file should be the same as in a regular Working File. To deviate would be confusing, and one more thing to have to keep in mind while working. Again, the basic reason for not auto-updating viewports is to avoid chewing up machine computational time when you really want to be working.
  8. I set up two computers next to each other so I could check and verify the conditions we've been bouncing around. 1. On machine A, add an annotation to a VP, then run 'save and commit' - refresh on machine B - the annotation immediately appears. 2. On machine A, update a rendered VP to show the rendered textures, sky, etc., then 'save and commit' - with the same sheet layer visible on machine B, hit 'refresh' - no change on machine B until 'update selected viewport'. 3. Add some data to the model on machine A - I added some geometry that would stand out very visibly, then 'save and commit' - on machine B, 'refresh' - the new data does not appear in the VP until you also 'update selected VP' This works with any data that's added, including adding rendering textures, but anything on machine B that would normally require a viewport update still needs a view port update. Adding annotations do not require a VP update, rendering operations, or model revisions, do require a VP update. They will only show up after 'refresh' plus 'update selected viewport'.
  9. Isn't dropbox just syncing to local files? How do you get around the issue of losing data in dropbox if the local file is deleted?
  10. Don't you have a landing at each stair, with a break in the handrail? Christian's method is what everyone I know uses - if you need to run the rail continuously through the landing, you could model that single piece of railing as a separate element and use it on as many levels as you need.
  11. This is my experience - if you add annotations to a viewport in a Working File, then save and commit, it is pushed through to the Project File. If you invoke the "Update Viewport" command to update a viewport in the Working File, whether for rendering, modeling, or to update any other new data, that does not cause viewports in Project File to have updated views. To me that makes sense. For example - imagine user A is working on updating the design documents, and user B decides to do a complex render of a view of the school, then saves and commits. User A's file would be essentially locked up while the viewport rendered - that's why we have control over when viewports are updated. I have no idea whether this is on purpose or not, but it does make sense to me.
  12. Shows how different users' perceptions are - I always use class hierarchies because for me it's very difficult to find what I want in a long list - makes my eyes glaze over. Points up the benefits of a customizable interface.
  13. I think the interesting thing about discussing interface design is how to get all that data organized visually, and hierarchically. Some of us respond better to the visual organization, others to the written data organization. i personally like the idea of expanding or collapsing tabs - allows me to see information together that I think is important.
  14. I don't mind the nested dialogues, specially the new style list down the side. To me it's certainly preferable to multiple dialogue boxes. I think nested dialogues help organize the clutter when there are miles of parameters to wade through. Particularly for related parameters normally used together. Agreed, nested dialogues are tedious.
  15. No - updating a viewport is just a rendering operation in a local window. Saving and committing data is different. Think about working in a non-project sharing environment - you work on the drawing, add some data, then save - if you go to viewports containing views of the data, they are not updated, they need to be updated. Imagine you have two identical viewports - update one, the other is not affected until you update it. And you don't want to have the viewports automatically updating - you want them to update on demand. Otherwise you would be constantly waiting while the machine performed updates. Project sharing works the same way in this regard - you work on the drawing in your Working file, save and commit. The data is saved to the Project file. No viewport is updated until there is a demand to update it. For users in other Working files, the data isn't even read into their copy of the Working file until that user demands a Refresh. If another user has a viewport affected by the new data after a refresh, that viewport isn't updated until there is a demand for update by the user. Viewport rendering isn't data - it's just making data visible.