Jump to content

michaelk

Moderator
  • Posts

    6,389
  • Joined

  • Last visited

Posts posted by michaelk

  1. @Cristiano Alves

     

    Double check your criteria.  

     

    Line 1 says ALL criteria in this set.

     

    Then there are two criteria indented in.

    .    Location is within Area Plateia 1

    .    Location is within Area Golden Circle

     

    If an object doesn't meet the criteria then it doesn't get to be in your database!

    The way you have it specified only objects that are in both of the areas will be included in the database.

     

    Change line 1 in the criteria to read ANY criteria in this set.

    Now the database will include any object that is in area 1 OR area 2.

     

    If you look at the bottom of the criteria dialog box you will see the number of objects that meet the criteria.  This is a great way of double checking your work as you add and remove criteria.

  2. I don't remember there being a worksheet for this.  I'm sure you found Tools > Reports > Create Panel Schedule…

     

    I thought it was always like that(?).  Maybe there was a localized report.  I agree it's strange for you to get a panel schedule with conduit in inches 🙂 .

     

    Do you have a 2007 file with a panel schedule?

  3. If you can post a file here with just the symbol in it, or if it's proprietary you can send it to me in a personal message, I'm sure we can figure it out quickly.  It's hard to imagine all the possible settings and parameters without seeing it 🙂 .

  4. You can define working plans that are rotated and or offset from any or all axis to make it easier and more convent to work on rooted and offset objects.  It's possible to have the front view, for example, be relative to the working plane and not the layer plane.  You should get a slightly confusing warning when this is in effect.

  5. I just tried price - because I know what price of a plant means - and it works as expected.

     

    It's possible that tag display isn't actually direct parameter (?).  The data for that parameter is in pulldowns, but you have to type Left,Right,Center,None.  So it may be a just for display parameter.

     

     

    • Like 1
  6. 14 minutes ago, Tom W. said:

    I was hoping that the @michaelk-patented PIO style editing technique would work here but it didn't: using =Style.'tag display' in a database to edit all the Plant styles + change this parameter to 'Center'... 

    You know, I never actually applied for that patent.  Probably wouldn't have gotten it anyway.

     

    I am horrible with plants, both virtual and real.  Can you post a file with a few actual styled plants and a worksheet with data you would want to edit so I can see what you're trying to do?

  7. The Create Interior Elevation Viewport… command is a little quirky.  But I find that the juice is worth the squeeze.

     

    It's way way faster to create interior elevations from a 3D model than it is to draw them in 2D from scratch or exploding a section viewport.  Especially if things change down the road.

    • Like 2
  8. @E|FA attached is a simple example that is, I'm sure, much less complicated that the giant worksheet that @Tom W. has made 🙂.

     

    There is one door worksheet and one window worksheet for display.  Then there is another 2 worksheets just to edit styles.

     

    You will notice that the style worksheet displays all dimensions in mm.  But you can enter a value in feet and inches and it works just fine.  (I believe you're in the US (?)).

     

    In the "regular" worksheet you can't edit the by style parameters of the doors and windows.  Some parameters - like the ID number - can be edited.  In the fancy Style worksheet you can edit the parameters that are by style and it gives you a warning that your are about to do something big.  Agree to it and then you will have to update all worksheets or update the "regular worksheet" to see the changes.

     

     

     

     

    Style Worksheet Example.vwx

    • Like 1
  9. @Tom W. I think you found a bug.  I wonder if it's related to the display in mm, but accept document units bug.  I'll add your discovery to the bug report.

     

    Does the mm vs document units even show up for you?   I assume you are working in mm anyway.

     

    So HingePref of 0 means point towards hinge.  HingePref of 1 means point towards handle.

     

    You are correct that it Style.HingePref always displays 0.  But if you change Style.HingePref to 1 it WILL change to pointing towards the handle.  But still display 0!  Entering 0 in for Style.HingePref has no effect!

     

    Weird.

×
×
  • Create New...