Stefan Bender

The name of the tool should be defined in the tool definition (SToolDef type) that is passed to the constructor of VWExtension tool. Same workflow for menu commands and PIOs.

Check out macros DEFINE_VWProtection; IMPLEMENT_VWProtection IMPLEMENT_VWProtectionLDF and their use, atm I don't know the details.

Maybe it is a protection issue. IIrc you need to add some protection stuff to the code telling VW which modules are supported. Unsupported plug-ins may not show up in workspace.

You have some control over basic menu items by setting the appropriate needs/needsnot flags of the menu's SMenuDef. I don't know what is possible for chunk items.

Thanks for bringing this up! I think we have a contradiction between the entered stair break height and the height of the stair break on the upper floor if the stair break offset moves the break to another step than on the lower floor. Having two different stair breaks (and removing the offset parameter) could fix this. However, in that case minor adjustments of the stair break (leaving the break on the same step) would not be possible anymore.

Thanks Joshua! If there is no official way to create and define visualizations, we will not bother with undocumented data nodes. I was just asked for an alternative solution to a rather unimportant problem that could have been solved by a hard-coded data visualization.

Dear developers, is there a way to create and/or activate data visualizations via SDK? I couldn't find any functions or extensions. Thanks for a short note! Best regards, Stefan Bender

Dear developers, how can we create extrudes/solids with different graphial attributes on each face? Are there any SDK functions for that? It seems that the Cabinet PIO does it in VW 2026, but I couldn't find anything in the SDK. It would be great if someone could give us a hint. Thanks a lot!

You could also try interactive reshaping. You can drag various corners or sides of the stair to change its shape. That could be more convenient than entering values.

Dear developers, is it possible to use a contextual help ID instead of a URL in functions virtual void VCOM_CALLTYPE AlertDialogWithHyperlink(const TXString& message, const TXString& adviceBeforeLink, const TXString& linkTitle, const TXString& linkURL, const TXString& adviceAfterLink) = 0; virtual void VCOM_CALLTYPE AlertCriticalWithHyperlink(const TXString& text, const TXString& adviceBeforeLink, const TXString& linkTitle, const TXString& linkURL, const TXString& adviceAfterLink) = 0; virtual void VCOM_CALLTYPE AlertInformWithHyperlink(const TXString& text, const TXString& adviceBeforeLink, const TXString& linkTitle, const TXString& linkURL, const TXString& adviceAfterLink, bool minorAlert = false, const TXString& category = "", const TXString& item = "", const TXString& checkboxOverrideText = "") = 0; ? This would be very helpful. We would like to direct users to certain pages of our help system without having to update the links in our code each year or whenever the page structure of the online help changes. Thanks for any help!

Hi Joshua, thanks a lot for your response! Yes, these values come from the data record, but there should be a way for the PIO to filter out unnecessary options when users actually click on the menu thus opening it. We don't intend to alter the choices list, but we need to prevent users from selecting one that is not available atm (both in OIP and worksheet cell). Imho this is a severe limitation/bug.

If a worksheet cell is referring to a PIO record field of type kFieldPopup, the user sees all popup choices if they click on the cell and the pull-down menu is shown. However, depending on other PIO settings, sometimes not all menu choices are possible so they should either be hidden or disabled. How can we do this? Imho this should be possible either in AllowWorksheetEdit or in another (non-existing?) function that is called directly before the menu actually is displayed and would allow the plug-in to disable/hide unnecessary options. Thanks for any help!

You might wish to check the new railing PIO to create railings for the stair instead of using the stair's railings.

Looks like a bug in the worksheet function that shouldn't allow you to edit values that are by style. But if something (like editing the style) triggers regeneration of the instances, the instances should be fixed (ie, the values should be replaced by the values of the style).

What you see in the drawing could be the top graphic of another stair. If it is actually the same stair, you might consider contacting support so they can submit a bug if there is no natural explanation for this behavior.