Especializa / nativescript-ng-shadow

Angular directive to apply shadows to native elements according to the elevation level guidelines of material design specification
Apache License 2.0
54 stars 38 forks source link

No shadows. #2

Open dbeulen opened 6 years ago

dbeulen commented 6 years ago

I'm currently trying to implement this plugin in an existing app, but I don't get any shadows on my android development phone. Do you have any direction on where i should start debugging?

I included the module in my app.module.ts, then i added a Label with a shadow property. Did i forget anything?

Which platform(s) does your issue occur on?

Please, provide the following version numbers that your issue occurs with:

    "@angular/animations": "~4.2.5",
    "@angular/common": "~4.2.5",
    "@angular/compiler": "~4.2.5",
    "@angular/core": "~4.2.5",
    "@angular/forms": "~4.2.5",
    "@angular/http": "~4.2.5",
    "@angular/platform-browser": "~4.2.5",
    "@angular/router": "~4.2.5",
    "nativescript-angular": "~4.2.0",

    "@angular/compiler-cli": "~4.2.5",
    "@ngtools/webpack": "~1.6.0",
    "babel-traverse": "6.26.0",
    "babel-types": "6.26.0",
    "babylon": "6.18.0",
    "copy-webpack-plugin": "~4.0.1",
    "extract-text-webpack-plugin": "~3.0.0",
    "lazy": "1.0.11",
    "nativescript-css-loader": "~0.26.0",
    "nativescript-dev-typescript": "~0.5.1",
    "nativescript-dev-webpack": "^0.8.0",
    "nativescript-worker-loader": "~0.8.1",
    "raw-loader": "~0.5.1",
    "resolve-url-loader": "~2.1.0",
    "typescript": "^2.5.3",
    "webpack": "~3.2.0",
    "webpack-bundle-analyzer": "^2.8.2",
    "webpack-sources": "~1.0.1"
berardo commented 6 years ago

Sorry for the delay. Did you managed to find the issue? Have you tried the demo app?

berardo commented 6 years ago

Please have a look at the newest version, probably the issue is gone. Thanks

dbeulen commented 6 years ago

I will check this tomorrow!

mxmp210 commented 4 years ago

I just installed it in existing app and importing it to specific module related to component fixed the loading issue. That is how Angular works usually, so if your component resides inside any module, you have to import it there instead of app module itself.