I have also been troubled by the clutziness of the BiaB interface. Luckily for me, RealBand solves most of my problems. Remaining issues? I have three interface concerns that I continue to scratch my head over:

1. Big dialog boxes with many options, and little consideration to functional grouping and natural eye/mouse movements. i.e., they are hard to understand and use.

2. Big lists of filenames in stylepicker and such, rather than a database-type interface. Why? It's gotta be a legacy thing.

3. The WIERD mix of slick User Interface (Track window, Mixer window) with prototype-level UI (the Arranger). <soapbox> Come on guys! The rule is, to the end user, the interface IS the program. If you go all clutzy on the UI, people think you are amateurs, and in large degree they are right. The other rule is, it all has to look like it was done by the same person. That means some measure of discipline in the software development standards area, using the same toolkit in the same way, and having a designer have final say over your UI. This *can* be done in a rapid develop environment, I've seen it done many times.</soapbox>

Scott Emery