Dieter @ DWorks

Nope, the part that is missing is definitely vector based graphics. The weird part is that some dimensions still are there. And the extra rectangle is just around the part that get's drawn correctly. The weird thing is that at the right edge, where it seems to have stopped rendering, there are thousands of objects on that line, so I guess VW has troubles getting them to the correct position....

@GioPet: I'm very interested in what's not working and want to find out together what needs to be done to get it to work. I would love to add it to DLibrary once we have the solution. It's what DLibrary is for: wrapping VS and avoid all weird stuff in it, making it easier to work with objects etc...

LObject isn't for the last object that was created: Function LObject returns a handle to the last object in the first layer of the active document. Use LNewObj, which is exactly to get the last created object: Returns a handle to the last object created by a VectorScript function call during the current script execution.

I was ungrouping a pdf today, which really is big, and some part isn't 'drawn'. It's really weird, as I can see two rectangles added on the area that does got drawn. Is there any limit on the size or object count when ungrouping a pdf? Note that it's a vector based pdf.

I see what you mean. My DLegend plugin also creates the objects first, because I arrange them depending on their size, specially for the texts. What I do is create them at the (0, 0) point, then do the math, and then move them to their location. This is done with a for loop, as I keep the handles in an array.

The second is correct. I'm using this. You can look at DLibrary: https://bitbucket.org/dieterdworks/vw-dlibrary/src/77b4aad5d060ef573db4f172653b8feadd24e74f/dlibrary/vectorworks.py?at=master&fileviewer=file-view-default in the Vectorworks module.

Just use ForEach... with Criteria, should be simple. Be aware that you can check out developer.vectorworks.net to see the function reference.

If you need multi-core support, then don't use Vectorscript. It's not meant to do such heave stuff....

VW doesn't store them as 'mm'. It will give you the values in the document units, whatever they may be, and it will do convertions behind the scenes to store the values....

One of the main reasons to always use attributes by class!

Why using the duplicate command? Just create a function that will create the object, and call that in a loop with a different insertion point. In VS, it's always easier to create an object than to edit it. Not that editing is that hard, creating is just simpler. I don't know how your code is, but the placement and creation of objects usually don't go together, they are two different things, so if you split them in your code, it will be easier. Maybe if we know what the parameters are and how you decide what the object is and how they are placed, then we could propose other solutions for you?

Just draw the shape of the hole on top of the slab, and then subtract that shape from the slab, it's like subtracting two shapes....

Can't agree on that. You can create great looking stairs in 2D!:

Oh please, Marionette is just Python in a graphical jacket. I would be more than happy to create Marionette components from my DLibrary DLibrary library, which is great for building plugins for Vectorworks. It just tries to get people into programming their own stuff....

That's no problem. I also learned Python over the last year and a half. though I have a lot of experience with other OO languages. If there are things you don't understand, then ask, I'll help out, even add more comments in code for things that aren't clear. I'm also busy on getting documentation for dlibrary, so please tell all problems, create issues on the public issue tracker, so that there can be examples and docs created for the specific problems you and others have with it. EDIT: Ow, and I do believe that there can be more learned by doing things yourself, that's why I don't always deliver the solution right away, so please go ahead and try, then I, and others, can comment on your code on the specific things you have troubles with, instead of pages of how to program in general. Even if the code doesn't work, or if your code is just build out of comments that tell what you want to do....

Because it's a hybrid object and will be shown in 2D plans. An extrude only shows an outline in plan view....

We'll, I also tried it, but in the end, it's still better to have those 'material' classes duplicated per context, as you can then change their attributes in viewport overrides if needed, plus being more specific in the criteria in reports and schedules. It makes it way easier. A good class structure and a nice setup library makes this so easy to work with....

I always use attributes by class, as you can control everything by it and in the long run, your far better off. Imo they should ban attribute settings and only allow by class (except for some cases). Why would 'by component' limit your 2.5D materials? in 2D, you see the attributes of the class of the object itself, in 3D and sections, you will see the components' attributes.

Nope. The floor object is the old slab, and you can create it through one of you menus. The 3D part is just the extruded 2D part.

I find the floor object better for counter tops, much easier and faster, I have always used it for counter tops.

you can edit the shape of a slab by selecting the slab, then select the edit polygon tool from your basic tool pallet, then you don't need to go into the edit mode...

OK, trick #1 I would not have expected that option (2D tool on 3D Object) Seems to work fine. Slabs aren't 3D objects, they are hybrid objects, like in 2D and 3D at the same time.

Yes! I'm very happy with slabs, they speed up the work, make great floor plans (because of the fill) and I get my sections almost complete for the first phases of the project. There are no real tricks to it. There are more tricks and workaround you need to know for the walls.

VW has Z problems in different areas, especially related to stories. If you want to get the extrude, just go to edit shape mode, copy it, go back from the edit shape mode, past it, extrude it, change height if needed.

You can just add and subtract shapes without going into the 'edit slab holes' mode. But yeah, I also hate it to have artefacts of previous adds/subtractions, so I also delete all and redo from time to time, though I don't have to add/subtract that many things, except for the door/window openings. Imo, we shouldn't need to be able to do this, at least not the subtracting, a slab should make the holes itself through priority based stuff, so if a wall is intersecting it, cut the slab.... This is already on the wish list.