Jump to content

Stefan Bender

  • Posts

  • Joined

  • Last visited


10 Good

1 Follower

Personal Information

  • Location

Recent Profile Visitors

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

  1. Hi all, how can we find out the current data mappings for a PIO or other record format? Are there SDK functions or VCOM interfaces for that? Thanks for any help, Stefan Bender
  2. Thanks for the replies! But recreating the entire widget does not seem to be a reasonable solution. There really needs to be an SDK call or member function of the widget for that.
  3. Dear developers, in one of our PIOs I will need to disable/dim several pull-down menu entries in an OIP widget. The widget is created automatically (it represents a kFieldPopUp field of the PIO record). I don't want to disable the entire widget, just some of the pull-down menu entries depending on the PIO's setings. Does anybody have an idea? Thanks for any help. Stefan Bender
  4. Did you try all render modes? OpenGL isn't available anymore in VW 2022 and at least one of the render mode constants is not working at all. IIrc there's a thread about it somewhere.
  5. Handles are dangerous if you give away control to other parts of the software that could delete them. Maybe you could store the UUID of the objects instead of the handles and call virtual MCObjectHandle VCOM_CALLTYPE GetObjectByUuid(const TXString& uuid) = 0; if you need to access the object later.
  6. IIuc the website shows an old version of Dialog Builder. The new version contains these four tools only afaik. You can change the type of a dialog item in OIP.
  7. The third option will be to write your own Vectorscript. That would be just the first part of the file created by dialog builder excluding the XML stuff after the Vectorscript routines.
  8. Dear developers, what exactly do the return values of these functions mean and what is the difference? - GetWallInsertLocationOffset returns (*((ParametricHandle) hObject))->wallInsertLocationOffset - GetObjectWallInsertLocationOffset returns symBreakType.locationOffset of the wall break the PIO is inserted into Are these values in sync? If not, then which one means what and which one has the priority? We will need to know that if we are supposed to support the new wall closure features in our PIOs. Thanks for any help, Stefan Bender
  9. I think quicktime support was removed from the SDK some versions ago.
  10. Hi Steve, here's the plug-in built with 27.0.1, CL 617382. Fenster CW.vwlibrary.zip Fenster CW.vwlibrary.dSYM.zip
  11. Dear developers, I have a PIO instance that has object style A. The symbol definition A as well as the style PIO (first member object of symbol A) are in class B. The object style's class is by style (gSDK->SetClassByStyle(obj, true)), but the PIO instance does not have class B but class "None" and the class pull-down menu in the OIP is dimmed. Even worse: I can't even assign the correct class to the PIO instance as ISDK->SetObjectClass(B) blocks the assignment. In function SetObjectClassWithOptionalNotification it is checked if the class is by style and if it is, the function quits so I'm stuck. So this looks like an obvious bug in VW to me. Or is there a workaround or proposed workflow for changing the class of a styled PIO instance? Btw, I can't find a function that gets or sets the class of an object style. Which class is relevant, the class of the symbol definition of the class of its PIO subobject? Thanks, Stefan Bender
  12. Yes, if the cursor hovers over a wall, the window data are recalculated based on that wall's thickness and cavities and the preview is replaced using the CallDefaultTool mechanism.
  13. According to the movie, it was reported for VW 2021, SP 2. Don't know if it existed before. I'm just going through some old bugs trying to evaluate them.
  14. Dear developers, depending on the activated snapping modes, VW displays horizontal or vertical guidelines starting at the cursor position along with the preview of the window while our window tool is in insert mode. However, as soon as the cursor is over a wall, these guidelines disappear. We noticed that VW window still does show a guideline along the wall when the cursor is over a wall so we would like to have the same behavior. How can we make the cursor display these guidelines, too? Is it some special flag or call we need to make somewhere? Or do the guidelines disappear as side effect of some SDK call? Thanks for any help, Stefan Bender
  • Create New...