On Friday 28 April 2006 02:43, Michael Gogins wrote: > The first problem is that there is a black console window, then there is a > second console window (with a white background) for Csound messages. The > first window can be omitted with the right linker flag, I think. Probably, > you have just left this in for debugging purposes. The Windows console was left there only by mistake: I forgot to compile with -mwindows. Fortunately, this is easy to fix. > The second problem is that configuration dialog has no "close" button > (though Alt-F4 does close it), and it's a modal dialog so when it's open, > you can't run Csound. This is obviously easy to fix in FLTK. Again, this is a result of differences between operating systems. The window does have a close button on Linux (where it was originally designed), but apparently not on Windows which removes the button for "modal" windows. I did already mention this in the notes when posting the link to the Win32 beta version, though. Anyway, it should not be hard to fix, but the window needs to be somewhat reworked to have enough space for additional buttons. Not making the window modal is an option (and from the user's point of view, certainly a good one), but needs some changes so that the main window will be aware of the possibility of settings being changed dynamically. > I think it might be a problem that you construct the Csound command line > entirely from dialogs. Perhaps there should also be a text field for > additional flags by hand? It might be added, although the GUI does allow for setting basically all the options supported by Csound 5, and explicit command line options can also be added to . Where should the input for additional flags be ? > I think it would be desirable to add a button that links to the Csound HTML > help with a configurable path. FLTK has some sort of HTML browser, though > I'm not sure it's good enough for this. Well, this just another "run an external command" functionality, so is technically easy to be implemented. Where should this button be ? By the way, when using vim as the text editor, with my syntax files, it is possible to open the HTML help for the opcode which is under the cursor. > I think "Seek" or "Goto" is a better term than "Apply" for the score offset, > which is a nice feature. So, which one should it be, Seek or Goto ? > Putting dummy widgets in so as not to break widget orcs is a good idea. It needs some maintenance, though (fortunately new widgets do not seem to be added frequently), but at least the program will not hang or crash. You can use FLTK widgets, however, just turn off "perform in a separate thread". This will also enable the graph displays. An alternative way for controlling the widget opcodes could be to implement some way of communication between the host application and the opcodes (e.g. using the csound*GlobalVariable interface), to make it possible to disable the opcodes, change the threading behavior, etc. > Did you look at John Ramsdell's flCsound? He had a feature of placing FLTK > graphs onto separate tabs that would be nice to have. I did try flCsound at some time. Implementing graphs may be a good idea, although at this time probably not of the highest priority, especially since the original Csound graphs still work as long as a separate audio thread is not used.