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

List not updating after gain applied #4

Closed
Sappharad opened this issue Aug 27, 2012 · 2 comments
Closed

List not updating after gain applied #4

Sappharad opened this issue Aug 27, 2012 · 2 comments

Comments

@Sappharad
Copy link
Owner

I received the following bug report via e-mail:

After applying gain (regardless of whether the analyze only operation was performed 
or the user pressed apply gain directly) the gain is applied but the list is not refreshed... 
it still shows the old volume and track gain, although the gain IS applied. I suspect this is 
because there is no call to refresh the list after the apply gain operation finishes.

I have not yet verified this to see if it occurs.

@Sappharad
Copy link
Owner Author

Unable to reproduce this problem.
The list is refreshed for both analyze and apply, and when I tested applying gain to a file that had never been processed before everything appeared in the grid correctly after it was complete.

Closing this issue.

@Sappharad
Copy link
Owner Author

I got another e-mail reporting this problem, which made me realize what this report was about.

I worked through the process, and realized it was kind of confusing for users. If you Analyze files, then Apply gain, nothing in the list will change. This is normal, because you just applied the levels that you analyzed, and the grid is being updated with the exact same information that was there from analysis because that's what you applied. If someone were to analyze first, look at the numbers, decide what they want and change it up top, once they apply they'd see the grid change. (That's how I usually use the program)

I may consider some kind of additional feedback in the future so the user knows that the application did something. But this bug can remain closed because it's working as it was intended to.

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

1 participant