NOOB Question: Webapp customization

[kevin]

1. Don't see any screenshot attached, but I think I understand what you mean
2. What IOS version is your iPhone 5 running? We don't have one, just an iPad running IOS 7+
3. Positioning will fix that - the dialog is actually confirming a touch of the 'F4' button, so this will have to be moved a bit anyway.

Hey Kevin,

I updated to the new dev version using the git command and now have the custom button feature. Thanks so much for adding this! I was able to create 2 buttons to open and close both my garage doors!

A few observations and issues that I have seen:

1. The "Custom Buttons" icon is a bit too small on the iPhone 5 and also a bit too close to the bottom row of keys (see screen shot). Can you make it a little bigger and maybe in a different position?
2. I cannot get the custom buttons button to work on the iPhone5 (when pressed nothing happens). iPad and computer web browsers work fine
3. The icon to close the custom buttons is a bit hard to activate on the iPad. Would it be possible to make it bigger? Also when I am able to get it a confirmation dialog window opens asking me if I am sure, is that the way it is supposed to work?

I am still doing some testing with it but overall I love the ability to create these buttons. Thanks again for all the hard work and great communications!


Andy

[ando1]

Thanks Kevin,

Yeah I think I forgot to attach the screenshot but it sounds like you know what I am talking about. Bot iPad and iPhone are running iOS 8.1 (laters version)


Thanks,
Andy

[kevin]

The custom buttons don't work on the iphone or the whole keypad doesn't work?

If you can give me an example of how they're not working on the iphone that would help, as we only have an ipad and it functions correctly

[kevin]

On our local branch here, I have done some changes with regard to this - on ipad devices the button is larger and more accessible and in a new position

On mobiles, once you hit the custom buttons button - everything else disappears except the custom buttons - once one is pressed or 'exit' is clicked, everything else shows back up - this will prevent clicking of items beneath the dialog, especially on android devices where this showed to be a real issue. I have confirmed this feature works 100% on my mobile android phone, but we do not have iPhone so I can't test there - no reason it shouldn't work as iphone and ipad are really the same kind of code ... we'll have to see.

[ando1]

Kevin,

OK I was able to finally get it to work on the iPhone. What was happening was when I touched the "Custom Buttons" button on the iPhone the window with the newly created buttons was not appearing. After playing around with it and trying to touch it just right I was able to make the window appear. It was quite hard to get this to happen. The buttons on the iPhone appear to be a bit different as well. I have posted the screen shots from the iPad and iPhone so you can see what I am talking about.

Andy

[kevin]

There's a lot more real estate on the ipad for display purposes so we were able to position it in a nice slick manner

Phone screens being so limited in real estate without having to adjust zooming or forcing scrolling the box needed to be squished a bit - we're trying to not make it device specific, but in some places we'll have to do some things specific for IOS displays.

In the next update, the buttons will be the only thing that shows - in the center of the screen - (along with alarm status) to avoid misclicking anything on phone devices - as soon as you close the panel or touch a button, it will disappear and re-show all the other controls.


I will see what I can do to the button styles to fit better on iphones.

[kevin]

I have increased the size of everything with regard to custom buttons to make everything easier to press. When it gets pushed to github you will be prompted to update and hopefully you enjoy!

[ando1]

Thanks Kevin!

Looking forward to tring out the new version.

Andy

[kevin]

Since it's just cosmetics, I'll see if Scott will post it to github tomorrow.

Thanks,
Kevin

[kevin]

Just to let you know - this has been pushed to our github and you should be able to update.