RoboDS First Test

[raystubbs]

Originally Posted by lopsided98

You released the app?

I sent the apk to those who wanted to test it, but I haven't heard back from them so I don't know if I should release it or not.

[Ben Wolsieffer]

Originally Posted by raystubbs

I sent the apk to those who wanted to test it, but I haven't heard back from them so I don't know if I should release it or not.

I thought I sent you a pm saying that I would be willing to test it, but I just looked and I guess it never got sent. I'm still willing to test it, though, if you want.

[raystubbs]

Just a reminder, I don't know if any of you have artists on your team, but if you do I can put your custom artwork into RoboDS widgets. If you want me to integrate your art just post it here or email it to me.

[raystubbs]

I know that other teams are working on other DS projects, if anyone needs the protocol let me know.

[Whippet]

Team 4301 has some beta test results:

Motorola Moto G (2nd Gen):
-Functional
-Occasional app crash related to adding joysticks. We haven't been able to reliably reproduce it. It just happens sometimes, and not very often.

Samsung Galaxy S5 and S6:
-Functional with no issues.

iPhone 4s, 5, 5c, 5s, 6+:
-Does not install
-Better programming training implemented for mechanical students.

[raystubbs]

The app is only for Android, it is not expected to work on any apple devices. Thanks for the test results.

[Whippet]

Originally Posted by raystubbs

The app is only for Android, it is not expected to work on any apple devices. Thanks for the test results.

That was the point, we needed to implement better programming training for our mechanical members so they would know that.

[raystubbs]

Originally Posted by Whippet

That was the point, we needed to implement better programming training for our mechanical members so they would know that.

Oh, OK, I thought you were serious. Sorry.

[raystubbs]

I'm graduating so after today I will no longer have access to a RoboRio, so I wont be able to test the app anymore. I'm gonna clean up my code a little and try to add some features, which will not be tested, then I'll put the code up on github if anyone wants to pick this project up. Sorry I was unable to finish it, and I'll keep trying to add features, but everything I do from here on out will be untested so if anyone wants to test or develop, I'll post a link to the github repo in a few days.

[Ben Wolsieffer]

I installed the app on my Galaxy S4 running 5.1.1, and tried to control our robot, but I ran into a few problems.

Here is a list of the problems I could find, in rough order of severity:

• IP address setting does not save when changed. I'm not sure if the IP address is actually being changed, but when you open the settings dialog, it is still set to the default and I was unable to connect to our robot.
• The same thing happens with the portrait/landscape setting, therefore I cannot create a portrait layout.
• Joysticks seem to be in editing mode when the app is started with an existing layout. They turn green when touched instead of allowing control. Workaround: enter and leave editing mode.
• When editing fields in the joystick and button creation dialogs, the first digit of each number field is not shown in the editing popup, and the none of the characters of the text fields show up. Interestingly, backspace will delete the these characters even if they are not shown.
• The bottom of the joystick creation dialog is cut off in the landscape orientation. Could be fixed by making the dialog scrollable.
• Pressing and holding on a joystick while driving causes the phone to vibrate.
• The bottom two editing drawers are cut off somewhat in landscape.
• It might be a good idea to allow only one drawer on the editing screen to be open at a time.
• Loading and saving multiple layout doesn't seem to work; there is no way to create a new layout. I'm not sure if this just hasn't been implemented yet.
• The joystick creation dialog should probably be initialized with sensible defaults.
• "Comming" is misspelled in the bottom two drawers of the editor.
• "Partrait" is misspelled in the layout settings.

I can upload some screenshots if you want. I hope this is helpful.

[raystubbs]

Wow, that sounds pretty bad. I have already listed some of these bugs, like portrait mode not working and only one layout. But I haven't heard o fthe others yet. Some screenshots would be extremely helpful and you android device also. Sorry for the UI mistakes, I'm guessing you are using a phone, I only have s 7" tablet to test on.

[raystubbs]

Originally Posted by lopsided98

• IP address setting does not save when changed. I'm not sure if the IP address is actually being changed, but when you open the settings dialog, it is still set to the default and I was unable to connect to our robot.

This is something I can work on. I never tested if the IP saved or not because the default IP is my robot's IP. I just tested the app on my device and found that it does not save, so I'll have that fixed in a few minuts, but my not have the time or internet access to upload it for a while, 'cause I'm going home to Mexico for a week.

[raystubbs]

Originally Posted by lopsided98

• Joysticks seem to be in editing mode when the app is started with an existing layout. They turn green when touched instead of allowing control. Workaround: enter and leave editing mode.

Does this happen every time you start the app? If not can it be reproduced? I used an android feature to switch back from edit mode, but this feature is only available in higher APIs, is your android device version 4.1 or higher?

[Ben Wolsieffer]

Sorry if I sounded overly negative in my last response. I'm just trying to suggest ways to improve the app.

My phone is a Samsung Galaxy S4 running Android 5.1.1, the absolute latest version, so it definitely has every API you use.

The editing bug occurs every time the app is cold started (ie. it has been deleted from the recent apps list), but not when the app is minimized/backgrounded and then opened again. When the app is minimized and then opened again, the joysticks start working as intended.

I attached screenshots of some of the bugs:

• drawer_cut_off.png: Shows the bottom editor drawer being cut off by the bottom of the screen.
• editing_bug.png: Shows how the joystick can be selected and turn green when not in editing mode.
• field_editor.png: On phones (I'm not sure if this happens on tablets), an editor pops up when a field in the joystick/button creation dialogs is selected. The field actually contains "-1", but the editor does not show the "-", so it appears as "1"
• joystick_dialog_cut_off.png: Shows how the last few fields in the joystick editing dialog are cut off by the bottom of the screen. It is still possible to edit them though, by pressing next in the editor.

If you release the code, I'll take a look and it and see if I can help with some of the bugs.

[raystubbs]

Originally Posted by lopsided98

Sorry if I sounded overly negative in my last response. I'm just trying to suggest ways to improve the app.

My phone is a Samsung Galaxy S4 running Android 5.1.1, the absolute latest version, so it definitely has every API you use.

The editing bug occurs every time the app is cold started (ie. it has been deleted from the recent apps list), but not when the app is minimized/backgrounded and then opened again. When the app is minimized and then opened again, the joysticks start working as intended.

I attached screenshots of some of the bugs:

• drawer_cut_off.png: Shows the bottom editor drawer being cut off by the bottom of the screen.
• editing_bug.png: Shows how the joystick can be selected and turn green when not in editing mode.
• field_editor.png: On phones (I'm not sure if this happens on tablets), an editor pops up when a field in the joystick/button creation dialogs is selected. The field actually contains "-1", but the editor does not show the "-", so it appears as "1"
• joystick_dialog_cut_off.png: Shows how the last few fields in the joystick editing dialog are cut off by the bottom of the screen. It is still possible to edit them though, by pressing next in the editor.

If you release the code, I'll take a look and it and see if I can help with some of the bugs.

Thanks a lot. You didn't sound overly negative, I was expecting to have some problems with smaller screens. Your feedback really helps. I've now fixed the IP and orientation settings. The problem is that I cannot reproduce your editing bug on my device, so that may take a bit longer to fix. I would love to share the code and get some help, but unfortunately it is extremely ugly. I was in a hurry when writing it so I got really messy. I don't think you want to go mucking through it. Thanks again for the info, it will really help.