Jump to content

Hans Martin Kern

  • Posts

  • Joined

  • Last visited

Everything posted by Hans Martin Kern

  1. Haven't seen this one. Off the top of my head - Is it a master snap in disguise?
  2. 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... 😉
  3. Tried it with a stock Vectorworks 2020 SP4 US - same problem. Record720.mp4
  4. Yup, I'm using the localized German version. Good point - I'll try with a stock VW US version tomorrow...
  5. 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.
  6. 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.
  7. 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?
  8. 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.
  9. 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?
  10. 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?
  11. 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?
  12. 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.
  13. 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).
  14. 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.
  15. 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 ;-)
  16. Patrick, thanks for the hint. However, this leads to the inevitable question: How do rotate a custom-object without taking the current view into account? Coming from an SDK background, I would expect to set the custom object's 4x3 TransformMatrix and I'm done. HMK
  17. Patrick - sure, here it is. Just for fun, I try to create & rotate a "Screw and Nut" custom object. RotatingScrew.vwx
  18. All, I'm trying to get my feet wet with creating Marionette nodes to support @Stephan Moenninghoff's endeavours. As you would expect from an old fart I run into all kinds of problems, so please feel free to hit me with a rolled-up newspaper if my questions are way too basic. My first "project" is a node creating any kind of custom object (code below). I tried both interiorcad's objects and stock VW plug-in objects. Works beautiful. If I route the custom object created by my node through the stock "Set 3D Rotation" Marionette node, the object is not rotated. I'm sure I'm missing something obvious here - any hints? Thanks! HMK == @Marionette.NodeDefinition class Params(metaclass = Marionette.OrderedClass): #APPEARANCE #Name this = Marionette.Node( "Create Custom Object" ) this.SetDescription('Creates a custom object') #Input Ports universalName = Marionette.PortIn(0) universalName.SetDescription('The universal name of the custom object') position = Marionette.PortIn(0) position.SetDescription('Insertion point of object instance') rotation = Marionette.PortIn(0) rotation.SetDescription('Rotation angle of object instance') showPropertiesDialog = Marionette.PortIn(0) showPropertiesDialog.SetDescription('Show the object''s properties dialog') #OIP Controls #Output Ports object = Marionette.PortOut('hObj') object.SetDescription('The resulting object instance') #BEHAVIOR def RunNode(self): #inputs universalName = self.Params.universalName.value position = self.Params.position.value rotation = self.Params.rotation.value showPropertiesDialog = self.Params.showPropertiesDialog.value #script customObject = vs.CreateCustomObjectN(universalName, position[0], position[1], rotation, showPropertiesDialog) #outputs self.Params.object.value = customObject
  19. Hi, I'm Hans Martin Kern, CTO of extragroup, the makers of interiorcad / interior xs. As some of you have pointed out, our focus has been on driving NC machinery for custom part based designs lately. Rest assured, we feel the pain of those who are using interiorcad / interior xs primarily for detailed cabinet visualization. We are (slowly but steadily) adding more functionality to the new Cabinet object - interiorcad 2017 introduced additional scribe options, additional kick options and rotated stretchers. Shaker-style / stile & rail doors (and faceframes, of course) are very much on our radar and will be (re-)introduced in future versions. If you have any specific cabinet design / visualization options you would like to see us address rather sooner than later, please don't hesitate to get in touch with me (just use the board's message option). I look forward to your feedback.
  20. Hi ccw, please contact sven.biermann@extragroup.de. He'll be able to help you out. HMK
  21. Hi, did you check out interior xs - This is the basic version without any support for manufacturing but with all other capabilities of interiorcad. It's available for Vectorworks 2010 & Vectorworks 2011 at 299? (about $430, depending on the exchange rate). As I speak, my colleagues are working on revamping our website, so there's no international info for xs yet - just contact sven.biermann@extragroup.de for more information. HMK (Disclaimer: I'm working for extragroup, developers of interiorcad & interior xs)
  22. Please excuse this shameless plug ;-) Looks like interior xs is a great option for you (http://interiorcad.org/index.php?id=387&L=1). It includes the interiorcad cabinet plug-in object plus our worktop object for a way lower price than the full, production-ready version of interiorcad. Disclaimer: I'm one of the developers of interiorcad / interior xs.
  23. Pat, sorry for the silence. Most of our engineering team is on an extended holiday break and I'm just trying to catch up on my e-mails and RSS-feeds. Unfortunately, there's no holy grail. Our main focus so far has been to provide a seamless CNC interface for our cabinet plug-in objects. In interiorcad 2009 & 2010, we have made some progress on manually designing objects for NC output, but most of it is not yet based on solid-models built with Vectorworks, but 2 1/2 D stuff derived from VW 3D objects. Most of interiorcads NC-output is targeted towards standard WOP-software packages bundled with machines like WoodWOP, NC-Studio, NCHops, IMAWOP, XILOG and others. We do not have an interface to Enroute at this moment (I know there have been talks with the Enroute guys to use their .mpr import interface, but it looks like it's not yet up to the task of importing full-fledged mpr files). We do not support going the "Export DXF route" yet, as exporting CNC-information via DXF is pretty tedious and you will lose all the CNC-semantics added in Vectorworks. Hope this provides a more complete picture, HMK
  24. Would there be substantial interest in us releasing the "Views" and "Rendering" palettes from interiorcad / interior xs to the Vectorworks community? Hans Martin Kern CTO extragroup GmbH Developers of interior xs / interiorcad
  • Create New...