Comments by a developer inside the Windows Media Player source code
11–20 of 135 posts
Re: Comments by a developer inside the Windows Media Player source code
#12This is why I love open source. In LibreOffice, cruft like this is often removed due to the embarrassment factor.
Since the 2002 TWC initiative, anything from easter eggs to things like that are all very strongly banned, and actively get removed as they're discovered.
Re: Comments by a developer inside the Windows Media Player source code
#13Re: Comments by a developer inside the Windows Media Player source code
#14Pulchritude!? Boy, I had to look that one up!
Looking it up, I still have no idea what it means. The best I can gather is its beautifully wholesome. Other sources say beauty, but it seems like such a specific word for a form of beauty.
Re: Comments by a developer inside the Windows Media Player source code
#15Pulchritude!? Boy, I had to look that one up!
Looking it up, I still have no idea what it means. The best I can gather is its beautifully wholesome. Other sources say beauty, but it seems like such a specific word for a form of beauty.
To me, pulchritude is such an ugly sounding word I can always remember the meaning as being the opposite of how it sounds.
(Funny enough, I was just looking up to see if there is a name for words that sound opposite to their meaning and found this [0] discussion on the English stack exchange, which gives pulchritude as its example!)
[0] https://english.stackexchange.com/questions/103741/name-for-...
Re: Comments by a developer inside the Windows Media Player source code
#16The bug here is in media player to listen on key-up events. Mouse-button-up makes sense because the user can move the mouse to cancel the click. But key events should be on key-down and that's how it is done most of the time. So if you use key-up you run into these problems.
Why?
I like how keyup is less ambiguous: it avoids the question “what do I do if the user is holding the key down?”
I also like being able to hold the key down to cue up a command and then at the right time, pull my hand away to execute crisply. For video editing mainly.
I’m not saying keyup is the only answer. Just that there isn’t one obvious answer.
Re: Comments by a developer inside the Windows Media Player source code
#17Earlier quoted context omitted.
Looking it up, I still have no idea what it means. The best I can gather is its beautifully wholesome. Other sources say beauty, but it seems like such a specific word for a form of beauty.
Have never come across the word before either. Makes you think - did the person say the word to convey some kind of meaning? Or to sound super-smart to their peers?
Re: Comments by a developer inside the Windows Media Player source code
#18The bug here is in media player to listen on key-up events. Mouse-button-up makes sense because the user can move the mouse to cancel the click. But key events should be on key-down and that's how it is done most of the time. So if you use key-up you run into these problems.
> But key events should be on key-down Why? I like how keyup is less ambiguous: it avoids the question “what do I do if the user is holding the key down?” I also like being able to hold the key down to cue up a command and then at the right time, pull my hand away to execute crisply. For video editing mainly. I’m not saying keyup is the only answer. Just that there isn’t one obvious answer.
Because of the reported bug in this example (which I also encountered quite often):
- user hits ESCAPE
- my window gets key-down/ESCAPE and closes itself
- your window (which happens to be the next in the focus-order) gets key-up/ESCAPE and closes itself
> I also like being able to hold the key down to cue up a command and then at the right time, pull my hand away to execute crisply
Ok, but if your window wants to support this behavior (which is not very common) you have to watch for key-up AND key-down like the bug-report suggests.
Re: Comments by a developer inside the Windows Media Player source code
#19Lecturing on keyboard shortcuts when windows media player is the only video player in the world not using the space bar as a shortcut for play/pause.
Re: Comments by a developer inside the Windows Media Player source code
#20Earlier quoted context omitted.
> But key events should be on key-down Why? I like how keyup is less ambiguous: it avoids the question “what do I do if the user is holding the key down?” I also like being able to hold the key down to cue up a command and then at the right time, pull my hand away to execute crisply. For video editing mainly. I’m not saying keyup is the only answer. Just that there isn’t one obvious answer.
> Why? Because of the reported bug in this example (which I also encountered quite often): - user hits ESCAPE - my window gets key-down/ESCAPE and closes itself - your window (which happens to be the next in the focus-order) gets key-up/ESCAPE and closes itself > I also like being able to hold the key down to cue up a command and then at the right time, pull my hand away to execute crisply Ok, but if your window want…