Hippocode

Is this VS or the SDK? Where are you filling the drop down? I don't have this issue with the SDK. It might be the location/event where you fill the dropdown?

Any component that can be hosted into a wall is actually being duplicated inside while the original is removed. This sounds very unlogical but I don't know the reason behind it. That might be causing that row being removed.

I don't think there is a function available that can do it, as it's default behaviour. I believe the only way is to force a class (or custom settings) on your subobjects. My guess is that the recalculate event uses the parent class for all created content in that container.

I don't think you can either. In vectorscript tools are generated automatically fitting the plugin type. In the SDK, these are separate and can be customized.

Yes our SymbolObject plug-in does exactly that. It can be very useful for indicating shafts and other components that have exact the same composition through multiple layers. You can choose to show the symbol on any combination of layers from a selection box. This is made possible by using the proxy object functionality and works best with 2D symbols only. The object duplicates it's content on all the chosen design layers. While you can select and modify this object on any of these layers, it is one unique object. It is also possible to count all the occurrences when using worksheets.

Sadly I won't be able to come to the DS this year, but I do like the idea. I'd say it should be even part of the DS, but I guess our numbers are probably to small for Vectorworks to invest their valuable time of the summit. Then again my opinion is that if you have zero custom scripts/tools/addons active in your workspace, you are doing it wrong and need help

From what I understand, plug-in styles are only supported if your object matches a unique ID hardcoded into Vectorworks (by request). It is required for your object to be recognized by the functionality.

If you debug you should be able to see on which line the error occurs? Also, you don't need to define "poly" on declaration.

if object A is the parent and it creates object B inside of it (parent - child) there is no need of catching it with a unique name, as you have a handle when creating it. That is, unless you have your object A set not to automatically remove all it's contents on reset, on which case your interface manages it. This is used if you don't wat to recreate all the inner objects each time the object is reset.

It only requires one argument, unless you want to specify a path/profile. Your object will be created and reset. Only after this creation the path will be attached and reset again. In any case, your object's code should be able to handle a NULL path. Can you post a bit more of the last steps before the crash occurs ? Could also be a recursive reset.

Yes, I assume you are not veryfing the path handle. When your parent creates the child, it could be that the first reset is called before your path is assigned. If you just assume its a correct handle and cast it to a nurbs or poly you'll run into this. Since you talk about parent and child, can I assume you've set your plug-in not to remove it's content on reset? If not you do not need to get the handle by using a unique name.

I usually add a class parameter that overrides the object class on object recalculation. I only do this when the current class does not match the class of the parameter to avoid infinite recursion as mentioned above. Though it could be that setting a class does not reset the object anymore, something changed about it a couple versions back.

Your object origin is always 0,0 towards your object insertionpoint. Knowing that, for your object to show something at an absolute position in the drawing, all you need to do is substract the object position from the relative position of the part within the object. Say you want something shown absolute at A(50,50), your object is placed at B(25,25) => The inner component of your object should be placed at A-B. Keep in mind that this does not take in rotation, you should apply the transformationmatrix of the object instead for this to work.

Assuming you have one instance of this symbol selected, you can use the active handle to retrieve the values, get the handle to the definition itself and overwrite them. From then on, any new placed instance will use the updated record information.

A light object is not a parametric object, thus any data is not saved into a record. Instead, everything is saved as object properties. You can find the appropriate constants in the SDK definitions. Search for ovLight. It could be that just like in the SDK, VS also has wrapper functions available.

Typically they should follow a logically order of events. kObjectExternalReset is called when an object reset is caused by another object. I assume the first reset is yours. For some reason, an additional reset by something else in the background is causing the other events. Some actions can cause multiple events because sometimes we want to do something on a specific moment when an object is changing. It could be that modifying text does that. I wouldn't worry to much about it unless you end up with unwanted behaviour.

Is this a custom object, or are you referring to symbols ? Default symbols have no way of autolinking fields. You can do this with a custom object using GetRField, SetRField.

You can change your view to 2D and reset it after you run that function.

I have no idea if it's possible with the default tools. We do have this feature enabled on our own plug-ins. Those annotations are symbol based and scale based on the pipe diameter which will show you that circle with the exact size in 2D. For other specific variants (Tee up / down) etc you can specify different symbols.

Hi I have objects that reference others by an internal index. Basically it's a list of objects A that reference any other object (any type) named B by their internal index. This reference is saved into a Sint32 Parameter. When referencing this file into an other document (e.g. layer viewport), the references are broken because they assume the indexes remain the same, which they don't. Is there any way to find out the new indexes relative to the other document so I can correct the internal indexes to their correct values?

I'm in need of a custom hidden group, similar to the profile/path group available in plug-ins. (I can't use those for this specific object as they are both in use already) Am I correct assuming the path and profile group are groups attached as aux objects with a specific data tag for them to be recognised? Is the content of such groups hidden by default or do I need to do something with it so it doesn't show as part of the object?

This should get you started. Modify the <> wrappers to the exact name, recordname and value you want to modify. Note that you might need to native object name which can differ from the visual localised objectname. Procedure EditRecordFormat; VAR ObjectName :String; RecordFormat: Handle; ObjectType: Integer; BEGIN ObjectName := '<ObjectName>'; RecordFormat := NIL; RecordFormat := GetObject(ObjectName); IF (RecordFormat <> NIL) THEN BEGIN ObjectType := GetTypeN(RecordFormat); IF (ObjectType = 47) THEN BEGIN SetRField(RecordFormat, ObjectName, '<FieldName>','<FieldValue>'); END; END; END; RUN(EditRecordFormat);

Normaly you can't modify any tool defaults with VS. What you can do is modify the default parametric record used in creating a new object. The parametric record is unique and can be retrieved with the unique name of the object. You can get the handle with GetNamedObject or some similar function taking a string. The normal Get/Set record field functions will work on this handle.

From looking at your screen I would think the VWX truss lacing is made with a curve split in many parts, while you have a continous curve. It could also be the weight of your nurbs points make it look so rounded.

I'm looking for some designers to test our new "Provision for voids" manager to provide feedback. You can reply here, by pm or by mail if interested. This video is a small teaser what it's about, there is however more to discover. Create voids (clash intersections) based on predefined sets of your choice (any object, including IFC entities). The idea is that once the Voids are created, they can be managed and used throughout the whole design process as a communication tool. These voids will automatically manage the required holes in walls and slabs. We are working on import/export functionality which enables collaboration beyond the scope of a document.