You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Probably my lack of shiny knowledge. In view mode, tmapProxy is already triggered at start up. So after the initial map rendering, the map is immediately updated, which takes a bit of time. See code in this vignette https://r-tmap.github.io/tmap/articles/adv_shiny#view-mode
In the same code example, the tmapProxy doesn't work when the original (projected) sf objects are used.
The examples in the documentation and the vignette work, so these issues are not critical for the upcoming tmap4 release.
The text was updated successfully, but these errors were encountered:
There are still a couple of shiny issues:
renderTmap
had mode-specific functions (not S3 but sort of): https://github.com/r-tmap/tmap/blob/master/R/tmapLeafletShiny.R However, I tried calling these functions withdo.call
https://github.com/r-tmap/tmap/blob/master/R/shiny.R#L46-L47 but that didn't work. For now, I hard-coded the mode-specific approached in these functions, with an error for modes other than plot and view.Probably my lack of shiny knowledge. In view mode,
tmapProxy
is already triggered at start up. So after the initial map rendering, the map is immediately updated, which takes a bit of time. See code in this vignette https://r-tmap.github.io/tmap/articles/adv_shiny#view-modeIn the same code example, the tmapProxy doesn't work when the original (projected) sf objects are used.
The examples in the documentation and the vignette work, so these issues are not critical for the upcoming tmap4 release.
The text was updated successfully, but these errors were encountered: