-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TabView is not rendering at bottom of the page. #2768
Comments
Hey @techguysyoo The tab-view can not be rendered at the bottom for Android. Here you can find a very basic example of how to use segmented-bar. |
Many thanks for your quick reply @NickIliev , Is there any way without segmented bar we can achieve the functionality since with segmented bare we have done but not getting the look and feel like tabview? |
The reason tab-view is render at the top for Android and at the bottom for iOS is because we want to keep the native behavior (so you would get exactly the same behavior as in the native iOS and Android). So you can't' customize some aspects of the modules. However, you have many ways to provide UX for your custom elements with animations (both CSS and https://docs.nativescript.org/ui/animation) and styles. In case you have chosen the path of creating your app with Angular-2 then you can also refer to the native Angular-2 structural directives. For example, this sample is very similar to creating a basic structure for custom tab view but with nativeScript and Angular-2 |
Thanks Team! |
I'm not sure if i should post my issue here or open another issue since what I'm trying to do is similar to this thread. I'm trying to render segmented bar at the bottom too but using the angular 2 implementation. I copied and pasted the example from the docs but when i place
the screen doesn't show the segmented bar at all but instead it shows white screen. If i remove the stacklayouts I see the segmented bar items. I copied the .ts example and the .html |
@NickIliev |
@Gerstalexej we've made some changes to the structure of the sample project - I have now fixed the links - for your convenience here is a direct link to the root directory of the sample application for NativeScript + Angular-2 @dianikol Keep in mind that you should have your components wrapped in a single root one. You can also take a look at this example of how to handle segmented bar in Angular-2 application - - you can also refer to the example given with *ngSwitch where we have not used segmented bar but the idea is applicable with the same logic. Example for creating custom tabs with content field (using FlexboxLayout and GridLayout but the same can be achived with other UI elements as well) page.component.html
page.component.ts
In the code above we are simply changin the color of the content but following the same logic you can pass different context or hide/show different layouts. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Team,
We are working on a native app using Typescript and Nativescript. In that we are trying to render tabview control on the bottom of the page. Although we have tried couple of things but unable to achieve the goal.
Please find the attached UI and needed code.
Please, provide the details below:
Did you verify this is a real problem by searching [Stack Overflow]
Yes, we didn't got the solution.
Tell us about the problem
We are working on a native app using Typescript and Nativescript. In that we are trying to render tabview control on the bottom of the page. Although we have tried couple of things in android but unable to achieve the goal.
Please find the attached UI and needed code.
Which platform(s) does your issue occur on?
Both
Please provide the following version numbers that your issue occurs with:
package.json
file of yourproject)
Please tell us how to recreate the issue in as much detail as possible.
Please add the attached xml file in your project to reproduce the issue.
Is there code involved? If so, please share the minimal amount of code needed to recreate the problem.
No, only xml view.
please find my .xml content below
The text was updated successfully, but these errors were encountered: