Developer Portal Community

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Interfaces at CPS

    Interfaces at CPS

    Despejo47
    Established Member

    Hello all,

    I have some questions and suggestions about use of interfaces in CPS. Use a Interfaces is a successful history between Peripherals and Units. We can extend this functionality to make easy handling between Units and CmdHandlers too and increase the standardization level.

    Question

    1- It's is possible to define more than one interface in a Code Entity?

    Despejo47_0-1712214622811.png

    Suggestion add more functionalities on CPS to extend the use of Interfaces.

    Could be interesant to have in CPS...

    ... possibly to declare an interface as a CodeEntity (not necessary to declare Methods and properties).

    ... a possibility to set interface implementations in CmdHandlers.

    What are your opinions?

     

    Best regards

    1 REPLY 1

    nexidator
    Community Moderator
    Community Moderator

    You can define more than one interface by separating them with a pipe sign (|).

    I don't think it would be a big benefit to declare interfaces in CpStudio. If that was possible, you would expect to link a dynamic number of interfaces at the implementing FB, which would be a technical problem. (The data layer we are using does not support lists of references to other data objects.) The way it is now is not very comfortable, because you can misspell interface names, but I would say it works well enough.

    I understand the requirement to add own interfaces to the declaration of object-defined FB types.  At the moment, the Interfaces property is editable for project-defined FBs but not for object-defined ones because every time when the object definition is reloaded, the Interfaces property is updated with the information from the object definition. If the user can add interfaces to object-defined types, CpStudio would need to remember which interfaces came from the object definition and handle them somehow separately. I don't say that's impossible, but it would be some implementation effort, so it would be interesting to know how useful this feature would actually be.

    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