All Activity

This stream auto-updates   

  1. Past hour
  2. One important point to remember when working with lists is that adding objects or deleting objects can be problematic. If you start at the top of the list and delete the object, then NextObj will not find anything because the handle to the "first" object no longer exists. For deleting objects you are normally better off starting at the bottom and using PrevObj (or PrevSObj). Get a handle to the PrevObj before you do the delete. If you are adding objects, you need to be careful that you don't create an infinite loop. Consider the following pseudo code. Get first object While Handle <> Nil Create new object at bottom of list Get next object End While You will never get to the bottom of the list because every loop through you add another object to the bottom of the list. Just some lessons I learned the hard way.
  3. Today
  4. Hi, How can I show the doors handles I choosed from the hardware list in my 2D plan? I can see them only in 3D.\ thanks Vectorworks 2017 SP2
  5. I tend to use ForEachObjectInLayer() more than ForEachObject(). Some people like to think using <criteria> to sort the whole document, while I like to think of lists describing smaller sections of the document. Essentially you should be able to do either to get the same result, but with ForEachObject() you will be looking at everything drawn on all layers if you don't filter anything out. Since you got your problem working, you can ignore this for now, but you might want to give ForEachObjectInLayer() a try next time. ForEachObjectInList() is also quite useful if you have a targeted list you want to traverse, like the Symbol Definition List, and you already have a handle to an object in that list. One caveat, the ForEach... commands use a built in equivalent of NextObj(), and not PrevObj(). Lists will always be traversed this way. Raymond
  6. There was a very interesting, efficient Subdivision demo of a door pull, but can I find it?
  7. What I see in my Vectorworks file is what I want to see when I export the image, but it is not. Is there a file format or setting that will give me the same results as what I see in Vectorworks? This screen shot is accurate. Oddly it can reproduce the colors extremely close (if not exactly the same), but Vectorworks cannot. This is a JPG export: This is a PNG export: This is a PDF export: Murphy Bed Queen Complex.pdf
  8. For me, creating a NURBS curve in 3d space is like grabbing a wad of string, closing your eyes, spinning around 3 times, and then throwing it. There seems to be no predictable results. I learned a lot from this exercise.
  9. I also prefer the Slab Modifier sub mode, as it is used in other 3D objects too. But there needs also to be a visual separation or layering of which 2D modifier geometry effects which component or the whole slab.
  10. Small but useful: I would like to see which wall component is selected in the Edit Wall Style window, maybe by a flash or somesuch. I would also like to see the implementation of the contextual menu items, so a right click on a component offers Edit, Duplicate, Delete & a right click on a blank area offers New. It would also be nice if the Wall Component Settings window moved so it didn't reliably cover the Edit Wall Style window by default. The first task is always to move these aside.
  11. @JROCCIHi, the site modifiers will alter any site model you place over them existing or new. Take a snapshot of the existing and use that. Have another design layer selected just for the snapshot as when you create it it will go onto the active Design layer. HTH Stand corrected about this, but that's the way i find i can solve the issue.
  12. It it generally possible. It may be that you need to restart VW to give it a chance to do some clearing and try it again. If you can upload the file or a sample file we can take a look.
  13. I've found with slab modifiers it's generally more productive to go cut the one you need to modify out of the slab. Fix it in context then reapply the resulting polygon(s) to the slab again. Especially given so many standard edit operations send the slab into error.
  14. i did this by purpose to keep the filesize down but no it doesn't get better....
  15. I am trying to create a DTM using a combination of survey and google earth data, and using tools such as the roadway (poly) to help carve and add detail into the DTM. This has all worked pretty well, except that in my siteplan it is now showing the contours in the location of the roadway as being modified per the proposed. In this project, all roads are existing, and I need them to read as such in the site plan. How do I designate that the site modifiers from the roadway are part of the existing line-work from the DTM? Thanks, Jerry
  16. Any resolution to this? I'm experiencing this issue now. It seems rotated top plan loses snap capability in dlvp's.
  17. Thanks, Pat...was able to get ForEachObject to do what I needed!
  18. I am referring to DLVP (Design Layer ViewPorts), not Sheet Layers. I am referencing an architects IFC building (via VW shuttle file) into a master site plan drawing. I have rotated, moved, and elevated the DLVP (building) to the correct location elevations based on the cad survey. All good to this point. The problem comes when I need to SNAP to the objects being referenced via the viewport. It seems I am completely unable to snap to the viewport objects no matter the settings I try.
  19. Was wondering about ForEachObject, but since the function reference guide states that it's essentially the same as writing a NextSObj loop, I thought it might not work. But I guess I will go test more of that.
  20. The Next and Previous commands work with a concept called Lists. You get a handle to an object in a list and then the Next will give you the handle to the next object in that specific list. Depending on exactly how you get the original handle the list will contain different objects. FInLayer get a handle to the first object in the specified layer. NextObj on this list will get you the next object in the layer (Next is defined primarily by the order in which they were drawn, but Send Forward/Backward/Front/Back will change the stacking order and list order). NextSObj will get you the next selected object in the layer. FinGroup get you a handle to the first object in a group (I think this also works in symbols), so the list is all of the objects that are in the group. FIn3D gets a handle to the first 3D object in a specified object. The list is all of the 3D items that make up that object. FinSymDef - The list is all of the objects that are part of the symbol. FObject - The list is all of the objects that are in the same layer as the very first object in the drawing. I learned about this limitation the hard way. It seems as if this should let you iterate through the entire drawing, but you can't as soon as you try to step past the last object in the layer you will get a Nil handle and not be able to go any further. FSActLayer - The list is all of the objects in the selected layer that come after the selected object. NextSObj will get you just the selected objects. NextObj will get you all of the objects. FSObject - The list is all of the object after the selected object that are in the same layer as the selected object. See FObject FSymDef - The list is all of the symbol definitions in the drawing. There is no easy way to use NextObj to step through objects on different layers. The work around is to use the ForEachObject command and an appropriate criteria to process the objects. Ask if you need more information.
  21. Sheet Layers are always at 1:1 scale while the viewport is usually at a different scale. In order to be able to snap to objects shown in the viewport enter the Annotions group of the viewport so you are working in the same scale as the objects being shown in the viewport. Right click or double click on the viewport and choose Edit Annotations.
  22. I've always used h:=NextSObj or h:=NextObj in loops to run a script across a series of items. While updating my scripts, I'm trying to get them to work across layers if layers are set to Show/Snap/Modify. Selection works across the layers, reporting the number of selected items world across layers, but NextObj and NextSObj do not. Is there another procedure I should be using?
  23. Nice job Bruce! KM
  24. Is there no way to snap to viewport objects? Theres gotta be...what am I missing?
  25. I know this is the convention. However, I would like to have the option to show imperial scales as 1/4" : 1'-0" and still have them use the correct scale of the viewport instead of typing a custom value.
  26. You should pick the type of object that matches how you want the user to place the object. If you want the user to just draw a line, pick the line type, etc. The various types also only have reshape handles according to their type, so if you draw an oval with the line object, the user can only adjust the height via object info. You can add control points for reshaping, but that adds a fair amount of complexity to the script. -Josh
  27. Michael, Yes, you can do what you want. You can use a line type PIO to define the length. Add an extra parameter (so it will show up in the OIP) and put in the default value you want. The user will then be able to change that parameter value to change what happens when the object is refreshed.
  1. Load more activity