DrumGizmo
DGEdit
General
We are proud members of:
DrumGizmo sponsors:
Congratulations GNU
We are proud members of:
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| roadmap:settings_analysis [2017/01/21 15:40] – [From the user perspective] deva | roadmap:settings_analysis [2017/01/22 15:53] – [Suggestion] deva | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| =====Settings Analysis====== | =====Settings Analysis====== | ||
| + | ====Suggestion: | ||
| + | * Users selects a drumkit file (as we do today) and clicks " | ||
| + | * Now the drumkit xml is loaded and the MemoryChecker analysis it so we know the estimated size of it. | ||
| + | * User then (optionally) turns the knob for memory preload, which live updates the estimated usage numbers in a label. | ||
| + | * User clicks " | ||
| + | |||
| + | While loading and while playing we could then have a label showing " | ||
| + | |||
| + | Muldjord: I quite like how it is right now. It's simple. Click to load the kit and it will load to the specified limit. Adjust the limit and purge if you need it. Less clicks and easy to understand. I don't think this needs redesigning. | ||
| ====From the user perspective===== | ====From the user perspective===== | ||
| //Chaot:// We should probably just give a "RAM usage" knob to the users, as this will probably be the only thing they can relate to in general. | //Chaot:// We should probably just give a "RAM usage" knob to the users, as this will probably be the only thing they can relate to in general. | ||