Revisiting widget.newNavBar tutorial for iOS7/8 - button target too wide

Solar2D General Questions/Discussion
#1

All - I’ve been using a version of Rob’s very useful widget.newNavBar extension to create simple text buttons for iOS 7/8 style navigation, pretty much as originally explained in this tutorial:

http://coronalabs.com/blog/2013/12/31/tutorial-extending-widgets-with-a-navigation-bar/

When built with 2014.2393 (current public version) it seems like the tap/press target area for text buttons is huge, far wider than the actual text button area should be.

To see the effect in action pull down the original tutorial demo project and build - clicking anywhere on the right 2/3 of the title bar flashes the ‘Add’ button.  

Original demo project:  https://www.dropbox.com/s/xnde9ttvz2htom7/NavigationBar.zip

After quite a bit of puzzling over and testing of the code in widget.newNavBar it seems that widget.newButton creates a much wider touch area than it should for text buttons and I don’t know why.  Image buttons (like the “back” button) in the example have a width parameter and the target area seems to match for them, but I can’t see how to do the same thing for text buttons.

Ideas?  Rob, others?

Thanks!

Dan

#2

Add this line:

                textOnly = true,

after line 108 of widget_newNavBar.lua

Rob

#3

The magic doesn’t get any simpler that that!  Thanks so much!  It works exactly as expected now.  Did I miss this in the original tutorial somewhere or was this more the product of the platform’s evolution after the tutorial was written?

In any case, thanks again.  Can we mark this as solved?

Dan

#4

You probably didn’t miss it, I probably did.

Rob

#5

Add this line:

                textOnly = true,

after line 108 of widget_newNavBar.lua

Rob

#6

The magic doesn’t get any simpler that that!  Thanks so much!  It works exactly as expected now.  Did I miss this in the original tutorial somewhere or was this more the product of the platform’s evolution after the tutorial was written?

In any case, thanks again.  Can we mark this as solved?

Dan

#7

You probably didn’t miss it, I probably did.

Rob