Jump to content

Hugues

Vectorworks, Inc Employee
  • Posts

    940
  • Joined

  • Last visited

Everything posted by Hugues

  1. The file may be damaged. How was the file created and what was the original extension ? Can you open the file in a text editor ? Please send the file and I'll take a look at it. htsafak@nemetschek.net Thanks Hugues NNA
  2. Yes, you can do this. =E2*F2 is the formula you need to write in cell G2. Hugues NNA
  3. Only record fields are editable in a two-way worksheet. If the object names are in a record they will be editable. The two-way worksheet was not designed to be a replacement for the Object Info Palette where you can edit everything from X-Y coordinates, Class, Layer etc... Hugues NNA
  4. Do you get the same result with GDI+ Imaging ON and OFF ? I understand from your post that the problem is with this specific cell only. What happens when you clear the cell and reformat it ? Can you reproduce this problem consistently from a new worksheet ? Hugues NNA
  5. MicThorn, Also be aware that Two-way worksheets is not available in VW Fundamentals. You'd need a Design Series product. Hugues NNA
  6. Yes of course you can combine criteria in worksheet criteria functions. For example, =CRITERIAAREA((ST=FLOOR) & (L='Design Layer-1') & (C='class1')) give you the areas of floors of 'class1' that are on 'Design Layer-1'. You can use the Paste Criteria command to build and insert the criteria into your function. It seems like CRITERIAAREA and some other new functions are missing in the documentation. Thank you for pointing this out. I'll make sure that they are documented in the next version. Hugues NNA
  7. Hi Markus, If all you need is the total area of all floor objects, then you don't need to create a database. You can use this function in a spreadsheet cell. =CRITERIAAREA(ST=FLOOR) Hugues NNA
  8. Hi all, yes this is a bug in the AREA function. We recommend the use of CRITERIAAREA that was introduced to solve that problem. Also VOLUME and SURFACEAREA should be replaced with CRITERIAVOLUME and CRITERIASURFACEAREA. Hugues NNA
  9. Yes, simply copy the database row and paste it into another row.
  10. Hi Andre, This is not a bug but rather a confusing design. The "viewports" criteria is actually used to tell the engine to search into the annotation space of sheet layers viewports. Note that if you create a sheet layer viewport your objects are not counted twice even though the "viewports" check box is checked. Design layers viewports don't have an annotation space and this is the reason why the "viewports" check box has no effect. I agree that we need a simple criteria to search design layers viewports. However this would have to be a new criteria since it doesn't make sense to tie it with the search into viewport annotations. Hugues NNA
  11. Hi Michael, Yes, that's true. Pat is right! I'll see if this behavior can be changed. Thanks Hugues
  12. Hi Andre, It seems like there is a data corruption in row 14. I would be interested in knowing how this happened. Was the file originally created in a previous version ? Did this happened during file translation. Any info would be appreciated. Thanks, Hugues NNA
  13. Hi Michael, You don't need parenthesis around result1 or result2. You only need parenthesis for Boolean statements within an IF statement. Also note that you need to place quotation marks around text within an if statement. Thanks Hugues NNA
  14. This is not a bug. Boolean statements within an if statement must be in parentheses. You should write: =IF((B17=0),0,B17) Hugues NNA
  15. Worksheets on drawing export to DXF/DWG in VW2008.
  16. You can use this: =('FramingMember'.'LineLength')
  17. gmm18, yes you can. Custom-made records are not different in nature from records derived from objects (plug-in object records) The #VALUE! error in the worksheet signals that one or more parameter in your operation has an invalid value. Check again the format of the record field (NOT the cell format in the worksheet) and make sure it is not a text. If it is in fact a number or integer, then the record might be corrupt. Send me the file at htsafak@nemetschek.net and I would investigate the issue. Thanks. Hugues NNA
  18. Make sure that your record fields are not formatted as strings. Hugues NNA
  19. Yes, the format of a database cell is always linked to the database header cell. The height of a database row is linked to the database header row. Prior to VW2008, database cells were only selectable as a block. Now with the introduction of single selectable database cells and 2way worksheets, this linkage doesn't make sense anymore. Hugues NNA
  20. We have it on the radar and I have elevated its priority. However I cannot guarantee the target relesase yet.
  21. I just want to point out that the Report generator has an option that allow you to append a database to an existing worksheet. Clicks on the Options button on the bottom left corner of the Create Report dialog. Now in the options dialog you can change the database placement option to 'Append to existing worksheet' and select the worksheet you'd like to append to. Hugues NNA
  22. Use the Create Report command Tools -> Reports -> Create Report
  23. Database cells are different from spreadsheet cells. You can't set the height or format for individual database rows. They always have the same height and their format is always linked to that of the database row. If you set the height of a database row, all rows in the database will get the same height. You may see a database row adjusting to fit the content of a wrapped cell in the worksheet editor. This is confusing. This problem will be addressed in a future release. Thanks Hugues NNA
  24. Grab the bottom right corner of the worksheet grid and drag to expand it. Hugues NNA
×
×
  • Create New...