Re: [pygame] pygame.midi using portmidi?

[René Dudfield <renesd@xxxxxxxxx>]

Cool.  the build page is back up for windows!  I guess that machine
has risen from the grave.


Now the sysfont tests pass on OSX.  The midi tests pass, all except
for on python2.4 on windows.

I think that 2.4 build still has the debug build of port midi - since
the results are dying.

Rather than the new prebuilts from here:
http://www3.telus.net/len_l/pygame/prebuilt-pygame1.9.0-msvcr71-win32.zip


cu,



On Mon, Jun 1, 2009 at 9:12 PM, René Dudfield <renesd@xxxxxxxxx> wrote:
> hi again,
>
> Concerning midi...  I've added a close() method to Input and Output,
> and an abort() method to Output.  close() lets any midi messages you
> have sent through get sent, and abort tries to stop the connection
> right away.  I've made it so that abort is not called on the
> __dealloc__, only close is.
>
> I asked on the port midi mailing list, and apparently Pm_Abort is not
> used all that much, and isn't implemented on linux alsa.  So now
> people will have to explicitly call abort() if they want it to close
> right away... otherwise it might wait around to send off the rest of
> the midi messages in the buffer.
>
> Also made it so that after pygame.midi.quit() the class instances
> remaining raise a MidiException, rather than calling the portmidi die
> code.
>
>
>
> cu,
>
>
> On Sun, May 31, 2009 at 10:18 AM, René Dudfield <renesd@xxxxxxxxx> wrote:
>> On Sat, May 30, 2009 at 8:41 PM, Brian Fisher <brian@xxxxxxxxxxxxxxxxxxx> wrote:
>>> since you mentioned the build page - power company turned off power to my
>>> neighborhood for a day, and the mac didn't auto power back on (anybody know
>>> if you can set a mac to do that?), while my PC seems to have had some part
>>> of it fried.
>>>
>>
>> ah, bugger.  I hate it when the magic smoke comes out.  I wish I could
>> email you some spare parts from two pcs I have that I don't really
>> need any more.
>>
>> my old pc used to die after power outages... unplugging the power
>> cable from the motherboard and plugging it back in seemed to do the
>> trick.  Some sort of weird reset thing happened.
>>
>>
>> I found this note about auto start for Macs:
>> "the Energy Saver preference pane and check the box for RESTART
>> AUTOMATICALLY AFTER POWER FAILURE ..."
>>
>