Re: [Rakarrack-users] another small bug

[Renato <re...@gm...>]

On Sun, 7 Aug 2011 14:09:00 +0100
Josep Andreu <ho...@te...> wrote:

> 
> Hi
> 
> Thanks Renato you are our best Beta tester :-) 

heh, I would have liked to be able to submit patches and fiddle with
the effects code too... sometime ago I thought of relearning my C,
then I found out that rakarrack's sources are indeed .C files but that
means it's C++ :( maybe in another life (if what I hear of C++ is true)

> I fixed the ALSA
> client names ... I was noticed that but I was forget ... thanks to
> remind me ... is fixed I hope in our git repository 

I can confirm it's fixed

>.... about the
> MIDI channel in the instances... here works ... maybe is now due the
> fixed ALSA names but I dont thinks so :-) ... check again
> please ..  :-) anyway you can see if the config
> (~/.fltk/rakarrack.sf.net/rakarrack.prefs) looks good .... .. here
> part of my config entrys ...
> 
> rakarrack MIDI IN Channel:1
> rakarrack-01 MIDI IN Channel:5
> rakarrack-02 MIDI IN Channel:3
> rakarrack-03 MIDI IN Channel:1

ok, I edited manually the file and now it's ok... But if I do changes
from the GUI they don't get saved. BTW I was wrong, it's not only MIDI
IN Channel, *all* settings from second or third instances of rakarrack
don't get saved (only if I edit manually the .conf file). Permissions
seem okay:

renato@acerarch ~/.fltk/rakarrack.sf.net $ ls -lh
total 56K
-rw-r--r-- 1 renato users 25K Aug  7 19:06 rakarrack.prefs
-rw-r--r-- 1 renato users 25K Aug  7 19:02 rakarrack.prefs~


> 
> About .... the program option  arguments ... I know that ... is a
> small problem ...  has a solution but ... not today :-)  the problem
> is due because ... some options are for the program itself ....  and
> other options are the FLTK options that has all of the FLTK
> programs ..  we parse the options getopt() for  the program in
> main.C ... and then we pass the arguments to FLTK  ....   you know
> that the program run without GUI .. then of course we need to parse
> the options before start the GUI ...  but seems that the FLTK
> automatic parser .. stops or I dont know what hi does when a option
> is not recognized ... FLTK has a way to disable this auto option
> parser and has methods to create our own FLTK options parser .... the
> thing is ... to fix that is a lot of code ... and .. this FLTK
> options .. are really not so important .. :-)   but maybe someday I
> will do it :-)

oh, I see. well yeah it's not very important, I just found it out in
"--help" and thought it was cool.

cheers and thanks for the bugfixes!
renato