Viggo Fredriksen wrote: > On Wednesday 15 September 2004 21:18, Dirk Meyer wrote: > >> Define 'after a while'. I works ok here. Maybe it depends on the text >> you draw? >> > > For me it happens after 15-20 minutes. Try setting high fps on the animation, > and it will happen even quicker.
I will try. > The OSD_MESSAGE was a last minute thing as I thought the buttons needed > some more explanation than just the image. I'll see if I can find a better > way to display it. Maybe add two text fields above to buttons. The first showing the name of the control (Audioplayer), the second the current button. Aubin: since you are our designer, any suggestions how this should look like? >> And something irritating: When you show the control, I _see_ a stop >> button, but can't press it becuase you don't understand that event >> (it's not mapped). Maybe define an extra keymap for each buttonbar, >> too? Or each button? > > Hmm, what do you mean? Pressing the stop button works just fine here. > Or are you saying we sould listen to other events such as the STOP > button mapped on the remote/keyboard? Yes, I mean the stop button on my remote. Or 's' in keyboard mode. >> BTW, can you send a patch to respect the coding guidelines? Before you >> ask: they are only in my haed for now :-). You respected most of my >> guidelines, only small things: >> >> o please do not use more than 80 chars in a line >> o every function needs a doc string >> o the header of a file needs a doc what this file does >> o more internal docs (# comments) what you are doing here >> >> Check the image viewer for a good example. I know, writing docs suck, >> but we need better development docs. > > I'll try to document better in the future. I have an exam monday, I doubt I > have the time to fix anything before that. Good luck. Dischi -- Bills travel through the mail at twice the speed of checks.
pgptoG9ixVAVB.pgp
Description: PGP signature
