- In earlier versions of AppFurnace, the af.openLinkInWebBrowser function would always open your links in the Safari browser. This meant that your app would stop running, and it was quite fiddly getting back to the app (you needed to press home, then double-tap home, then select your app).
- In 2.3, all links will open in a special browser inside your app - so your app will carry on running in the background. To get back to your app, the user simply presses the Done button. If your user really wants to view the content in Safari (for instance they want to set a bookmark or add the page to their home screen), there's an open in Safari button they can press.
- You can now click @mentions, #hashtags, and http://links in Twitter messages. This is optional - set the allow links property on your Twitter widget to use this new feature. The links will be opened in the new embedded browser.
- You can now create links in your RichText widgets. Use the syntax [Text of the link](http://www.example.com/mypage). Again, these links will open in the embedded browser.
Note that in order to use the new links you'll need to update Calvium Player to the new 1.30 version, now available from the Apple App Store
IMPORTANT: If you do not upgrade to Calvium Player 1.30, then any calls you have made to af.openLinkInWebBrowser will have no effect.
- Styled ImageButtons now work properly. Thanks again to Marin Auer for letting us know about this problem. Previously if you created a style from an ImageButton then those buttons wouldn't show the pressed image property.
- Text that spans over more than one line inside a Button widget now centers properly. Previously multi-line text would align left regardless of the alignment setting. Thanks to Rik Lander for making us aware of this issue.
- We've prevented insertion of iFrames into RichText widgets. The reason for this is that iFrames worked in the Preview tool, but not on the device.
- We've removed the outline feature for fonts. Outline was a feature where a colored outline could be added to text. Android doesn't support this feature (in fact it results in all text being horribly garbled) so unfortunately we've had to remove it. Sorry if this affects your app.