-
Notifications
You must be signed in to change notification settings - Fork 3
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
Change back-end to use {openxlsx2} #70
Comments
{openxlsx2} has continued to develop and is on CRAN, but it's still not a v1. There's a vignette to explain some of the changes. Consider forking {a11ytables} and creating {a11ytables2} (or complete rename) using {openxlsx2}. |
A nice accessibility feature that appeared in a test of the package is that automatic cell colour is supported through |
Just to say I would find this really useful as it would mean I can use |
Hi Stanley, thanks for the message. Yeah, as far as I know, {openxlsx} doesn't really have an analogue for This is definitely something that we're interested in. I've been investigating {openxlsx2} in the {a11ytables2} and {yamlsheets} packages, but they're very much in development and not yet ready for release. |
Thanks Matt! Just for anyone having the same problem, I think for now you can adapt some of the commented out code from the openxlsx source code to change the creator (not just add new ones using
|
{openxlsx2} will replace {openxlsx} at some point, presumably? Investigate its potential, but don't integrate until CRAN release and some stability.
The text was updated successfully, but these errors were encountered: