Skip to content

Commit b3d5dae

Browse files
Cannot link to utils::winProgressBar() help, because it only exists on Windows
1 parent 4370e21 commit b3d5dae

File tree

4 files changed

+4
-4
lines changed

4 files changed

+4
-4
lines changed

R/handler_winprogressbar.R

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
#' Progression Handler: Progress Reported as a MS Windows Progress Bars in the GUI
22
#'
3-
#' A progression handler for [utils::winProgressBar()].
3+
#' A progression handler for `winProgressBar()` in the \pkg{utils} package.
44
#'
55
#' @inheritParams make_progression_handler
66
#'

R/progressr-package.R

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
#' these progress updates. For instance, they can chose to report progress
1313
#' in the terminal using [utils::txtProgressBar()] or
1414
#' [progress::progress_bar()] or via the graphical user interface (GUI)
15-
#' using [utils::winProgressBar()] or [tcltk::tkProgressBar()].
15+
#' using `utils::winProgressBar()` or [tcltk::tkProgressBar()].
1616
#' An alternative to above visual rendering of progress, is to report it
1717
#' using [beepr::beep()] sounds.
1818
#' It is possible to use a combination of above progression handlers, e.g.

man/handler_winprogressbar.Rd

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

man/progressr.Rd

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)