-
18 Mar 2012 8:25 AM #1
[2.0.0] Can't remove default back button text
[2.0.0] Can't remove default back button text
Demo:
http://www.senchafiddle.com/#A3mkcCode:Ext.Loader.setConfig({ enabled: true }); Ext.application({ name: 'SenchaFiddle', launch: function() { var view = Ext.create('Ext.NavigationView', { fullscreen: true, defaultBackButtonText: null, navigationBar: { backButton : { align : 'left', iconCls: 'back', iconMask: true } } }); view.push({ title: 'First', html: 'First view!' }); view.push({ title: 'Second', html: 'Second view!' }); } });
-
18 Mar 2012 9:29 AM #2
back button is central thing on NavigationView, like a the ".." on a directory file browsing
If you don't want back button, why not using card layout
-
18 Mar 2012 10:32 AM #3
you miss understood, I want the back button. But no Button text. Only a back icon instead (more space). Navigationbar seem“s very buggy. Title text is alway centered, title overlapse buttons ... and I want the back button to only show an icon. ;o)
-
19 Mar 2012 8:49 AM #4Sencha - Sencha Touch Dev Team
- Join Date
- Mar 2007
- Location
- Redwood City, California
- Posts
- 3,651
- Vote Rating
- 14
Thank you for the report.
-
26 Mar 2012 1:04 PM #5
NavigationView has been cleaned up a lot for the next release, and I just tested today and this already works. Thanks for the report.
Sencha Inc.
Robert Dougan - @rdougan
Sencha Touch 2 and Ext JS 4 Core Team Member, SASS/Theming Wizard.
-
29 Mar 2012 5:04 AM #6
Until the next release you could alter the code within the View.js & Bar.js file.
simple find the 'defaultBackButtonText' within the 'Ext.navigation.View' class, (within the navigation folder in the Veiw.js and Bar.js)
(EDIT: Sorry: 'src/navigation/View.js' and 'src/navigatio/Bar.js')
then remove the text in both. you might then need to add a few non breaking spaces within them so the button stretches but this will remove the text.
This worked for me, then when the next release and updates are out it can be put back. hope this helps.Last edited by simondavies; 29 Mar 2012 at 5:06 AM. Reason: added a little more details
Success! Looks like we've fixed this one. According to our records the fix was applied for
TOUCH-2510
in
2.0.


Reply With Quote