Search Results for

    Show / Hide Table of Contents

    Plugin SDK v1.4.3.0 Release Notes

    Required HS Core Version

    This release is focused on updates to the JUI framework to improve performance and make it more flexible. This includes backend changes to the way data is managed for events.

    • Changes to GridView
      • GridViews with SelectListViews inside of them were not behaving correctly in event actions and triggers. GridViews should now behave as expected. (PSDK-291) (#314)
      • GridRow.HorizontalAlignment and GridRow.VerticalAlignment properties have been added to allow you to change the content alignment within a GridView GridRow. Use the enums EHorizontalAlignment and EVerticalAlignment. (PSDK-295)
        • Add GridRow.HorizontalAlignment
        • Add GridRow.VerticalAlignment
        • Add EHorizontalAlignment
        • Add EVerticalAlignment
      • GridViews did not align with other views correctly due to some extra padding being added into their HTML. This padding has been removed to better align the view on pages. (PSDK-297)
    • Changes to SelectListView
      • Add SelectListView.UseOptionKeyAsSelectionValue to allow SelectListView to use the option key as the value of the option in HTML (PSDK-299)
      • Include OptionKeys in SelectListView when posted back from HS in OnDeviceConfigChange (PSDK-101) (#124 #201 #223)
    • Change how plugin triggers and actions are saved to events.json. Previously, the whole page (i.e. collection of JUI views) was serialized and saved to events.json. This was causing some problems for select lists that contain dynamic data (such as a list of devices) because the entire select list is loaded from JSON and no call to the plugin is made to refresh it. Now, we only save a list of key/value pairs to events.json, where the key is the id of the view and the value is the return from AbstractView.GetStringValue() (the same thing as the dictionary returned by Page.ToValueMap()), and rely on the plugin the provide the translated list of key/value pairs to display to the user. This behavior is automatically handled using AbstractActionType and AbstractTriggerType, and AbstractActionType2 and AbstractTriggerType2 have been added to allow you finer control over this behavior. The sample plugin has been updated to include an example of this; see the "Write Device PED to Log" event action. (PSDK-298) (PSDK-303)
      • Add AbstractActionType2
      • Add AbstractTriggerType2
    In This Article
    Back to top HomeSeer Technologies