Charles Chandler

The "new" space object, which is currently in public beta, allows separate specifications of the class for the poly and the class for the text. You might not want to install a beta of anything but I thought that I'd mention it, so you'd know something better was headed your way, before you make some sort of elaborate change to your workflow to get the effects you want.

This is exactly what Merge Organizations does. It can also import/export design layers, sheet layers, viewports, and saved views. No need for templates (which are hard to keep up-to-date), and no need to drag project files into the Standards folder so you can import classes etc. from them. You can import settings to create them in the active document, and you can just as easily export settings to the standards file for re-use in other documents. http://softwarecustomizationservices.com/default.php?page=products&subPage=products/merge%20organizations/Default

If you're looking to "define" a new set of standards, I would definitely use an AIA-based system, such as the Architect standards, as the starting point. In each instance where there is an existing AIA name for something, if you use this name instead of making up your own, your drawings will be easier to understand to others, and their drawings, to the extent that they use AIA-based standards, will be easier to understand to you. Remember that as time goes on, there will be an increasing amount of electronic transfer of data. Back in the old days, when everybody just printed out their drawings and red-labeled them to each other in these funny-looking long tubes, the internal structure of the drawing was just a personal preference. But as electronic data exchange becomes the norm, the internal structure of the document gets exposed, and finding your way around in a document that uses standards that you don't understand is a nightmare. Because of this, at some point in the future, you may actually be required (by clients and/or governing agencies) to supply electronic documents that adhere to a specific set of standards. These standards, in the US, will most likely be AIA-based. If you're already using AIA-based standards, this will be easy for you. If you're looking to figure out how to "manage" standards once they've been set up, you might want to take a look at the Merge Organizations plug-in. Once you've set up one document the way you want it, you export the standards information to an external file. Then you can just apply those standards to other documents. This makes it easy to keep all of your documents compliant with the standards you've defined, even as the standards invariably change over time. http://softwarecustomizationservices.com/default.php?page=products&subPage=products/merge%20organizations/Default

Maybe you're doing a DSelectAll in the script? Maybe calling SetSelect at the end of the script would guarantee that the object is still selected?

You should check out Merge Organizations: http://softwarecustomizationservices.com/default.php?page=products&subPage=products/merge%20organizations/Default Charles

One of these might do what you want: PROCEDURE NurbsSetWeight(objectHd :HANDLE; index1 :LONGINT; index2 :LONGINT; weight :REAL); PROCEDURE NurbsSetKnot(objectHd :HANDLE; index1 :LONGINT; index2 :LONGINT; knot :REAL);

The updater requires an open connection to the Internet. If you don't have this, just request the latest installation DVD from NNA, and do a full installation from that.

I totally agree, that getting to the data visually, instead of through a tabular interface, would totally romp. By the way, nice thread Christiaan! Regards,

=DATABASE(((('FURNITURE RECORD'.TYPE='CH') & ('FURNITURE RECORD'.ID=1) & ('FURNITURE RECORD'.'OPTION '='A'))))

"Develop the concept further" is a little too vague... What do you want it to do?

It is so easy to be misunderstood in print, and this has happened, so I owe you an apology. I totally agree that all manner of discussion is valuable, and I think that the points that you have raised are legitimate. Very legitimate in fact. (Remember, I considered these problems to be so acute that I did the Info Editor -- so yes, I concur with your assessments.) And this has been a very interesting thread. I didn't mean to sound derisive, and if I did, I apologize. Cheers!

NNA definitely intends to continue to enhance worksheets, and editable database rows are high on their priority list. But they probably will not do the advanced editing features in the Info Editor, such as the "types" functionality, the user-definable pop-up lists, etc. They already have the "group by" functionality (a.k.a., "sum"), but it's questionable whether they would support editable summed rows, the way the Info Editor does. At one point or another, you have to decide whether you're trying to do an editable query or a report writer, and while editable reports are nice, if you try to combine high-end editing features with all of the presentation features that you need for reports, nobody would ever figure out how to work the thing. So I decided that the Info Editor was still worth doing, even if NNA introduces substantial improvements to worksheets. I have had many discussions with Sean & others at NNA, before & after leaving, about types of exchanges that could occur between me and them. All that I can say for sure at this time is that I will continue to maintain and support the features that I have done, until/if/when they are completely eclipsed by NNA features. Regards,

You guys really ought to check out the documentation for the Info Editor, because it handles this kind of problem in a flexible and elegant way. http://www.softwarecustomizationservices.com/default.php?page=products The concept of "definitions" for all or part of an object is useful. Unfortunately, you have to prepare in advance for what you intend to do. If you know that you need to edit each instance, you use PIOs. If you know that you want to gang edit the instances, you use symbols. But invariably, you wind up wanting to do something that your strategy doesn't support. Now you have to delete things and replace them with other things. The Info Editor allows you to dynamically create groupings of objects. You can dynamically group by the width and height of doors, reducing several hundred door PIOs to just a couple of items in the list. Change the width of one of those items, and all of the doors of that width get changed. Next you can group by the trim dimensions and change all of the 3" trim to 3 1/2" trim. This means that you do not have to know in advance how you will need to group the objects. Christian -- while I completely understand not wanting to use third party software, I just can't resist commenting on the fact that you won't spend $10 on a plug-in that fixes this problem, but you will spend an hour griping about it on a list, and the problem still isn't fixed! ))))))) Don't get me wrong, I DO understand -- it's just that I got a chuckle out of the irony... )))))) Cheers!

No, I think it's yours, Petri. As I recall (it's been a long time, but...) you wanted us to open-source ours, so you could tweak some things, and we couldn't do that, so you did your own and put it on VectorDepot. There may have been some example code on the VS list, but what I see above is a lot more than example code. So I think it's yours.

In VectorWorks, the basic approach to architectural drafting is that you draw in 2D, and sometimes you do a little editing in 3D. Nine times out of ten, if you're drawing in 3D, there's some feature that you don't know about that could have accomplished what you're trying to do with simple 2D drafting. VectorWorks doesn't really do 3D dimensioning per se. If you just want to check a dimension in 3D, you can rotate the current view until the thing that you want to measure is parallel to the screen, and then use the Tape Measure tool to measure it, or use the Linear Dimension tool to pull a dimension. All of this is working in the screen plane (the "DCS" in AutoCAD), and any dimensions that you create will remain in the screen plane, no matter what you do. To insert an archway into a wall, place a Door object into the wall, make the configuration "Cased Opening", and then select the type of arch you want (Round, Arc Segment, Ellipse, or Gothic) from the Top Shape pop-up. Only one person can be working on any given document, but multiple documents can all be brought together into a master document using "workgroup referencing". This is like x-ref'ing in AutoCAD.

Try: result:= GetElementValue(hXML,'/geo/cloud/vector[2]/x',str1); result:= GetElementValue(hXML,'/geo/cloud/vector[2]/y',str2);

Or you could try doing a ForEachObject(callBack, (T=SYMBOL)), and then, in callBack, if GetType(GetParent(theHandle)) = 68 then it's a symbol in a wall. If you want to look for symbols in round walls too, check for a parent of type 89 as well.

It sounds like you'll have to have two plug-ins: one that is a tool, and the other that is an object. Just use the tool to collect the points, and then call CreateCustomObjectN to create an instance of the object using the points that you have collected. Objects have nice, but limited, built-in creation behaviors. If you want anything fancier than the standard point, line, box, etc. behaviors, it's easier to just to a separate tool.