David Poiron

  • Content count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About David Poiron

  • Rank

Personal Information

  • Occupation
  • Homepage
  • Location
    Nanaimo, BC
  1. It would be nice if palettes could have multiple instances. This way you could, for example, display your list of classes in one instance and your list of layers in another. Or you could show the shape tab of the OIP and the render tab at the same time.
  2. It would be great if this tool had some additional features: 1. Ability to add more than 4 ID symbols 2. Ability to have more customization of markers 3. Ability to use in section 4. Ability to rename the ID I am using this tool for tagging walls - have not used it for other objects yet.
  3. Pat, thanks for taking the time to help with this! Much appreciated.
  4. I assume that the formula in column H should be =IF(G4,0,D4/Value(F4)). Still does not work for me however. I think IF is broken. Does not work for me in 2017 either.
  5. Thank Pat. This did work. The next roadblock seems to be getting rid of a division by zero error. I tried using an IF statement to check the denominator for zero, and then use zero instead of the D4/value(F4) =IF((VALUE(F4)=0), '0', (D4/VALUE(F4))) but it behaves strangely or does not substitute a zero for the error. On a different version of the same worksheet I used the criteria to get rid of the objects with a zero factor but if I want to show this object as zero persons in the calculation I cannot get it to work.
  6. I think the problem is that the factor column is not taken as a number but perhaps text.
  7. Attached is the file. I need to have D4/F4 for each subrow to give the number of persons per space object but it gives a #value! maybe something is not set properly. worksheet_database_row_calc.vwx
  8. I have a worksheet with database rows showing areas and occupant load factors from space objects. I would like to do a calculation of the occupant load based on the values of these two fields (area/occupant load factor). I understand that calculations in database fields may only be possible using scripting. Does anyone know how this might be accomplished? I've seen a file with a scripted calculation using one parameter, but not two, although I cannot seem to be able to make one parameter work.
  9. Here is a VW 2018 file and screen shots - pointing up or pointing down - there is no graphic difference. stair_2018.vwx
  10. It it just me or is the point direction pop-up menu of the stair tool broken in 2018?
  11. I would like to see a checkbox in the OIP of a worksheet to turn on or off the database header(s) without having to go into the worksheet.
  12. When using the grid bubble tool and dual dimensions, the brackets are grouped together when the grid bubble is mirrored, instead of being on ether side of the dimension text. See attached. Is anyone else having this issue? It would be nice to have the ability to change the dimension style in the OIP instead of having to create it from scratch every time (unless I am missing something).
  13. We are shifting our workflow into using stories. In past multi-family-residential projects where many units are the same, we've put these units in symbols so that we can make wide scale changes to them. However, when creating a symbol of the units with wall styles bound to story levels, the walls show up as having no height. There is a story aware checkbox in the create symbol dialogue box but I'm unclear to what it really does. Do styled walls work within symbols or do we need a new set of unbounded wall styles? Any tips relating to multiple unit type arrangements using stories would be appreciated.
  14. I've been trying to figure out levels and stories recently and the interface certain hampers this effort. I think there are a lot of issues including the level type button being in the Design Layer tab, and the confusion of layer types and multiple possible level elevations being in a list that you check off. I think the graphic in the current UI is useful as a confirmation, but the entry method is flawed. What Thomas shows above is a good start. To me this is a possible workflow/interface: 1. Define the layer elevations (absolute height) in the deign layer dialogue as normal if desired. 2. Create a list of stories 3. Create a list of levels for each story from a default (user-modifiable) list of level names (without elevations or layer affiliation) 4. In the list of levels assign a relative height of each level to the storey, and then assign an existing layer to each level if appropriate. The layer elevations will then show up and could be modified in the same interface. The absolute levels would then be shown for each level in the UI graphic of the stories. I think this would be better than the mish mash of dialogue boxes we have now.
  15. I have a long narrow roof that I would like to create a centre valley with multiple drains and saddles in between each drain. I can link the first two drains together and create a saddle but when I try to link the second two it gives me an error about 160 degree angle (see attached). Is there a way to do this?