Skip to content
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

Small inconvenience to fix for wide data and the viewing of the column metadata #9351

Open
rdstern opened this issue Jan 11, 2025 · 5 comments

Comments

@rdstern
Copy link
Collaborator

rdstern commented Jan 11, 2025

@N-thony or @Patowhiz I go into a wide dataset as shown below. (I used CarcassoneHeat, from the extRemes package.) I then pressed the option to open a script/log window. Lo and behold I am asked about whether I really want to get the column metadata.

The trigger for the question seems to be asking for another window. Please could it be limited to the metadata windows and not the script window. That's confusing!

image

It is correct in opening the log/script window, rather than the blank metadata window. I say No, because I certianly don't want it now, then I've lost the chance to get it later, because it doesn't seem to ask again.

@rdstern rdstern added this to the 0.8.0 milestone Jan 11, 2025
@Patowhiz
Copy link
Contributor

@rdstern thank you for spotting the bug, I agree that it should be limited to the column metadata window.
@N-thony, this issue can be delegated and fixed.

@N-thony
Copy link
Collaborator

N-thony commented Jan 14, 2025

@N-thony or @Patowhiz I go into a wide dataset as shown below. (I used CarcassoneHeat, from the extRemes package.) I then pressed the option to open a script/log window. Lo and behold I am asked about whether I really want to get the column metadata.

The trigger for the question seems to be asking for another window. Please could it be limited to the metadata windows and not the script window. That's confusing!

image

It is correct in opening the log/script window, rather than the blank metadata window. I say No, because I certianly don't want it now, then I've lost the chance to get it later, because it doesn't seem to ask again.

@rdstern, correct me if I got this wrong. I'm a bit confused to the fact that after clicking on Script/Log window you were expecting to get the Column Metadata window. This seems to be an issue even tho the dataset is large, we shouldn't get the Column Metadata window after click on Script/Log window. I think we have two issues here, the one you have mentioned and not open a Column Metadata window from Script/Log window.

@rdstern
Copy link
Collaborator Author

rdstern commented Jan 15, 2025

@N-thony when I click on Log/Script I certainly was not expecting to get the blank Column Metadata window. Getting that is all to do with the error I hope can be rectified. I hope I have now explained more clearly in your post just above.

@rdstern
Copy link
Collaborator Author

rdstern commented Jan 15, 2025

@N-thony I now have another bug, reported separately, but it all started when @Patowhiz was sorting out the wide datasets, so I think it may be related - not sure.
Here is how to get it.
a) Go into R-Instat and get the tutorial_after data from the R-Instat side of Import from Library.
b) Go to View and choose Swap Data and Metadata.

Here is the result:

Uploading image.png…

You now see the non-existent sheet1 in all its glory. You seem to have lost the real data frames, though the bottom left shows that R-Instat still thinks it is showing diamonds!

@N-thony
Copy link
Collaborator

N-thony commented Jan 15, 2025

@N-thony when I click on Log/Script I certainly was not expecting to get the blank Column Metadata window. Getting that is all to do with the error I hope can be rectified. I hope I have now explained more clearly in your post just above.

@Fidel365 would you like to try this? You can report here if you get stuck.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants