Live data from Hacker News

Comments by a developer inside the Windows Media Player source code

pastebin.com

81–90 of 135 posts

Re: Comments by a developer inside the Windows Media Player source code

#81

What is the best library to use these days for developing in Visual C++? I had to write some VCpp code a few days ago using the Winhttp api and it was a nightmare. I'm not sure if its because I've been spoiled rotten by python where you can do a get/post request with a few lines of code, and that this is just how CPP is, but most of the complications are to do with calling and using the (not very well) documented API…

For http? Embed libcurl.

Re: Comments by a developer inside the Windows Media Player source code

#82

Pulchritude!? Boy, I had to look that one up!

Gonna take a gander and guess the developer might have an Indian origin! Or at least studied for the GRE!

"pulcher" is a fairly elementary piece of Latin vocab. It's in Book I of the Cambridge Latin Course, for example. This is much the same in other courses. So anyone, Indian or not, who has done basic Latin in school is likely to have encountered it and hence be aware of "pulchritude".

* https://www.dl.cambridgescp.com/dl_course/book-i

A random other example: https://www.ocr.org.uk/Images/221512-gcse-latin-j282-defined...

Re: Comments by a developer inside the Windows Media Player source code

#83

Earlier 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.

Keydowns have the physical button analogue: when you press a physical button, it immediately closes the contact, it doesn't wait until you lift your finger again. Not saying key down is better than key up, there are certainly arguments for both.

Your experience of physical buttons is limited. There are many sorts. To pick an apposite example: The "Pause" button on old tape players used to be press-and-release to change state. Because it was a direct mechanical linkage and not motorized on some players/recorders, this made it possible to perform quite accurate editing with very basic kit: pressing and releasing pause to pause, pressing it again and keeping it held down, and releasing exactly when one desires to un-pause.

Re: Comments by a developer inside the Windows Media Player source code

#84
post #58

The 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” Should they, in general? If you want to press a key combination, you never press the two keys at exactly the same time. So, if key events were on key-down, you would have to press modifiers before letters to type capital letters, use keyboard shortcuts, etc. I think that would be annoying and slow typists down. It also rules out using bare modifier key presses as input methods,…

Where on Earth have you been typing capital letters? One does have to press the modifier first on conventional home and personal computer keyboards.

Re: Comments by a developer inside the Windows Media Player source code

#86
post #76

Pretty much what I am expecting from Windows based software considering the mess windows always was and is to this day.

Yeah let's rewrite the entire system from scratch every 2 years with the langue-du-jour and deprecate everything. That 'll show them

Re: Comments by a developer inside the Windows Media Player source code

#89

This is why I love open source. In LibreOffice, cruft like this is often removed due to the embarrassment factor.

lol LibreOffice codebase is cruft on top of cruft.

Indeed, it is an ancient codebase. It is being constantly refactored.

Re: Comments by a developer inside the Windows Media Player source code

#90

This is why I love open source. In LibreOffice, cruft like this is often removed due to the embarrassment factor.

It was removed from Microsoft code too. This is an old snapshot of the code, almost two decades old. 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.

I wasn't aware of this.
Post reply on HN