Asked — Edited
Resolved Resolved by Steve G!

Multiple Screens On Mobile App

So I'm running out of real estate on my tablet for my EZB mobile app. I was looking for a way to have an extra screen that I can toggle between on the same mobile app, so I can have one set of buttons on one screen, and another set of buttons on the other screen.

This is not an issue on the PC edition, as I can use the Script Manager and run as many programs / routines as I want to. Does anybody know of a way to do this?



Upgrade to ARC Pro

Experience early access to the latest features and updates. You'll have everything that is needed to unleash your robot's potential.

United Kingdom

The only way I know how to do something similar that may help you, is to toggle between the mobile interface and "desktop" screens on the app. When on desktop, you can press in a control which expands the control and shows al the buttons for it.

When your mobile interface is showing on the screen, swipe up to show options, then his "Desktop". Or you can press "Controls" which will show all of your project control options.

Not all of your project controls may work on the mobile app though (and you will get a warning saying as much), as they may not have been implemented for mobile use yet, such as speech recognition.


Thanks Steve, that would be great if the script manager worked on the desktop page of the mobile, only it doesn't right now.

I was concerned about making smaller buttons that I wouldn't be able to read them, but I guess I can color code them in order to tell what is what, then with smaller buttons I can have a little more functionality.

Thanks again.


In reading over my post I wanted to make sure it wasn't taken as sarcastic, as I didn't mean it that way. I really am grateful for you input, and was hoping I had missed an easy way to do this.

Thanks again for your help and not leaving me in the lurch.

United Kingdom

Hey, no worries. I didn't take it as sarcasm anyway.:)


I may be completely wrong about this but doesn't Windows 10 now support expanded window view and multiple desktops? I just upgraded to 10 the other day on my laptop and I thought I saw this feature advertised during the upgrade process. I know it doesn't work on the Surface Tablet but Win 10 should work on phones and win based tablets I think. If so this may be of help to you.


Currently I have windows 7 on my pc & android on my phone and Android on my phone & tablet, but I'll keep that in mind if I upgrade anything.



Make multiple mobile interfaces.

Now look at the cheat sheet. See there's a "show()" for each of them? Select that for your buttons.

There's also a return or back or close or something. Not in front of my PC to tell you but take a look and you'll see. The manual explains it as well:)


Perfect, exactly what I was hoping for! Thanks so much.


Anthony(xlrobots) made an app that has a directory using multiple mobile interfaces.

United Kingdom

That's an even better solution. I must admit that I missed that one and didn't know you could add multiple mobile controls. Good to know.


Very cool, I haven't had time this weekend to try the show command yet, but Anthony's app is what I wanted to do, as I wanted to be able to pre-program several subroutines that I can call manually, this will be great!


I think I will be able to get this going now, but thanks Anthony for offering to help with the setup.


So what type of a command would be in your script for the button?


r1d1, to avoid confusion from Anthony's response - he indeed uses the ShowControl() command, which is available in the Cheat Sheet. The ShowControl() can be used for any control in ARC which supports a mobile interface. You can see the list of supported controls by pressing the ? (question mark) on the Mobile Interface Builder.

The only way to show a control on the mobile app programmatically is to use the ShowControl() command.

I recommend adding back buttons to return from the control so you do not create a huge breadcrumb stack. You can close controls with CloseControl(). The EZ-Script manual explains further detail.


Thanks DJ for the clarification, I was a little confused, and thanks Anthony for the idea