How to implement visibility in nativescript with angular
I've got a dead simple nativescript angular component that I'm trying to set the visibility on and extending ContentView doesn't seem to work.
<capture-component [visibility]="'collapse'" top="0" left="0"></capture-component>
@Component(
moduleId: module.id,
templateUrl: './capture.component.html',
selector: 'capture-component'
)
export class CaptureComponent extends ContentView
Anyone have a clue how to do this correctly? I've tried variations of collapse, 'collapse', collapsed, bound or not bound, etc. Kind frustrating how easy this is to do. I could make a property and set the css but i'd rather use the framework if possible.
angular components nativescript visibility
add a comment |
I've got a dead simple nativescript angular component that I'm trying to set the visibility on and extending ContentView doesn't seem to work.
<capture-component [visibility]="'collapse'" top="0" left="0"></capture-component>
@Component(
moduleId: module.id,
templateUrl: './capture.component.html',
selector: 'capture-component'
)
export class CaptureComponent extends ContentView
Anyone have a clue how to do this correctly? I've tried variations of collapse, 'collapse', collapsed, bound or not bound, etc. Kind frustrating how easy this is to do. I could make a property and set the css but i'd rather use the framework if possible.
angular components nativescript visibility
Did you try[style.visibility]="'collapse'"
?
– ConnorsFan
Nov 12 '18 at 21:49
It seems as though you can just usevisibility="collapse"
orvisibility="collapsed"
, since at the moment you're not binding thevisibility
property to a property in your class.
– Brian Lin
Nov 12 '18 at 21:54
add a comment |
I've got a dead simple nativescript angular component that I'm trying to set the visibility on and extending ContentView doesn't seem to work.
<capture-component [visibility]="'collapse'" top="0" left="0"></capture-component>
@Component(
moduleId: module.id,
templateUrl: './capture.component.html',
selector: 'capture-component'
)
export class CaptureComponent extends ContentView
Anyone have a clue how to do this correctly? I've tried variations of collapse, 'collapse', collapsed, bound or not bound, etc. Kind frustrating how easy this is to do. I could make a property and set the css but i'd rather use the framework if possible.
angular components nativescript visibility
I've got a dead simple nativescript angular component that I'm trying to set the visibility on and extending ContentView doesn't seem to work.
<capture-component [visibility]="'collapse'" top="0" left="0"></capture-component>
@Component(
moduleId: module.id,
templateUrl: './capture.component.html',
selector: 'capture-component'
)
export class CaptureComponent extends ContentView
Anyone have a clue how to do this correctly? I've tried variations of collapse, 'collapse', collapsed, bound or not bound, etc. Kind frustrating how easy this is to do. I could make a property and set the css but i'd rather use the framework if possible.
angular components nativescript visibility
angular components nativescript visibility
edited Nov 12 '18 at 21:48
asked Nov 12 '18 at 21:34
Adawg
19618
19618
Did you try[style.visibility]="'collapse'"
?
– ConnorsFan
Nov 12 '18 at 21:49
It seems as though you can just usevisibility="collapse"
orvisibility="collapsed"
, since at the moment you're not binding thevisibility
property to a property in your class.
– Brian Lin
Nov 12 '18 at 21:54
add a comment |
Did you try[style.visibility]="'collapse'"
?
– ConnorsFan
Nov 12 '18 at 21:49
It seems as though you can just usevisibility="collapse"
orvisibility="collapsed"
, since at the moment you're not binding thevisibility
property to a property in your class.
– Brian Lin
Nov 12 '18 at 21:54
Did you try
[style.visibility]="'collapse'"
?– ConnorsFan
Nov 12 '18 at 21:49
Did you try
[style.visibility]="'collapse'"
?– ConnorsFan
Nov 12 '18 at 21:49
It seems as though you can just use
visibility="collapse"
or visibility="collapsed"
, since at the moment you're not binding the visibility
property to a property in your class.– Brian Lin
Nov 12 '18 at 21:54
It seems as though you can just use
visibility="collapse"
or visibility="collapsed"
, since at the moment you're not binding the visibility
property to a property in your class.– Brian Lin
Nov 12 '18 at 21:54
add a comment |
2 Answers
2
active
oldest
votes
You have to declare a Input()
visibility in your CaptureComponent and then you an use that in your capture.component.html e.g.
<capture-component [visibility]="'collapse'" top="0" left="0"></capture-component>
Let's assume your capture.component.html starts with a GridLayout, then in your html
<GridLayout width="100%" height="100%" rows="auto,*" [visibility]="visibility">
and in your .ts file
import Input from '@angular/core';
@Component(
moduleId: module.id,
templateUrl: './capture.component.html',
selector: 'capture-component'
)
export class CaptureComponent extends ContentView
@Input() visibility: string;
I know that would work, but figured extending ContentView would already do that for me. Perhaps I'm just assuming too much.
– Adawg
Nov 13 '18 at 14:09
add a comment |
I ended up just using *ngIf although I feel visibility should work when extending any Base view.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53270435%2fhow-to-implement-visibility-in-nativescript-with-angular%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You have to declare a Input()
visibility in your CaptureComponent and then you an use that in your capture.component.html e.g.
<capture-component [visibility]="'collapse'" top="0" left="0"></capture-component>
Let's assume your capture.component.html starts with a GridLayout, then in your html
<GridLayout width="100%" height="100%" rows="auto,*" [visibility]="visibility">
and in your .ts file
import Input from '@angular/core';
@Component(
moduleId: module.id,
templateUrl: './capture.component.html',
selector: 'capture-component'
)
export class CaptureComponent extends ContentView
@Input() visibility: string;
I know that would work, but figured extending ContentView would already do that for me. Perhaps I'm just assuming too much.
– Adawg
Nov 13 '18 at 14:09
add a comment |
You have to declare a Input()
visibility in your CaptureComponent and then you an use that in your capture.component.html e.g.
<capture-component [visibility]="'collapse'" top="0" left="0"></capture-component>
Let's assume your capture.component.html starts with a GridLayout, then in your html
<GridLayout width="100%" height="100%" rows="auto,*" [visibility]="visibility">
and in your .ts file
import Input from '@angular/core';
@Component(
moduleId: module.id,
templateUrl: './capture.component.html',
selector: 'capture-component'
)
export class CaptureComponent extends ContentView
@Input() visibility: string;
I know that would work, but figured extending ContentView would already do that for me. Perhaps I'm just assuming too much.
– Adawg
Nov 13 '18 at 14:09
add a comment |
You have to declare a Input()
visibility in your CaptureComponent and then you an use that in your capture.component.html e.g.
<capture-component [visibility]="'collapse'" top="0" left="0"></capture-component>
Let's assume your capture.component.html starts with a GridLayout, then in your html
<GridLayout width="100%" height="100%" rows="auto,*" [visibility]="visibility">
and in your .ts file
import Input from '@angular/core';
@Component(
moduleId: module.id,
templateUrl: './capture.component.html',
selector: 'capture-component'
)
export class CaptureComponent extends ContentView
@Input() visibility: string;
You have to declare a Input()
visibility in your CaptureComponent and then you an use that in your capture.component.html e.g.
<capture-component [visibility]="'collapse'" top="0" left="0"></capture-component>
Let's assume your capture.component.html starts with a GridLayout, then in your html
<GridLayout width="100%" height="100%" rows="auto,*" [visibility]="visibility">
and in your .ts file
import Input from '@angular/core';
@Component(
moduleId: module.id,
templateUrl: './capture.component.html',
selector: 'capture-component'
)
export class CaptureComponent extends ContentView
@Input() visibility: string;
answered Nov 12 '18 at 22:56
Narendra Mongiya
1,285718
1,285718
I know that would work, but figured extending ContentView would already do that for me. Perhaps I'm just assuming too much.
– Adawg
Nov 13 '18 at 14:09
add a comment |
I know that would work, but figured extending ContentView would already do that for me. Perhaps I'm just assuming too much.
– Adawg
Nov 13 '18 at 14:09
I know that would work, but figured extending ContentView would already do that for me. Perhaps I'm just assuming too much.
– Adawg
Nov 13 '18 at 14:09
I know that would work, but figured extending ContentView would already do that for me. Perhaps I'm just assuming too much.
– Adawg
Nov 13 '18 at 14:09
add a comment |
I ended up just using *ngIf although I feel visibility should work when extending any Base view.
add a comment |
I ended up just using *ngIf although I feel visibility should work when extending any Base view.
add a comment |
I ended up just using *ngIf although I feel visibility should work when extending any Base view.
I ended up just using *ngIf although I feel visibility should work when extending any Base view.
answered Nov 13 '18 at 16:36
Adawg
19618
19618
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53270435%2fhow-to-implement-visibility-in-nativescript-with-angular%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Did you try
[style.visibility]="'collapse'"
?– ConnorsFan
Nov 12 '18 at 21:49
It seems as though you can just use
visibility="collapse"
orvisibility="collapsed"
, since at the moment you're not binding thevisibility
property to a property in your class.– Brian Lin
Nov 12 '18 at 21:54