New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SubActionTypeNames missing? #69
Comments
Anyone cheking in now and then on the issues here? This one is a show stopper for the conversion of action for my plugin? |
You will have to handle SubActionTypeNames manually. The HS3 code has SubTriggerTypes integrated directly into the workflow, but Actions were never completely integrated in the same way. The SelectedSubActionIndex is for backward compatibility only right now because that information would otherwise be lost. The documentation will need to be updated to properly reflect this. Your best bet is to ignore it and manually handle it like another select list on your page because it is not processed automatically like the Triggers are. |
There was no suggestion to leave users hanging in any way; so I'm not understanding your position here. There is no functionality to convert from the perspective of the SDK. Sub-Actions were never implemented in the same way as Sub-Triggers as is evident by the existence of legacy members like I have done exactly what I am recommending for the Z-Wave plugin, and have run into no issues with it as a solution. Unless you are converting a legacy action you should be ignoring the I closed this issue because there is no action item for it in terms of development necessary within the SDK at this time. The functionality was ported exactly as it was and verified to be working as expected. This is an improvement that we can look at moving forward; at which time we can reopen the issue. |
@jldubz , Jon, Here is all the code I needed in the hs3 version to show the magic window I posted in my earlier post: `Region "Action Properties"
` All entries were prepared in the sample plugin for HS3. This resulted in the above image, which I did not have to program other then catching the SubActionNumber. Really, the plugin here is ready to show to users, including the conversion, except for this step. In ZWave also subactions are shown in HS3. What is needed other then the above code to use it in HS4? Wim |
Had a good night sleep and rechecked again this morning. Went over it several times in the past few weeks. But indeed, found it finally, I created this list myself! Thanks! |
I am testing what you described, earlier: Unless you are converting a legacy action you should be ignoring the SelectedSubActionIndex. I am now trying to convert the actions and helas, the SelectedSubActionIndex is always 0. In the HS3 plugin the ActInfo.SubTANumber is set and works fine there. It appears as this number is not copied to SelectedSubActionIndex. Tried to guestimate the SubTANumber by looking at the fields that are set, but I have a challenge with 3 of the actions as they all contain the same fields, so I really would need this value? Any suggestions on this? |
Merge in HSPI/plugin-sdk from release/1.4.0.0 to dev * commit '6cce84830efe7eb08b9d0f59a0c0a5fd88f0542f': (71 commits) JLW mark nuspec version as release candidate JLW add navigation button to sample plugins Removed the & symbol from some documentation PSDK-221 JLW ignore ID validation test in AbstractViewTests until there is more clarity on how invalid IDs should be handled. See PSDK-261 for more. PSDK-218 Fix InputView date and time implementation PSDK-258 JLW add check for invalud Rows on TextAreaView. Update associate unit tests PSDK-221 JLW remove invalid unit tests now that the SelectListView Selection property can never be set to an invalid value. PSDK-257 JLW add a selection check on set to the SelectListView PSDK-259 JLW fix formatting PSDK-260 JLW check value on InputView everywhere it is set PSDK-259 JLW check name in all InputView constructors PSDK-218 JLW add a space to the InputView date and time classes PSDK-218 JLW add InputView date and time implementation. DateTime still needs to be done. PSDK-234 Fix references to the deprecated AbstractHsDevice.Status in docs. Fix HsFeature.Duplicate() and HsDevice.Duplicate() methods. Fix docs for EProperty.DisplayedStatus and EProperty.StatusString PSDK-213 Add ESelectListType.SearchableDropDown select list type. Jui/Views/SelectListView.cs edited online with Bitbucket PSDK-244 JLW moved updated docs to remarks PSDK-192 JLW Add unit tests for AddNamed<TData>, AddUnNamed<TData>, GetNamed<TData>, and GetUnNamed<TData> PSDK-138 JLW move TestData class to project root so it can be used by any tests. PSDK-240 JLW update RemovedUnNamed documentation ...
I am trying to get the actIons and subactions to work in HS4. But although I do find a "SelectedSubActionIndex" property, I cannot set the names with something like "SubActionTypeNames". How should this work?
For triggers creating a list for "SubTriggerTypeNames" works fine, but it seems to be missing for actions?
The text was updated successfully, but these errors were encountered: