-
Notifications
You must be signed in to change notification settings - Fork 19
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
Editing and Resetting Tables #94
Comments
@rb543210 Which version of excelR are you using? The first issue is not replicable in the latest development version of excelR. The second issue is more of a feature request which I plan to implement in the next version of excelR. |
@Swechhya Thanks for your response! I'm using excelR 0.4.0 and R 4.0.2. |
@rb543210 Can you try with the development version? I'll be releasing a new version with the fixes and getting the data soon. |
@Swechhya It looks like both issues I identified are fixed. Thank you for the package! It seems like the next version will be really useful. |
I am trying to use excelR for editable tables that can be reset by a button. The code below is a simplified extract from a larger app. I see two issues when I do this, although one might be a feature request:
When editing a cell once and then discarding, the table behaves as expected. I can make as many different edits as I want and get the expected result, but when I edit the same cell twice in the same way, the second edit (and subsequent edits) do not show up as changed. E.g., if you make the value of A1 5 and reset, and then make A1 5 again, the change is not registered.
There doesn't seem to be a way to extract the value of input$data without editing the table. I.e., if I remove the line
rvals$changes <- FALSE
, the button is always shown and the value of rvals$changes is always TRUE after the first edit, even though the table shows the reset values. In this simplified example it doesn't matter, but in a larger context it makes excelR much harder to use.Code used to generate bug
The text was updated successfully, but these errors were encountered: