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
Trying to use Placeholder to insert UILabel #283
Comments
I was working with @getmetorajesh on this tonight and also puzzled on this one, would love to know the solution. We also tried:
Both Labels, above and below will render in the view of course, but we could not simply insert a native |
Looks like the |
Found a dirty workaround until that is fixed. Load with the component
|
@vakrilov @VladimirAmiorkov do we know if the above ^^ is fixed? Do we still need the dirty workaround or know? Was going to try but just wanted to check if either of you knew first. |
@NathanWalker I dont think it has been resolved just jet. |
I tried:
But in the console I get the error:
I also tried it without the:
|
Note: Closing due to inactivity |
@NickIliev Is it still true that |
Thanks manojdcoder for his help on my post. |
I think the angular way is to viewContainerRef |
I don't think so, since |
@manojdcoder Are you referring to me ? if so , it is possible and the modalDialog plugin used by NS , does use viewContainerRef. |
Thank you @RoyiNamir for pointing it, I must check that. I was under assumption that using |
@manojdcoder What did you end up with? Really looking for a definitive way to go. |
@hettiger Placeholder will be my choice. Though most times I prefer writing it as a component extending from appropriate NativeScript base class and use |
I am trying to add
UILabel
returned from a cocoapods library in place of aplaceholder
{N} element. As a simple test/experiment I created the label within thecreatingView()
event as show below,e.view = nativeLabel; //<UILabel: 0x7a942e60; frame = (0 ...
Though the placeholder seems to have updated with the UILabel the simulator does not show it. Any thoughts?
The text was updated successfully, but these errors were encountered: