I've been working on the Vortech memory changing from Vortech page today. I've got it working. The way it works is this...
- Swipe to the Vortech page
- Long press on the VALUE being display. If you want to change the Mode, you long press on "Constant" (or whatever is displayed).
- The long press displays a popup that displays the appropriate options. For Mode, it displays the list that I previously posted. For Speed, it displays 0-100% in a list. For Duration, it displays 0-255 in a list. The lists are not set based on the current value. If this functionality is desired, I'm sure I can figure out a way to handle it.
- Press Update for the value to be updated. It does not care if you set it to the existing value, whatever value is selected is what will be set. You will see the "Last Update" status text change as it is sending the command. It "finishes" with "updating display" but I thought about changing it to something different. More about this later. And it also displays a Toast popup stating whether the command was successful or not (just like the current memory page does).
- OR you can press Cancel to return to the page.
Before I get to the main question, I have a question about triggering the popup.
Should the popup be triggered by long pressing on the LABEL (Mode, Speed, Duration) or the VALUE (Constant, Tidal, 100%, 0%, etc)? I originally coded it for the label but then changed it to the value. Doesn't matter to me, but I want the input from people who will use it.
Now, I have a question on how the app should behave after the update command is sent. Currently, the display text will read "Updating display" when the command is completed (like I stated). I have a couple options that I can do. I do not care which one is chosen. I just want it to behave like everybody thinks it should.
So, here's the options:
- Last update status changed to "Command Response: STATUS" and display whatever the controller says back. The values are not updated on the page so the old values will still be shown until the controller is refreshed again.
- The display is refreshed to display the LAST SUCCESSFUL UPDATE values and you get the Toast message that says "OK" or "ERR" from the controller. The old values still remain until you refresh again (like the previous option).
- The app initiates an Update / Refresh from the controller after a successful response from the controller. You get a Toast message that says "OK" or "ERR" from the controller. The values are updated right after the command was sent out.
My comments are as follows:
Option 1: Good that it shows the status. No popups are displayed. Bad because the data is not refreshed so you have to manually refresh to see the new values. Good because the controller is not queried immediately especially if you are updating multiple options like Mode and Speed.
Option 2: Same response as Option 1 except the popup is nice to see and behaves how the current memory updating does for consistency. The updated text line is returned to the last updated time so you can easily see the time associated with the values.
Option 3: Great for immediately showing the values and displaying a popup message to keep consistency with the memory updating. Bad because the controller is queried immediately and sometimes querying too fast can cause problems. Bad because it will take longer to make more changes if you are changing both Mode and Speed.
I am initially inclined to code in Option 2. However, Option 3 does sound very logical to me as well. Like I said, I do not have a preference on this one. It can be coded either way. In fact, I could even put in a setting that you can control how you want the behavior to be: Option 2 or Option 3. (Yeah, I'm not a fan of Option 1 but I still wanted mention it).
With that being said, I'm ready for the feedback. Oh, and I almost forgot.....some screenshots for your viewing pleasure.
![Smile :)](./images/smilies/icon_e_smile.gif)
Here's 2 screenshots for changing the Mode:
![Vortech Config Popup for Mode displaying list](./download/file.php?id=683&sid=65946402e0914210744f3119e4435a18)
- Vortech Config Popup for Mode displaying list
- VortechConfigPopupList.png (39.56 KiB) Viewed 6403 times
![Vortech Config Popup for Mode](./download/file.php?id=682&sid=65946402e0914210744f3119e4435a18)
- Vortech Config Popup for Mode
- VortechConfigPopup.png (44.38 KiB) Viewed 6403 times