Re: [Lmuse-developer] midi

[Tim E. R. <ter...@ro...>]

On June 29, 2012 9:23:38 PM Florian Jung wrote:
> Am 29.06.2012 20:58, schrieb Tim E. Real:
> > On June 29, 2012 1:51:29 PM Tim E. Real wrote:
> >> On June 27, 2012 1:17:26 AM Florian Jung wrote:
> >>> Am 27.06.2012 00:59, schrieb Tim E. Real:
> >>>> On June 27, 2012 12:12:53 AM Florian Jung wrote:
> >>>>>> It may not be terribly obvious (we really should have a 'none'
> >>>>>> selection),
> >>>>> 
> >>>>> i already coded that. i'll commit it, okay?
> >>>> 
> >>>> Sounds good. Try to label it <None> including the brackets so it's
> >>>> clear.
> >>> 
> >>> okay, i'll do that.
> >>> shall i make it checkable then?
> >>> 
> >>>> Can you have another look at the 'read configuration' disabling thingy?
> >>>> Most of the time it remains disabled even when I select a med file.
> >>> 
> >>> observed. more specifically, this always happens when you change
> >>> directories. i'll try to fix this before the release, thank you.
> >> 
> >> Fixed. I just reversed your routine a bit.
> >> It specifically looks for midi files, instead of med files,
> >> 
> >>  and blanks the checkbox if found.
> >> 
> >> Tested OK.
> >> Tim.
> > 
> > I just noticed that if you open a midi file via command line
> > 
> >  or a file manager's 'open with', our midi ports are still blanked.
> > 
> > So we will definitely need to embellish this a wee bit in the
> > 
> >  file opening routines in app.cpp, to prevent it from
> >  blanking the ports.
> 
> should we? don't we usually want MusE to load a complete song (including
> ports) when we run muse fo.med?

Yes, look closely, I said a loading midi file, not med. I meant prevent
 loading a midi file from blanking the ports.

Tim.

> 
> > But it's not too critical right now. It can wait.
> 
> +1
> 
> flo
> 
> > Tim.
> > 
> >>> greetings
> >>> flo
> >>> 
> >>>> Thanks. Tim.
> >>