Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

22 Great

About Hippocode

  • Rank
    500 Club

Personal Information

  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I believe when creating a symbol from the VWSymbolObj wrapper class it's not properly attached to a container, in your case the active layer. Try additing it manually after you create the symbol, and before you reset it using "gSDK->AddObjectToContainer"
  2. Have a look in this topic: If you don't create something, your can use other functions to traverse the workspace, find the palette by name or identifier and use that handle to show/hide these.
  3. Well it could be any of these settings. I'm setting all these to show the palette in a specific spot. bool inTearOffState = false; bool inTopPosition = false; Sint16 ToolinSortStyle = 1; Sint16 ToolinViewStyle = 2; Sint16 ToolSetinSortStyle = 1; Sint16 ToolSetinViewStyle = 2; bool inVisibilityState = true; bool inWindowShadeState = false; EWindowHomeCorner inHomeCorner = EWindowHomeCorner::eWindowHomeCorner_ScreenUpperLeft; Sint16 inHorizontalOffset = 0; Sint16 inVerticalOffset = 0; ViewRect screenRect; gSDK->GetScreenSize(screenRect); ViewPt Center = screenRect.Center(); inHorizontalOffset = +Center.x; inVerticalOffset = +Center.y; if(VCOM_SUCCEEDED(errorCode)) errorCode = pToolPalette->SetTearOffState(inTearOffState); if(VCOM_SUCCEEDED(errorCode)) errorCode = pToolPalette->SetToolSetPosition(inTopPosition); if(VCOM_SUCCEEDED(errorCode)) errorCode = pToolPalette->SetToolSetSortStyle(ToolSetinSortStyle); if(VCOM_SUCCEEDED(errorCode)) errorCode = pToolPalette->SetToolSetViewStyle(ToolSetinViewStyle); if(VCOM_SUCCEEDED(errorCode)) errorCode = pToolPalette->SetToolViewStyle(ToolinViewStyle); if(VCOM_SUCCEEDED(errorCode)) errorCode = pToolPalette->SetToolSortStyle(ToolinSortStyle); if(VCOM_SUCCEEDED(errorCode)) errorCode = pToolPalette->SetVisibilityState(inVisibilityState); if(VCOM_SUCCEEDED(errorCode)) errorCode = pToolPalette->SetWindowShadeState(inWindowShadeState); if(VCOM_SUCCEEDED(errorCode)) errorCode = pToolPalette->SetHomeCorner(inHomeCorner); if(VCOM_SUCCEEDED(errorCode)) errorCode = pToolPalette->SetHomeCornerOffset(inHorizontalOffset, inVerticalOffset);
  4. Is there any way we can provide a link to our own help documentation/wiki when creating tools with the SDK? When you hit F1 on default tools you end up on the specific article explained in the Vectorworks help.
  5. Make sure that the workspace interfaces are initiated correctly. This is a snippet of my workspace wrapper class and confirmed to be working: VCOMPtr<IWorkspaces> pWorkspace(IID_Workspaces); // Get current workspace file name. TXString workspaceFileName; gSDK->GetCurrentWorkspaceFile(workspaceFileName); // Current workspace full file name. TXString workspaceFullFileName = workspaceFileName + ".vww"; VCOMPtr<IWorkspaceFile> pWorkspaceFile(IID_WorkspaceFile); if(pWorkspaceFile && pWorkspace) { errorCode = pWorkspaceFile->Open(workspaceFullFileName, kFileReadPermission); VCOMPtr< IWorkspaceToolPalette > pToolPalette; VCOMPtr< IWorkspaceTool > pTool; TXString ToolPaletteName = "VectorMEP"; TXString ToolPaletteIdentifier; if(VCOM_SUCCEEDED(errorCode)) errorCode = pWorkspace->CreateIdentifier(VectorWorks::Workspaces::EWorkspaceItemType::eWorkspaceItemType_ToolPalette, ToolPaletteIdentifier); if(VCOM_SUCCEEDED(errorCode)) errorCode = pWorkspaceFile->CreateToolPalette(ToolPaletteIdentifier, &pToolPalette); pToolPalette->SetDisplayName(ToolPaletteName);
  6. In short: Only the creator of the voids requires a VectorMEP license. All the other communication tools are free. The mapping tool allows you to predefine filters of objects you would like to compare. For instances all pipes versus floors. You can even define a parameter value to filter even further. You can also setup additional dimensions when creating voids, based on some categories. If you map a "pipe" as "Plumbing" category, the additional offsets will be used as set in the dimensions dialog. Person A creates the voids by selecting the mappings. Person B references the file that contains the voids. Person B can now manage the status and comments of these voids within his own project. Person B can export his modifications to an XML file. Person A imports the XML file, which updates the status and any comments of each void. This process can be repeated. Note the the openings are only created for those objects that support it, but in both cases the void object will be present. You can create unlimited void mappings based on object names and optionally based on a parameter value. Also supports custom objects. I'm about to update some of it's functionality so wait a tiny bit if you plan on testing it out.
  7. This plug-in is part of our VectorMEP bundle. It's not meant to be a clashing tool, but rather a tool that automates openings and allows you to communicate about it. While the example shows automated voids between pipes and walls, the tool allows you to select any kind of "clashing" object, thus not limited to MEP design. It also allows you to export/import voids between users as a communication tool. You can add comments, accept or deny void suggestions etc... Showcase video:
  8. If they are also "outside" the container of your PIO, so not part of it, you need to attach them to the PIO's container after duplication.
  9. Couldn't find any constant to read that property in the minicads file. I vagely remember when building lists the filename was used as prefix or something similar but that would require you to build a huge list of all available resources, which is still a valid possibility. From looking at this article, one of the other similar functions will probably return the filename within the symbolname if from an external file, but it might only work if those are duplicate: http://developer.vectorworks.net/index.php/VS:GetActualNameFromResourceList You could also try using the IResourceManagerContent VCOM interface to search for the specific symbols, maybe some of the functions also return the filename.
  10. I faced a similar issue trying to find out if some of my custom plug-ins were referenced or not. I used the following approach which seemed to work as the "IsObjectFromReferencedFile" function didn't (always) return the expected results you can just look at the object's layer name instead. // Referenced? fInfo.IsReferenced = gSDK->IsObjectFromReferencedFile(this->GetThisObject()) || gSDK->IsViewportGroupContainedObject(this->GetThisObject(), kViewportGroupCrop); // Since above doesn't work :( MCObjectHandle hLayer = this->GetParentLayer(); if(hLayer && VWLayerObj::IsLayerObject(hLayer)) { VWLayerObj L(hLayer); TXString strLevel = L.GetName(); fInfo.IsReferenced = strLevel.Find("NNA") != -1; // NNA seems to be put in all referenced layers, so any object that is referenced matches this parent layer name. }
  11. I can provide you with some other samples if you need some. They come in handy sometimes, the benefit is that such a tiny script has access to your complete SDK. If you have SDK bases plug-ins you can use this to make certain data or functionality accessible through VS. I have made several of those for my plug-ins. e.g.: The ability to activate our license to use our software for the current session, bypassing our default activation method. It requires a custom hash to unlock the current specific day.
  12. Using the plug-in manager to install the plug-in did work, thank you for the suggestions. I'm a bit surprised this works but manually installing doesn't. Maybe Vectorworks removes the quarantaine of the file while copying.
  13. I removed the quarantaine of the buildvwr tool instead of disabling scrutil so I can see the error messages myself. Signing alone doesn't do it and I'm unable to create an archive of the plugin in order to get it notarised (Also tried it on the TesterModule sample). Has anyone done this before? I'll see if I can do it manually using terminal instead.
  14. All of them as zipped files (download available on a website or Google Drive). Some bundles support the third party plug-in installer within Vectorworks, which requires the files to be zipped. I also zip them because some browsers/cloud solutions rename extensions and capital letters in the VWR resource on download/zip which breaks the plug-in. I can't really imagine doing this without these files being zipped ūüėģ
  15. Thanks, this helped me out on the developer side. But clients are now reporting Vectorworks prevents them of using the plug-in because of restrictions obviously... Do we need to modify some settings of our projects for them to be accepted somehow?


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

  • Create New...