#82 GUI of Obi is somewhat sluggish

[Testing Team]

Whenever some operation like split, merge, copy, paste etc. is performed the GUI of obi takes time to show the change.
This will be a problem in production environment as the GUI is expected to react rapidly atleast to audio operations as audio editting is one of most time consuming part of DAISY content production.
Moreover the system resources consumed in GUI sometimes disturb playback / recording a little.

[Julien Quint (Pom)]

Logged In: YES
user_id=1313300
Originator: NO

Yes, drawing performances are horrible, and this is a big problem. Unfortunately I don't know how that can be improved.

[Markus Gylling]

Logged In: YES
user_id=523358
Originator: NO

Here are some thoughts that may/may not work:
1) At project open time, open the TOC collapsed, and only draw child sections when they are opened/accessed
2) Only draw whats visible on screen
3) Persist wave form data (if that increases the speed of redrawing)
4) Limit the amount of visible items in the content view. Now, collapsing in the TOC view also hides those strips in the content view. Perhaps there could be an option of only having currently selected section visible in the content view? (Which also raises the (longer term) question of having folded phrases, ie several rows of phrases per section, instead of one static row+scrolling.

Re 4, it may also be a usability issue; I am working on chapter 4, why are you showing me the wave forms of chapter 2?