Hippocode

If you want to select certain objects, yes SetSelect will do. If you want to traverse the selected objects and do something with it you don't need the above but the for each loop instead. There are plenty examples to be found on this forum and even on the function reference how this works. Creating criteria can be a pain I admit. The easiest way to find out how to create criteria is by using the custom selection command and save to script. In there you'll find the criteria for what you need.

I have no experience with python. Do you also have a toolkit with wrapper classes available as in the SDK ?

Look at the ForEach... calls in the function reference. If you use the ForEachObject for instance you can add any criteria your like. Objects being selected can be one of them.

There is no manual available yet for that object. I'll try to make a small video in the coming week. The symbolobject is just a point based object. From the oip you can select a symbol from your library to display. The space reference is made automatically so just place or move this object into the 3D cube of a space object. If a space reference is found, the information will be visible in the OIP.

Thank you all for your interest. Those that requested will get an activation key to unlock the full features which expires in a couple of weeks. The latest version is available on our website and includes the ducting plug-in set. If you missed the train don't worry, you can still try out our plug-ins even without any license key. In that case it will run in a limited demo mode. Kind regards, Wouter

What you are trying to do is not possible. When changing the project based information, the records attached to the titleblock in the active drawing are updated. Currently there is no way to link this new data into other files that have this titleblock symbol referenced. It could be done however with 2 simple scripts. In the base document you need to alter your symbol's default record values to match the project settings. In any other document you have to do the opposite.

Yes the difficulty will depend on how far you want to go in changing or extending the functionality of a plug-in. It's easy to add something. But changing something will probably force you to recreate the whole thing yourself. The example you mentioned in your first post sounds easy to do.

You guessed right. I made the right choice going the C++ way. Although coding has become much more complicated, at the same time it has become much easier. Object type programming and all the possibilities are just awesome.

Did you create the shape pane yourself or is it the default pane ? Does the OIP correct itself once you reset those "old" objects ? It is most likely fixed when you restart Vectorworks as well. If made in vectorscript, try recompiling the code as well. This might reset the shape pane.

Hi, The following plug-in makes you choose a symbol and will keep track of the space object(Building, roomname and roomnumber) it is within. This can be retrieved when creating reports. http://hippocode.com/symbolobject

A lot of the default shipped tools are made in vectorscript and encrypted. It's not possible how you want it to be. What you can do however is create your own object, that creates a subobject you want to extend. This means you will need to duplicate all the params that define this subobject yourself and any additions so you can pass them through. It's not that hard. For those tools created with the SDK you might have some classes available to ease your pain. But it's still the same story. It's not open source sadly.

I've re-uploaded the video with some additional content. If you did watch the previous one start around 5 minutes for some 3D magic.

Oops I forgot to show that in the video. The duct group tool IS a 3D polygon so yes you can do anything you wish in 3 dimensions! The flexible duct is a 3D nurbs which allows any kind of curves in 3D. I will add it to the video soon.

Hi Tom, It is only available in Vectorworks 2015. So unless your signature is out of date you won't be able to test it. Let me know if you do have a 2015 license.

I've send you both a pm with some more instructions.

It seems that the video embedding stopped working so here is the link manually:

Hi, I'm looking for some people that are interested in a duct plug-in set and would like to test out our first beta. I'm interested in your opinion and desires for such a plug-in. I don't think I will find many users here but I'll give it a shot anyway. In return you will be given a discount coupon if you decide to purchase the plug-in later on. I've made a video showcasing the plug-in in it's current state: You can respond in here or send me a private message. I will contact you with more info. Kind regards, Wouter

Well that's a surprise Have fun with it ! You might also store the UID of each object into your stamp object. If your stamp object auto resets on printing it will be updated in case one of your linked objects changed size.

I've tried your plug-in and it works here. The tool ends correctly and clicking a second time will do the usal select of another object instead of running your tool another time. I tested it in VW2015 on OsX.

hPick := NIL; WHILE hPick = NIL DO BEGIN GetPt(p1x, p1y); hPick := PickObject(p1x, p1y); END;

While your object handle is NILL. This will allow you to keep clicking until you click on a valid object.

Try rewriting it in a while loop so until the user succeeds selecting a point it will keep requesting one. Maybe that "ends" the function in a better way. This will also make sure it will only copy the area if it has a valid object. Clicking in white space would not reset the values even if the GetPt was triggered again for some reason.

Whenever an object regenerates. If you for instance manually add the IFC tags of a wall and let Vectorworks regenerate that object, some or all IFC values might be overwritten. It depends on how it was hard coded.

I think I know what is wrong. Your event is running twice because you don't clear your state info on resetting. You can test this easily to assign an alertbox in your event and see how much times it pops up. Add this as an theEvent case: 3: BEGIN result:= GetCustomObjectInfo(objName,objHd,objrecHd,wHd); vsoStateClear(objHd); END;

Yes where the biggest problem is that you have the name of that English tool but have no idea what it would be in your current language.