Hello Jeremy,
Thank you for your suggestion about being required to click the Save button in addition to clicking the update button. My assumption was that the update button committed the change. Clearly that was a bad assumption on my part. The good news is I'm past this now and can move on.
For GHL, I'm a Sr. Software Developer at Microsoft and I'd like to propose a suggestion or two. I'm not trying to be anything other than helpful so I hope that these suggestions will be forwarded to a stakeholder at GHL.
1- Consider combining the actions of the "Update" button and the "Save" button into a single "Save" button. A single "Save" button can perform many actions and is all that is required for this page from a programmatic standpoint. In a typical page such as this, all variables are first read from the P4 device and written to memory before they are displayed to the user. If the user changes one or more values and then clicks the Save button, the changed state is detected automatically before the change is committed.
2-Consider introducing a confirmation dialog that shows the proposed change and includes an OK/Cancel button combination. This provides the opportunity for the user to confirm their actions before they are actually saved.
The interface currently lacks both capabilities and requires redundant and unnecessary steps to successfully configure the P4/powerbar the first time. The current style of programming is causing customer confusion and creating an unnecessary number of support cases at GHL. The end result is costs are increased and customer satisfaction is lowered, which drives down future sales. If you would like additional feedback or code samples, please feel free to contact me directly.
Thanks