Jump to content

Hans Martin Kern

  • Posts

  • Joined

  • Last visited


4 Neutral


Personal Information

  • Homepage
  • Location

Recent Profile Visitors

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

  1. Just off the top of my head - Did you supply a png for the "Keiner" option (even if it's a an empty png)?
  2. If I insert a Door or Window object into a drawing using VW 2023, VW immediately displays blue reshape handles on the Door / Window object and I can start resizing it right away - without an additional trip to the reshape tool. Any hints on how to achieve the same behavior for a SDK-based third party plug-in? I found the extended property "kObjXPropInteractiveSizingInsert" but it looks like it's restricted to door/window use? Any hints appreciated.
  3. Hey @Woodychips, unfortunately, there's no way to parametrically remove the edge banding on the toe kick recess. As you're exporting to Enroute I assume your design is almost done so it may be worth your while to actually ungroup (a copy of) the cabinet object and turn off the the edge banding for the toe kick recess in the left & right side of the cabinet.
  4. One of our plug-ins is automagically exporting symbols to a library file using virtual bool VCOM_CALLTYPE ExportResourceN(MCObjectHandle resource, IFileIdentifier* pFileID = nil, TImportResourceConflictCallbackProcPtr conflictCallback = nil) = 0; Works like a charm. Users have requested that we should export the symbol into a resource folder within the library file - so the structure of the library file is somewhat "tidier" and easier to work with when they open it up for maintenance purposes. Is there a way to accomplish that with the SDK?
  5. @VW Inc. - maybe there is a special GS_Kludge call to give VW some time to actually close the document?
  6. You can find instructions on installing the dialog builder at https://developer.vectorworks.net/index.php/SDK:Dialog_Builder There's also the option to create the dialog layout with the SDK functions supplied, just scan ISDK for functions like Create... and SetBelow... / SetRight...
  7. Haven't seen this one. Off the top of my head - Is it a master snap in disguise?
  8. Pat - thanks for checking the issue in a different version. I verified it using the different version, too. Looks like I'll hold my breath... 😉
  9. Tried it with a stock Vectorworks 2020 SP4 US - same problem. Record720.mp4
  10. Yup, I'm using the localized German version. Good point - I'll try with a stock VW US version tomorrow...
  11. Units are the same in both files. In fact, I do create them both from the very same template file. Same result with text field. The same effect can be triggered if I create a record format manually in both files.
  12. Thanks for reaching out, Jushua. In fact, that's what I did. I assigned the record format to an object in file B. Both record formats are structurally identical as they were created from scratch by the code snippet posted. I have not touched the record formats after creation by any means. They are identical. So my conclusion is that there has to be some hidden ID / timestamp attached to the record format which makes the record formats different.
  13. I create a VW record format in document A with the following code snippet if (! VWRecordFormatObj::GetRecordFormat("SomeRecordFormat")) { VWRecordFormatObj recordFormat("SomeRecordFormat"); recordFormat.AddParamCoord("SomeParam", 0.0); recordFormat.SetLock(false); recordFormat.SetFormatVisibility(true); } and assign the record format to a VW object in document A and enter some value for "SomeParam". Then, I open up a new document B and create a VW record format in document B with the very same code snippet shown above - so record format "SomeRecordFormat" is structurally identical in both document A and B. Now, I try to copy / paste the VW object with the associated "SomeRecordFormat" data from document A to document B. Vectorworks brings up a dialog complaining about the record format ("SomeRecordFormat") already being contained in document B and asks if I would like to replace, merge, rename the record format or continue using the existing record format. Is there a way to "convince" VW that the record format in document A and B are the same and that it should not bring up the aforementioned dialog? Looks like there's a hidden unique ID or a time stamp attached to the record format?
  14. Stephan, Here's how I would tackle this: class SomeClass { public: SomeClass(); private: IEnergyBuildingElementWinDoorExPtr m_energy_2021; } SomeClass::SomeClass() : m_energy_2021(IID_EnergyBuildingElementWinDoorEx) { // If querying the interface fails for some reason, m_enery_2021 would be nullptr } The default destructor of SomeClass() will take care of releasing the acquired interface. Even if you create your own destructor, m_energy_2021 will still be released. So, to the best of my knowledge, there's no need for you to manually release it.
  15. A dialog of ours displays a list browser with a list of choices. Users can double-click on one of the items in order to select AND close the dialog right away. This is implemented in the dialog event handler function by if (itemHit == -kListBrowser) itemHit = kDefaultButtonID; This was working fine on both platforms for years, but with VW 2020, the code is no longer working on Windows (macOS still works fine). Is this a regression or do we need jump through more hoops due to the new editable list browsers?
  • Create New...