DrumGizmo
DGEdit
General

We are proud members of:


DrumGizmo sponsors:








Congratulations GNU

Celebrate 30 years of GNU!

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
roadmap:settings_analysis [2017/01/22 15:23] – [Suggestion] muldjordroadmap:settings_analysis [2017/01/23 21:55] (current) – muldjord
Line 1: Line 1:
 =====Settings Analysis====== =====Settings Analysis======
-====Suggestion===== +====Suggestion: Two step drumkit load (abandoned)=====
-Two step drumkit load:+
   * Users selects a drumkit file (as we do today) and clicks "Load".   * Users selects a drumkit file (as we do today) and clicks "Load".
   * Now the drumkit xml is loaded and the MemoryChecker analysis it so we know the estimated size of it.   * Now the drumkit xml is loaded and the MemoryChecker analysis it so we know the estimated size of it.
Line 20: Line 19:
  
 //Deva:// The "Purge and Reload" button really simplifies things from the engine perspective. //Deva:// The "Purge and Reload" button really simplifies things from the engine perspective.
 +
 +//Muldjord:// We could work with a colorcoded slider for setting the cache limit. We could do a simple calculation based on the kit size and look at how many instruments there are, and calculate a sanity value from that. So if the user slides the slider below a certain point, it goes from green to yellow. And even further down, turns red. To indicate that the user is now in unstable territory.
 +
 ====The technical/code side of things===== ====The technical/code side of things=====
 From ''src/drumkitloader.cc'': From ''src/drumkitloader.cc'':
roadmap/settings_analysis.1485095010.txt.gz · Last modified: by muldjord
Trace:
GNU Free Documentation License 1.3
Valid CSS Driven by DokuWiki Recent changes RSS feed Valid XHTML 1.0