Developer Portal Community

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 
    SOLVED

    CM Addon forces ViewRequest variable

    CM Addon forces ViewRequest variable

    CtrlDiogoC
    Established Member

    Hello,

    I have an issue: whenever I want to show a dialogue in the HMI, the requested view is always the unit where the CM addon is placed.

    CtrlDiogoC_0-1730830520832.png

    How can I disable this behaviour? It's preventing me from doing the UserGuidance for the MES@AE changeover sequence, among other things.

    CtrlDiogoC_1-1730830660593.png

    Thank you in advance.

     

     

    2 REPLIES 2

    nexidator
    Community Moderator
    Community Moderator

    Sorry, but I don't really understand what's happening. What is your source code for requesting the dialog? Which variable is configured as dialog variable on which handler?

    The HMI works like this:

    • On every object, you can configure a string variable that is used to request dialogs. When writing a view name to the variable, the view is found in the scope of the object where the variable was configured. (Technically, this is not necessarily the unit that the variable belongs to.) It is possible to request dialogs of sub-units using a logical path like 'SubUnit/MyDialog'.
    • When a new dialog is requested, the HMI will navigate to the object where the respective dialog request variable was configured. This is not necessarily the object owning the dialog view when using relative paths.
    • If the same object is currently requesting a view that is visible in the functions section, the HMI will switch to that view and display the dialog in front of it, assuming that the view and dialog are somewhat related as the same object (maybe even the same sequence) is requesting them.

    Hello,

    Thank you in advance for your reply.

    I later found the issue. It had to do with the View and DialogRequest variables. I had only created one variable for each and used them in the HMI configuration of the different units.

    I then created different HMI variables for each unit and solved the issue.

    Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist