I vote for native look and feel versus consistency across platforms. I
understand the point but I would rather my app looked like a real Windows
Mobile app.
I do actually add the back button on Windows but on the form level:
_backCommand = new Command(Prefs.getMsg("rw.msg.nv.lst"));
setBackCommand(_backCommand);
This adds the back button to the title bar on iOS and Android but not on
Windows. Initially I thought that was fine because on a Windows phone you
have the hardware back button.Unfortunately a Windows app can run in a lot
of different modes and the hardware back button is not always there.
I am reluctant to use the Toolbar class as that does not seem like the
native look and feel to me.
On Saturday, November 12, 2016 at 11:17:30 AM UTC-8, Bryan Buchanan wrote:
>
> I would agree with Shai - Android and iOS use a back button, and it
> doesn't look out of place on UWP devices - in fact I think the consistency
> that CN1 allows across platforms is a good thing.
>
> I've not experienced any problems with back button code on UWP devices.
>
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to codenameone-discussions+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit
https://groups.google.com/d/msgid/codenameone-discussions/076de9c1-3f0c-48b5-8416-5fca351261b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
