[pygame-bug] Pygame.cdrom bug


R

rantingrick

Hello folks,

Pygame --the best little 2d game engine in Pythoina-- is great for
little 2d one off games and such (or so i've heard). I really don't do
much 2d graphics but pygame has some other helpful modules so i
downloded it about a year or so ago although i had not used it until
today. I just wanted to be ready just incase the 2d bug bit me. So
recently I wanted to do some cdrom automation for one of my Tkinter
scripts and thought... Hey, i finally found a good use for that old
pygame module!

So with much anticipation i moseyed on over to my site-packages folder
and dusted off the old pygame module and docs and i was coding away
just happy as a clam. I had my initialization working well, my
ejections were a breeze, and i even had some boolean testing
functionality all wrapped up nicely. Boy was i on cloud nine! And just
as i was finishing up the interface class with a "close" method i
realized in horror... YOU CAN OPEN THE CD TRAY WITH PYGAME HOWEVER FOR
SOME CRUEL AND UNJUST REASON YOU CANNOT CLOSE IT! WTF?

Yes at this point i realized that without a method to close the cd
tray my little module was useless. Sure i could drop into my OS
functionality and close the cdtray by first setting up a device handle
and calling a few underlying Windows functions however i am convinced
that this basic functionality should be a part of any cdrom interface.
Why would someone create such an interface and leave out such an
important method? Surely this functionality must be available through
the SDL API? What gives pygame developers? What gives?
 
Ad

Advertisements

B

Benjamin Kaplan

Hello folks,

Pygame  --the best little 2d game engine in Pythoina-- is great for
little 2d one off games and such (or so i've heard). I really don't do
much 2d graphics but pygame has some other helpful modules so i
downloded it about a year or so ago although i had not used it until
today. I just wanted to be ready just incase the 2d bug bit me. So
recently I wanted to do some cdrom automation for one of my Tkinter
scripts and thought... Hey, i finally found a good use for that old
pygame module!

So with much anticipation i moseyed on over to my site-packages folder
and dusted off the old pygame module and docs and i was coding away
just happy as a clam. I had my initialization working well, my
ejections were a breeze, and i even had some boolean testing
functionality all wrapped up nicely. Boy was i on cloud nine! And just
as i was finishing up the interface class with a "close" method i
realized in horror... YOU CAN OPEN THE CD TRAY WITH PYGAME HOWEVER FOR
SOME CRUEL AND UNJUST REASON YOU CANNOT CLOSE IT!  WTF?

Yes at this point i realized that without a method to close the cd
tray my little module was useless. Sure i could drop into my OS
functionality and close the cdtray by first setting up a device handle
and calling a few underlying Windows functions however i am convinced
that this basic functionality should be a part of any cdrom interface.
Why would someone create such an interface and leave out such an
important method? Surely this functionality must be available through
the SDL API? What gives pygame developers? What gives?

--

1) That's a feature request (something isn't there that should be
there), not a bug (something that doesn't follow documented behaviors)

2) If you have a feature request or bug for a 3rd party package,
moaning about it here won't do anything. Try asking nicely either on
the project's mailing list or on the project's bug tracker.
http://www.pygame.org/wiki/patchesandbugs
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top