Jump to content

Peter Vandewalle

Member
  • Content Count

    158
  • Joined

  • Last visited

Community Reputation

30 Great

About Peter Vandewalle

  • Rank
    Journeyman

Personal Information

  • Occupation
    Senior Product Specialist - Design Express
  • Homepage
    www.designexpress.eu
  • Hobbies
    Architecture, Music, Mac
  • Location
    Belgium

Recent Profile Visitors

898 profile views
  1. In older versions, one could open the dialog and close it without modifications. At that time the databaseformula was editable in the formula bar. This still works in 2021 also. I've been using that for years. That enhancement request exists indeed. Not sure about how high this is in the ranking though.
  2. @B Cox Hatches aren't necessarily an issue in imports. If you import the file in the correct way, it will be no problem. The issue is that most ACAD-users never fill out the used units in their file, so chances are the units recognised are wrong. Here's the best way to import a dwg-file: Open a new, empty drawing with your drawing units set. (The issue with wrong sized dwg-imports isn't scale related, it's unit related.) Import the dwg-file without using the automatic unit recognition. Start from the idea that the ACAD user is using your own units, so select your own units. After the import, verify the size of any object of which you know a size. Don't trust those things that look like dimensions, often they are groups of lines and texts. While you see the size of the object, try to determine the units in which it has been thought. I.e. if I see a stair in my drawing in cm that says it is '900' wide, I know that should be mm, not cm. This way I'm sure the ACAD-user has been thinking in mm. DO NOT scale all the imported objects, this will cause the hatches issue. Instead of scaling the contents, just close your vwx-file without saving. Open a new vwx-file with your units set. Import the dwg-file for the second time. Now choose the units you derived from the previous import. The import will be OK. Hatches will no longer be an issue.
  3. I use these commands in a 'renovation tool' that is included in our regional version. That tool will show/hide classes depending on a calculation from the class name. So it it perfectly possible.
  4. At creation dimensions will be created in the dimensions class, if that option is checked in the preferences. They can be assigned to any other class manually or by script however. If I get it right you want every text and callout to be assigned to the 'Tekst' class. Not section lines, dimensions, ... Then this script should do the trick: def main(): criteria="INSYMBOL & INVIEWPORT & ((T=TEXT)|(PON='Callout'))" vs.ForEachObject(DoIt, criteria) def DoIt(h): vs.SetClass(h, "Tekst") vs.ResetObject(h) main() Scripts run from the resource browser don't need the 'import vs' line. You don't need to create a selection to pass to the ForEachObject call, you can use the selection criteria.
  5. Also check the density of imported hatches. If you import an acad file and the content isn’t in the correct size, most users will scale the imported objects. The hatches however won’t scale and might be extremely dense. This results in zones with hundreds of thousands of hatch lines that have to be computed by the graphics card. This will dramatically slow down the file.
  6. And also add "vs.DSelectAll()" before the selection call.
  7. You can use the SetWSCellFormulaN command to fill text or formulas into a worksheet cell. That won't be a cell in a database row however. These rows are calculated and can only show object data. That object data may be seen very large, certainly with the RunScript possibilities. https://developer.vectorworks.net/index.php/VS:SetWSCellFormulaN
  8. Try it in 2021. I noticed much faster hidden line renders.
  9. I think rewriting is the only way to go. Python is slightly faster in execution than Vectorscript.
  10. Make sure the autosave saves to your local disk and not a server. And don’t autosave every 2 actions...
  11. I’m in the car right now so I can’t test but I would try with 0, 1, and so on. Or create a little loop with integers and an alert dialog...
  12. The only parametric objects that can be contained in a Vectorworks file are Marionette objects. Vectorscript or Python plug-ins are less limited and run faster however. I put my plugins in a workgroup folder. That folder is on my iCloud but it could also be Google Drive, One Drive, Dropbox, ... I can then share that workgroup folder with other users in the team, so they can also use the plugins.
  13. There seems to be no call for shadows... I'll check on that but here's a version that should also do text styles and textures. Object Attributes to Class_02.zip
  14. The 'Assign obj attrs to class.vsm' is protected, so one cannot edit the script. But from your description, this plugin should do the trick. It acts on a multiple selection also. Just unzip the archive and put the folder in your plugin folder. Object Attributes to Class.zip

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×
×
  • Create New...