I'm circling the drain on figuring out how to use the action config page stuff, have posted a few things here, added one issue on GitHub, and I've had exactly ZERO input. Pretty disheartening.
Announcement
Collapse
No announcement yet.
Is HST helping us with plugin stuff anymore?
Collapse
X
-
Originally posted by kriz83 View PostI'm in the same boat- New input contents/changes are lost when a dropdown is changed.
- Dynamically removing a view from the page doesn't work.
- My HS3 plugin used multi-select checkbox dropdowns, which don't exist in HS4.
- I want to control the formatting of the controls better (like having "height" x "width" input boxes on the same line!) but can't.
Comment
-
Originally posted by shill View Post
Also actions? Happy to compare notes if there's something you're stuck on. My problems are:- New input contents/changes are lost when a dropdown is changed.
- Dynamically removing a view from the page doesn't work.
- My HS3 plugin used multi-select checkbox dropdowns, which don't exist in HS4.
- I want to control the formatting of the controls better (like having "height" x "width" input boxes on the same line!) but can't.
I create a new Pagefactory and process the existing pagefactory (if not first time called) with the configviewchanges and apply those to the newly created Pagefactory. If you want to remove a view, I won't include it again. When done, I take the newly created PageFactory to overwrite the existing. It will fix your item 1 & 2 above.
I use a GroupView if I want to do multi-select HOWEVER there is a bug that has prevented me from using it. It is logged as issue PSDK-57. This is my solution to your issue 3.
Hope this helps, I can post code but I have to admit, when I looked at my own code, it wasn't very simple because I use perhaps too many actions that have a tree of attributes and the attributes are different depending on which "path" is being followed.
Comment
-
Thanks. I'm sure I could work around the fact that "RemoveViewByID" simply doesn't work by replacing the entire Page, but that seems like overkill. If it comes down to it, I will but it shouldn't be necessary. I also don't think it will fix item 1 - the input text is never posted back, so I couldn't manipulate the inputview in the new Page to add the text since I don't know what it was yet.
I don't quite understand how the ViewGroup (I assume that's what you meant) would help replace that - the one time I used it it simply seemed to add an extra label above the fields. It's simply not viable to list hundreds of devices in a vertical list that can't be collapsed...
Comment
-
Originally posted by shill View PostThanks. I'm sure I could work around the fact that "RemoveViewByID" simply doesn't work by replacing the entire Page, but that seems like overkill. If it comes down to it, I will but it shouldn't be necessary. I also don't think it will fix item 1 - the input text is never posted back, so I couldn't manipulate the inputview in the new Page to add the text since I don't know what it was yet.
I don't quite understand how the ViewGroup (I assume that's what you meant) would help replace that - the one time I used it it simply seemed to add an extra label above the fields. It's simply not viable to list hundreds of devices in a vertical list that can't be collapsed...
Comment
Comment