Jump to content

Stefan Bender

Distributor
  • Posts

    149
  • Joined

  • Last visited

Posts posted by Stefan Bender

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

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

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

     

     

     

     

     

     

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

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

  6. Dear developers,

    in a QTO function (EQTOFunction::ObjectData, VWWSFunctionCall_EventSink::MyFunction(const SDispatchContext& context,  VWVariant& outResult)

    our plug-in returns a VWVariant of type eVWVariantType_Bool (i.e., outResult = VWVariant((bool)(true/false));

    But in the worksheet cell, no boolean value (localized true/false string) is displayed but only the number (1 for true, 0 for false). Imho this is a bug. A number should onmly be displayed if VWVariant is one of the numbers type. If VWVariant is of type bool, the cell should treat it as bool and display it as such. 

    Do I need to submit a bug or is this WAD? If WAD, how else can I make sure that the actual bool value is displayed instead of a number?

  7. Dear developers,

    we are adding some qto functions ('ObjectData') to a few of our PIOs. These plug-ins are meant to be used in different countries so they should be easily localizeable.

    Some of these QTO functions are a little complex and require more than one parameter.

    Some of these parameters must be strings from a given list, like parts of the plug-in or words like "interior" or "exterior".

     

    Let's say a function allows three additional parameters

    ObjectData('keyword',<param1>,<param2>,<param3>)

    and the string in the Opt Desc.vwstrings file would be 

    "ObjectData-keyword"      = "Objektdaten('keyword';<param1>;<param2>;<param3>)";

     

    A sample would be:

    "ObjectData-doorhandletype"      = "Objektdaten('DoorHandleType';<InteriorOrExterior>;<NoOfLeaf>)";

     

    How can we make sure that users may use a localized version of 'DoorHandleType' or 'Interior/Exterior' when calling this?
    And how can we make sure that they see these localized names in the function description?

    And how can we define a list of valid localized options for <param1> and <param2>, in case of the sample the localized versions of "Interior" and "Exterior"?

     

    In theory, it is possible to support localized options, but all potential solutions would require more string files and  a manual synchronization between these string files and the  strings in Opt Desc.vwstrings and Opt Desc DB.vwstrings. It is very likely that localizers will fail to do this correctly and thus the localized versions of the PIO will fail or display an incorrect description.

     

    So my question is if there is a proposed workflow for such a synchronization, maybe some additional strings in OptDesc.vwstrings or something? I think there should be some sort of universal and localized name for function options and also for each parameter. The localized names should be stored in a localizeable string file and be used by VW when displaying the function descriptions. Or does this sort of workflow already exist?

     

    Thanks for any help,

    Stefan Bender
     

  8. Dear developers,


    There are requests to quit a VWDialog during  an ADD_LB_DIRECT_EDIT() event (i.e., when direct editing a list browser cell). The main idea is that if the user selects a custom SResource control (i.e. button button "New" or "Edit..." instead of selecting a resource) in a direct editable resource browser cell of a listbrowser, the dialog should close down and the user enters symbol edit mode.

    We could do this in "normal" dialog events by setting the item to 0, but how is this possible in a direct edit event?

    Or is there another way to force a dialog to quit? I tried CloseDialog(true), but no effect.

     

    Thanks for any help,

    Stefan Bender 

  9. Hi there,

     

    what is the recommended way for a PIO to offer information about the materials of certain components (window frame, glass, shutter...) to the data tag of to worksheet functions? I'm thiunking of a solution that does not require Psets or record fields with names  of materials. Are there any special qto functions or interfaces for that? Is there a PIO that is actually doing this?

     

    Thanks for any help,

     

    Stefan Bender

  10. Dear developers,

     

    does anybody have an idea how I can center an image in a list browser cell? I tried 

     

    VWListBrowserItem vwi = lb->GetItem(ind_line, ind_column);

    vwi.SetItemTextJustification(kItemTextJustificationCenter);

     

    but no effect. I couldn't find any other functions. 

     

    Thanks for any help,

     

    Stefan Bender

     

     

    806627516_listbrowserimagenotcentered.png.82578ea977d2132ebe358ab415db75fa.png

×
×
  • Create New...