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

blank diagram window #105

Open
ceheitsch opened this issue May 16, 2022 · 3 comments
Open

blank diagram window #105

ceheitsch opened this issue May 16, 2022 · 3 comments

Comments

@ceheitsch
Copy link
Contributor

The first time a diagram window is opened for a folder it is blank. If the blank one is closed, then the next one opened is fine:

Blank diagram window:

Screen Shot 2022-05-16 at 3 01 42 PM
.

@ceheitsch
Copy link
Contributor Author

Sometime the first blank one appears briefly, and then disappears. In this case, the second one is still blank but the third one is fine.

@maxieds
Copy link
Contributor

maxieds commented Jun 2, 2022

The most recent commit message reflects that I am not able to completely reproduce the issue here. On my system, the window is minimized automatically, and when it is manually maximized again by the user everything redraws correctly from what I can see. I think that these changes should fix the bug. It will need more testing to verify on the target system where this issue appeared.

@ceheitsch
I am marking the release (and corresponding brew formula) as a prerelease (beta) version. This is how to install it to see if the issue is fixed:

$ brew tap gtDMMB/homebrew-core
$ brew update
$ brew reinstall --verbose gtDMMB/core/rnastructviz

@maxieds
Copy link
Contributor

maxieds commented Jun 2, 2022

@maxieds closed this as completed in 09c123e 19 minutes ago

This is weird. All I did to invoke the issue getting closed was to mention the issue (by its number: #105) in the commit message. Maybe this is a non-standard repo/admin/commit configuration option on GH? It seems like it's good practice to refer to the issue that led to the changes. OTOH, just having mentioned it does not imply a mature fix to the bugs witnessed in the issue.

At any rate, I do not have the permissions on the gtDMMB organization pages to dig into to why this happens.

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

No branches or pull requests

2 participants