Jump to content

Pat Stanford

Moderator
  • Posts

    12,532
  • Joined

  • Last visited

Posts posted by Pat Stanford

  1. You are trying to use the Database criteria in the worksheet cell instead of in the database header.

     

    Right click on the Row header (I usually start at Row 3 because it is easier to add extra lines above later when I figure out what titles I need).

    Choose Database from the popup menu.

    image.png.3e5959a1714e72ab15c3874ed748fcaf.png

     

    This will open the Criteria Builder 

    image.png.0f79cb896be6b5ab4e9d2b287dbd839f.png

     

    When you click OK on the criteria builder, the Database function will be automatically created.

     

    To edit later, right click on the database row header and choose Edit Criteria.

     

    Or if you want to manually adjust the criteria choose the Edit Database Formula and the database formula will appear in the formula edit bar so you can change it.

     

    Sorry that I didn't pick up on your putting the database in the wrong place on your first post.

    • Like 1
  2. Post the file happy to look.

     

    If you use the same criteria in a database row, how many objects does it return?  It is likely that there are no objects that satisfy the criteria which is why it is returning zero.

     

    For the record.field functions, the criteria would be something like:

     

    ('Space'.'11_Name'='Room123')

     

    All three of the field you named are defined as Text, so you will need the single quotes around the value you are comparing them to.  if you have a Space with the 11_Number of 99 then ('Space'.'11_Name'=99) won't work, but ('Space'.'11_Number'='99') should.

    • Like 1
  3. 10 minutes ago, Tom W. said:

    =OBJECTDATA((L='Ground Floor_SPACES') & (PON='Space', 'universal value', '', 'EnergyArea'))

    Close, but your parentheses are wrong.  I think the below will work but have not tested it.

     

    =OBJECTDATA(((L='Ground Floor_SPACES') & (PON='Space')), 'universal value', 'Space', 'EnergyArea')

     

    ObjectData requires four "parameters" that have to be independent and separated by commas (semi-colons in languages that use commas as decimal point)

    1.  The Criteria. This specifies the objects to be used. You can use the Worksheet Insert menu can click Criteria to open the criteria builder with all the correct parentheses.

    2. The ObjectData "Function". In this case it is 'universal value'

    3. The Record Name.  If this is left blank and the criteria is for a single object type the object parameter record will be used. In this case since there is a complex criteria (even though it specifies a single object type) I am not certain if it will find the correct record, so I have manually entered the name of the Space object Parameter Record.

    4. The Field Name.

     

    HTH.

     

    • Like 1
  4. Unfortunately, I don't think it is a bug but rather a design decision. So it is unlikely to be changed for VW2024. There have been several other similar comments so it may get traction for a future version.

     

    There are ways to hide an application window. On Mac you can either minimize the app or you can hide the app. I believe there are similar functions on Windows.  Learning the shortcuts for those may be your best way forward.

     

    But if this is a deal breaker, you will have to stay with VW2023 for now.

  5. If the problem is only with that one file, it sounds like it could be some kind of file corruption.

     

    Try creating two new files and importing 1/2 of the layers with objects from the problem file into each one. If one of them opens slowly, then you know the problem is with the layers in that file.  Repeat as necessary to identify the layer with the problem. Then duplicate the file and delete 1/2 the objects. If still slow then the problem is in the remaining objects. If not slow, then repeat with the other 1/2 of the objects.

     

    Or if both of the first 1/2 files are quick, then import the layers so you are back to one file and see what happens.

     

    And make sure you are running the latest update (3.1) to VW2024.

  6. Certain categories of menu items are considered "chunks" and you can't give items in the chunk an individual keystroke.

     

    For most of them, you could make a script and convert that to a menu command you could add to your workspace and give a keystroke to.

  7. You need to SUMmarize the data.

     

    Pick the row column that has the data you want to Summarize on, probably the Model Name.  Click on the disclosure triangle in the header row (6, not 6.1, 6.2, etc). and check the Summarize Items check box.

     

    This should give you one subrow for each different Model Name and the Count column should be the total of items with that name.

     

    image.png.294e267a39e8fd63d4822402b3e4b85d.png

    • Like 1
  8. I think Virtual Environs is correct that it is intersecting geometry.  I think somewhere in the sweep, the "back" corner of the profile polygons are overlapping.

     

    I slightly "sloped" the back edges "down" to make the back edge slightly smaller and then the sweep and the shaft were able to be Added.

     

    image.png.738bee17e5e0a1971636fc4ab91fa607.png Original

    image.png.8d9db931ba7f9f437989cba62764331e.png Modified

     

    Vectorworks really does not like having overlapping geometry in the same object.

    • Like 1
  9. There is definitely something wrong with your file, but I have not been able to identify it.  I was hoping one of our other dedicated troubleshooters would have noticed this thread and taken a look.

     

    TL:DR - Walls in the same class and same style (single component with solid lines) have different appearances with some walls not showing the wall lines.  When the layer is copied and pasted into a different file all of the walls show correctly.

  10. I think you are going to have to post the Vectorworks file for anyone to actually figure out what is wrong. There are too many possible interactions to do more that guess without seeing the file.

  11. I would start with a Data Stamp formatted Data Tag. The defaults are in the Vectorworks Libraries:Annotations:Data Tag (styles):Dims_Notes:Data Tags.vwx

     

    Versions for Long medium and short names. If you don't need the date or time you can edit the Data Tag to remove them.

     

    image.png.ef1a8113d3c50f5629caaae26be5fd88.png

  12. Did you ever get an answer to this? This is not something I have seen before.

     

    There is a setting to assign objects inside groups to the same class as the group and it has an Always Do button. If that was set, then the objects inside the group would end up in the same class as the group.

     

    But that does not seem to work with symbols. And it would not explain why you are getting Random classes.

     

     

  13. Sorry, but I just got back to this.

     

    I finally found the Window Area Ratio. It is in the 2D Boundaries and Area section and can be added to the OIP by checking the lines in blue in the Advanced Settings for the space.

     

    image.thumb.png.1d742a578591b7c5c8dfbdd5a334582c.png

     

    Here is a simple script that will set the ratio for a Space that is the first selected object in the Active Layer.

     

    Procedure SetWindowAreaRatio;
    
    Var	H1	:Handle;
    	R1	:Real;
    	
    Begin
    	H1:=FSActLayer;
    	If GetName(GetParametricRecord(H1))='Space' THEN
    		BEGIN
    			R1:=RealDialog('Enter Window Area Ratio for the selected Space object', '0.20');
    			SetRField(H1,'Space','Window Area Ratio',Num2Str(3,R1));
    		END
    	ELSE
    		AlrtDialog('First Selected Object Is Not a Space');
    End;
    
    Run(SetWindowAreaRatio);

     

    The decimal and fractional versions appear to be separate and have to be set separately.

     

    I don't think a Space has any knowledge of windows in the walls that surround it, so I don't think there is a way for the value to be automatically calculated.

     

    HTH

    • Like 2
  14. It looks like the texture of the original object was assigned to the class. See in your first screen shot the the OIP say Texture: By Class for the desktop and None for the circle.

     

    What you did is fine, but if you have a bunch of parts that need to be textured the same, you could put them all in the same class, assign a texture with transparency to the class and then tell the objects to use the Class Texture.

     

    Glad you got it working.

    • Like 1
×
×
  • Create New...