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

Feature request / DAML Studio: Don't revert back to table view on changes #1675

Closed
sofusmortensen opened this issue Jun 14, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@sofusmortensen
Copy link
Contributor

commented Jun 14, 2019

If you have chosen the "transaction view" for showing the result of your scenario, and you make a change that automatically reruns the scenario, the view is reverted back to "table view".
I don't think the user would expect that. I find it more convenient to stick to the chosen view.

@sofusmortensen sofusmortensen changed the title Windows SDK / DAML Studio: Don't revert back to table view on changes Feature request / DAML Studio: Don't revert back to table view on changes Jun 16, 2019

@cocreature cocreature self-assigned this Jun 18, 2019

@cocreature

This comment has been minimized.

Copy link
Contributor

commented Jun 18, 2019

Thanks for the bug report! I fully agree that the current behavior is undesirable. I’ll look into a fix.

cocreature added a commit that referenced this issue Jun 20, 2019

Preserve the selected view on scenario result updates
Previously, we always reverted back to the table view when the
scenario results changed. This PR changes this to preserve the
selected view.

I’ve also tested that this does not break backwards compatibility: If
you use the newer extension with an older SDK, you will get the
previous behavior of reverting to the table view and you can still
switch by clicking on the button.

Fixes #1675

cocreature added a commit that referenced this issue Jun 20, 2019

Preserve the selected view on scenario result updates (#1776)
Previously, we always reverted back to the table view when the
scenario results changed. This PR changes this to preserve the
selected view.

I’ve also tested that this does not break backwards compatibility: If
you use the newer extension with an older SDK, you will get the
previous behavior of reverting to the table view and you can still
switch by clicking on the button.

Fixes #1675
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.