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.

Sign up for GitHub

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

Jump to bottom

Bugfix: Inconsistency of view buttons for multiple workspaces in the VSI #11482

Closed
AntonPiccardoSelg opened this issue Nov 27, 2014 · 5 comments
Closed

Bugfix: Inconsistency of view buttons for multiple workspaces in the VSI #11482

AntonPiccardoSelg opened this issue Nov 27, 2014 · 5 comments
Assignees
@quantumsteve
Labels
Framework Issues and pull requests related to components in the Framework Stale This label is automatically applied to issues that are automatically closed by the stale bot Vates

Comments

@AntonPiccardoSelg
Copy link
Contributor

This issue was originally TRAC 10640

The view buttons behave inconsistently when loading several workspaces.

  1. Load an MDHisto workspace into the VSI
    You should see only the MULTISLICE and THREESLICE view as selectable

  2. Load an MDEvent workspace into the VSI
    You should see that the MULTISLICE, THREESLICE and the SPLATTERPLOT view are selectable. This is fine.

  3. Switch to multislice
    You should see that only the STANDARD and THREESLICE view are available

    Keywords: VATES-vis
@AntonPiccardoSelg
Copy link
Contributor Author

@NickDraper (2015-04-27T08:10:34):
Moved to R3.5 at the R3.4 code freeze

@AntonPiccardoSelg AntonPiccardoSelg added Framework Issues and pull requests related to components in the Framework Vates labels Jun 3, 2015
@AntonPiccardoSelg AntonPiccardoSelg self-assigned this Jun 3, 2015
@AntonPiccardoSelg AntonPiccardoSelg added this to the Release 3.5 milestone Jun 3, 2015
@NickDraper NickDraper modified the milestones: Release 3.5, Release 3.6 Sep 14, 2015
@NickDraper NickDraper modified the milestones: Release 3.6, Release 3.7 Jan 22, 2016
@AntonPiccardoSelg
Copy link
Contributor Author

As of 3.5.1 this issue still remains

@NickDraper NickDraper modified the milestones: Release 3.8, Release 3.9 Oct 3, 2016
@NickDraper NickDraper modified the milestones: Release 3.9, Temporary Holding Oct 14, 2016
@NickDraper NickDraper removed this from the Temporary Holding milestone Oct 3, 2017
@AntonPiccardoSelg
Copy link
Contributor Author

@quantumsteve I am reassigning this to you. Please feel free to change this, if this is not appropriate.

@stale
Copy link

stale bot commented Feb 23, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

@stale stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Feb 23, 2021
@stale
Copy link

stale bot commented Mar 2, 2021

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.

@stale stale bot closed this as completed Mar 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@quantumsteve quantumsteve

Labels
Framework Issues and pull requests related to components in the Framework Stale This label is automatically applied to issues that are automatically closed by the stale bot Vates
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@NickDraper @quantumsteve @AntonPiccardoSelg