Jump to content

Hans Martin Kern

Member
  • Content Count

    36
  • Joined

  • Last visited

Community Reputation

2 Neutral

4 Followers

About Hans Martin Kern

  • Rank
    Greenhorn

Personal Information

  • Homepage
    www.extragroup.de
  • Location
    Germany

Recent Profile Visitors

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

  1. 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... 😉
  2. Tried it with a stock Vectorworks 2020 SP4 US - same problem. Record720.mp4
  3. Yup, I'm using the localized German version. Good point - I'll try with a stock VW US version tomorrow...
  4. 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.
  5. 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.
  6. 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?
  7. 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.
  8. 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?
  9. Thanks - great idea, will try that one. Maybe we should encourage VW, Inc. to deliver a VW.app bundle with the get-task-allow entitlement alongside the SDK to avoid this "all-or-nothing" workaround?
  10. I found that Vectorworks 2020 uses the the "disable-library-validation" entitlement, so plug-ins should load and run (for now). However, it looks like it is lacking the "get-task-allow" entitlement, which enables debugging the plug-ins with Xcode debugger (at least on 10.14.6, lldb can no longer attach to the Vectorworks 2020 process). Any pointers?
  11. macOS Catalina requires code to be signed and notarized. Does this apply to Vectorworks plug-ins, too? Or does VW use the disable-library-validation entitlement? Any hints would be greatly appreciated.
  12. Well, in my particular setting, the dimension would be contained in a plug-in object, so I'm not concerned about the user messing with the dimension - but your suggestion "fake it using the leader text" is certainly a good one - thanks a bunch (didn't see the forest for the trees).
  13. Hi, I've been searching high and low both in ISDK and in the Object variables for an SDK equivalent to VectorScript's SetDimText() function (http://developer.vectorworks.net/index.php/VS:SetDimText). Any pointers? I think I'm not seeing the forest for the trees here. Thanks! Basically, I would like to create a linear dimension object and modify the value displayed by the dimension object afterwards. Of course, I could dive head-first into the dimHeaderNode and navigate to the text node, but I'm wondering if there's an official way to do it.
  14. The engineers are working hard on interiorcad 2018 - We hope to get it out to both our international and German speaking customers in late October / early November. I'm not yet allowed to talk about the feature set but will post more details / a URL here as soon as I'm allowed to ;-)

 

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...