Here is a list of the changes:

- Removed toolbar scrolling panel due to many requests from users
- Added yearly archive view
- Minor bug fixes

Let me have your feedback as usual, enjoy!

Developing it was much easier than I thought and I decided to make it public, publishing it on GitHub.

The result is a simple yet highly customisable numeric keyboard for iPhone. Uses ARC. Currently does not support rotation, you are more than welcome to implement it. Includes some input checks to allow only 2 decimal digits, but you can easily change those checks to allow whatever input suits your app.

Some days ago the control has also been accepted in the Cocoa Controls list, which is another site I use to visit often to avoid re-inventing the wheel every time. Thanks.

An automatic segue is created in IB by dragging from a (prototype) table cell or other control. The nice thing about it is that it’s, well, automatic — tapping the control performs the segue, and all you need to do in your code is implement prepareForSegue:sender: so that the destination view controller gets the right data. The downside is that any given control (including prototype table cells) can only have one outgoing segue (otherwise, the storyboard wouldn’t know which to automatically perform).

A manual segue is created in IB by dragging from the source view controller. The upside to this is that a view controller can have multiple outgoing segues. On the other hand, they aren’t associated with a tappable control, so you have to implement logic that determines which to perform when (and calls performSegueWithIdentifier: to make it happen).

Given those tradeoffs, there are two possible ways to implement multiple segues from the same UITableView:

Use multiple prototype table cells — then each can have its own outgoing automatic segue. You’ll need to change your table view controller’s tableView:cellForRowAtIndexPath: to check the index path’s section number and choose the appropriate identifier for dequeueReusableCellWithIdentifier:, but this might make things more convenient or efficient if your trend and story cells have different content anyway.

Use manual segues. Then your table view controller can implement tableView:didSelectRowAtIndexPath: to call performSegueWithIdentifier: with the appropriate identifier chosen based on the index path’s section.

Here is a list of the changes:

- iOS6 and iPhone5 compatibility upgrade.
- Application icon and user interface restyle.
- Reverted to bar navigation and portrait only orientation due to requests from many users.
- Added toolbar scrolling panel activated by navigation bar item and pull/release gesture.
- Added yearly view in home.
- Added Italian localization.
- Minor bug fixes.

Let me have your feedback as usual, enjoy!