Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Comments by a developer inside the Windows Media Player source code

pastebin.com

Post reply on HN
Print view View original

121–130 of 135 posts

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

#121

Post by ma2rten »

lanternslight wrote: post #120
Sembiance wrote: post #101

Earlier quoted context omitted.

Ahh, stack overflow. Hugely popular thread with a lot of engagement? Lets lock it. Wouldn’t want to encourage behavior that doesn’t match our narrow minded “vision” for the site. Still though, an improvement over the early years where they just outright deleted countless pages with countless contributions. In the end it’s their site and they can run it however they want, but it’s sad to see such massive potential squ…

Lol, that's funny coming from a commentor on THIS site! This is the first comment I've made here in a longtime, because anything that goes against the hivemind here gets downvoted to Oblivion.

No it doesn't if you make well reasoned arguments.

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

#122

Post by nishmastime »

oefnak wrote: post #119
gspr wrote: post #114

Earlier quoted context omitted.

I think a lot of people's frustration comes from questions where it's abundantly clear that the asker searched neither SO nor the web first. It only takes a few dozens of "why is [insert programming language]'s {addition, multiplication, subtraction, division} broken?!?!" questions that are all pointed to What Every Programmer Should Know About Floating Point Numbers before you lose all faith in humanity and get cran…

Or, even more annoyingly, when you Google something and the first result is the exact problem you have, with the answer being someone pointing out that the solution can easily be found by googling... People like you seem to forget that not only the question-asker profits from an answer, but future people as wel...

Did you consider looking at the other 1000s of results returned by Google?

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

#123

Post by tibbydudeza »

xmprt wrote: post #47
tibbydudeza wrote: post #3

One of the ugly hacks you do in SAP to make it work is reading/changing variables and structures inside the SAP standard code because there is no API exposing them. It is blessed officially as doing a "dirty" assign.

> there is no API exposing them. If there's no API exposing them but there's a way to make use of the internals with a dirty assign then sounds like the internals are now part of the API.

It is a feature of their language but you are on your own as a customer when an upgrade breaks the internals.

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

#124

Post by bredren »

mkl wrote: post #48
bredren wrote: post #41

Earlier quoted context omitted.

Indeed. One of the first things I did after adopting a package was remove a well understood and unnecessary exploitive. One person noticed and gave it the looking eyes emoji.

> well understood and unnecessary exploitive Probably not what you intended to say. "Expletive" or "exploit"?

Expletive.

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

#125

Post by fooker »

williamdclt wrote: post #98
Someone wrote: post #58

Earlier quoted context omitted.

“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,…

I've never seen a system where you can press modifiers _after_ letters, what are you using? Letters are definitely inserted on key down on all windows/linux/macos I've used

Ligatures pretty much work this way.

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

#126

Post by ThePadawan »

exikyut wrote: post #49
dijit wrote: post #21

Earlier quoted context omitted.

I think you’re mistaken, YouTube (in all the forms I use it with a keyboard at least) supports spacebar as a pause key. Your browser might try to pop you down half a page if the thing that is selected or highlighted on the page is not the video player itself though. But it works 100% of the time in fullscreen.

YouTube's keyboard handling is Insanely Intuitive™, I must absolutely agree. Usefully, the up/down keys don't change the volume unless the player is also focused. What's incredibly sad is that j/k/l were agreed upon to rewind/pause/forward the video, and these generally work unless you're in a textbox... but dedicated keys were not similarly approved to control the volume. -- My current winner for Absolutely Favorite…

> (...) but dedicated keys were not similarly approved to control the volume.

Arrow-up and arrow-down?

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

#127

Post by flurben »

ma2rten wrote: post #121
lanternslight wrote: post #120

Earlier quoted context omitted.

Lol, that's funny coming from a commentor on THIS site! This is the first comment I've made here in a longtime, because anything that goes against the hivemind here gets downvoted to Oblivion.

No it doesn't if you make well reasoned arguments.

Your argument here is not well reasoned.

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

#130

Post by m0dest »

Jare wrote: post #65
cm2187 wrote: post #9

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

Amazon Prime web player uses it but does not force keyboard focus on the place where it can detect it, so many times you have to click first before it will pause on space bar. Focus handling is generally terrible in web apps, but few instances infuriate me like this one.

Space bar handling in media players is a particularly hard problem because space bar is also the key that users expect to trigger the currently focused button. Some users rely entirely on keyboard focus.

So it starts to intersect with some non-obvious accessibility issues.

Post reply on HN