Comment On Slow Down, You Click Too Fast

Your Name:

They also double-click every single time.

DrPepper:

Your Name:

They also double-click every single time.

I -- still -- double-tap the "end call" button on my phone, which reacts fast enough that the first tap ends the call; the 2nd tap calls that person AGAIN.

DrPepper:

Your Name:

They also double-click every single time.

I -- still -- double-tap the "end call" button on my phone, which reacts fast enough that the first tap ends the call; the 2nd tap calls that person AGAIN.

daef:

* if you have none: enable 3-button-emulation and middle-click by left+right-clicking simutaneously

Ralph:

Soon we were blessed with double-click and right-click and click-hold (drag) and triple-click and control-click and... you can probably spot a trend here.

Apeiron:

trwtf is the Synaptics Windows drivers. They don't even have middle-click emulation, which means good luck middle-clicking anything on a laptop unless you figure out a way to get one of their gesture features to spit out middle-click (couldn't find it).

Kaosadvokit:

Bring Back Nagesh:

So I'm assuming this abstraction for System.Windows.Forms.WebBrowser is written in VB or C# and is meant to work for built-in IE frames inside a parent application?

If so, TRWTF is forcing someone to use an embedded web browser to do something rather than opening the link in the user's default web browser. A bit like Steam, which as we know, is also a WTF.

And even if you absolutely MUST force people to use a browser panel inside your app, why does it need to have multiple tabs?

why an integrated browser?

Because your application has an integrated document viewer and you happen to use HTML-based documents--after all, that minimizes the effort to have the same documents available online.

Because users (and IT staff) like to install different browser versions and you value a consistent user experience.

Because you're writing software to run on a semi-embedded system where you want to lock the user into a single application (think kiosk software).

Why support tabs?

Because people are used to them. Back when IE6 had 90% market share, tabs were a niche feature that 90% of people didn't use. They use them now; support is expected. If you want angry users, provide a user experience that is inconsistent with their expectations.


No, TRWTFs are developers who live in a small corner of the development world and don't understand that there are applications where this is a legitimate and proper design decision. TRWTFs are developers that rush to condem actions they don't understand because they don't understand them. Do you know of a better debounce mechanism? I don't; similar mechanisms have served me well across hundreds of projects, because it is simple, easy to implement/maintain, produces the correct result, and fails to produce an incorrect result. Sure, this one is rough around the edges, but it is pretty clear what it does and why.

Maybe it was the smaller readership years ago, maybe it was the submission quality, I don't know... but TDWTF has really gone downhill over the last several years.

urza9814:

xorsyst:

urza9814:

What if, for (a somewhat poor) example, you're writing something like Outlook? Emails are going to be in HTML; you could write your own parser, but why reinvent the wheel? But you also don't want to launch a full browser every time the user clicks to view a message.

To continue your example, what if there's a url in the message? If I click on it, should it spawn my browser, or render the webpage in my application?

To use a different example (application help). Lots of applications have their help in html format in one form or another (including windows chm). Many of them launch the windows help viewer or a browser to view the help. Is that wrong?

Obviously there's no firm line there but my opinion, as I said, is that core functionality shouldn't require an external app. Help isn't core; you can use the browser or windows help to do that. Clicking a link from an email isn't either if your app is an email viewer and not a web browser. Sure, both are HTML documents in a sense, but most users don't know that and they're certainly different conceptually.

If I'm forced to interact with two separate applications simultaneously to use your software, you're probably doing something wrong. There are certainly valid reasons to do that, but definitely not for something Grandma might be using...unless Grandma is a sysadmin.

Kaosadvokit:

Is it wrong to spawn a second application to interact with components of the first? Usually. When I open a mail message, I need to interact with it. Reply, forward, delete, etc. These are not operations for a web browser to handle, they are for my application. The browser that displays the message content should be embedded. When I click a link, I'm now transitioning to the standalone document interface; it should be a browser window and, at this point, user experience concerns say to use the user's preference because it is a standalone resource, it should conform to their expectations--your application supports the content, not the presentation now. Of course, if the link is a mailto: link, it shouldn'thand it off to the browser, it should create a new message (thats my opinion, feel free to disagree, but implementation details like this aren't the topic here).

NH:

It looks like a remedy for those sites that opens a kiloton of windows when you try to close one. Some phishing sites did that a few years back.

Apeiron:

daef:

* if you have none: enable 3-button-emulation and middle-click by left+right-clicking simutaneously

trwtf is the Synaptics Windows drivers. They don't even have middle-click emulation, which means good luck middle-clicking anything on a laptop unless you figure out a way to get one of their gesture features to spit out middle-click (couldn't find it).

It does let you remap left/right, but then you lose left/right. Best bet is to either:
A) Remap the left button to middle and only tap-click with the pad
B) Switch to Linux, where the Synaptics driver is sane.

da Doctah:

ZoomST:

In fact, using the middle mouse button in FireFox over a link, opens it in a new tab.

Cool! You just saved me something like 24 hours over the remainder of my lifetime.

CodeSimian:

Apeiron:

trwtf is the Synaptics Windows drivers. They don't even have middle-click emulation, which means good luck middle-clicking anything on a laptop unless you figure out a way to get one of their gesture features to spit out middle-click (couldn't find it).

There's a couple of registry keys you can set to enable middle-click emulation by either pressing both buttons or tapping with 2 fingers:
http://iampaulh.blogspot.ca/2012/06/adding-middle-click-to-synaptics-touch.html

DrPepper:

I -- still -- double-tap the "end call" button on my phone, which reacts fast enough that the first tap ends the call; the 2nd tap calls that person AGAIN.

¯\(°_o)/¯ I DUNNO LOL:

I write the code for an embedded device with a small QVGA screen and a keypad. It has a simple user interface based on going through various levels of screens. I found out that I (as the programmer, who knows how it works, with it conveniently on my desk and not 5 feet up on a wall), I was screwing stuff up when I pressed the ENTER or ESC key once too many times, due to slow key bounce with the rubber keys. And this was even with flushing the keyboard buffer when changing screens.

So I added a 200ms delay after changing screens (both forward and back) during which it would ignore either of those two keys. And it did the trick.

But I actually documented in the comments what it's trying to do and why.

da Doctah:

ZoomST:

In fact, using the middle mouse button in FireFox over a link, opens it in a new tab.

Cool! You just saved me something like 24 hours over the remainder of my lifetime.

instigator:

LoremIpsumDolorSitAmet:

Yuck... Kiosk browsers are a WTF in their own right.

Are you saying we shouldn't have Kiosks? Or that Kiosk's should not have the ability to show documents? Even help documents?
There are more things on Heaven and Earth than are dreamt of in your philosophy.

Kaosadvokit:

@LoremIpsumDolorSitAmet:

Adhering to standards is all good and well, however the standards don't state which browser has the correct font-rendering engine. The standards don't mean you will have an ideal implementation with whatever your end-user has installed, and the standards don't get your application 508 certified if significant portions of the operating environemnt cannot be assessed.

Being dismissive of 99% of development efforts doesn't make your 1% right, it makes your views of the 99% wrong. You don't seem to understand that an embedded web browser isn't about browsing the web, it is abotu displaying application-centric content that happens to be stored as HTML. Kiosks that are powered by browsers strike a nice balance between cost and benefit. Strangely, this appeals to the suits, even if it isn't the most elegant solution from a software standpoint. Complicator's Gloves, anyone? Would you like an arbitrary system to pass condiments? I'm sure somebody can provide links if you don't get the references.

It is pretty obvious you've never developed COTS or embedded software...

Ralph:

Anyway this code is for those luzers who think you have to double-click web links because... well, um, I never really thought about it, just because.

ZoomST:

Remy Porter:

In my day, that was "middle mouse click". You kids and your fancy scroll-wheels.

In fact, using the middle mouse button in FireFox over a link, opens it in a new tab. Is it covered by this code? Seems not, AFAIK.

Chromatix:

One of the railway signalling systems in Scandinavia indicates different speeds with different numbers of lights. A single green light means "clear, full speed". Two or three green lights together mean "clear" and successively *lower* speeds. This leads to an obvious wrong-side failure mode where one of the green lights blows, and the signal indicates a higher speed than it should.

Worse, the immediately neighbouring country has a signalling system that is very similar, was derived from the same older system, yet has some indications which are completely opposite to the indications in the first country.

Accordingly it is prohibited for the same driver to operate a train in both countries, even though they speak nearly the same language and the networks are interconnected.

Herr Otto Flick:

ZoomST:

Remy Porter:

In my day, that was "middle mouse click". You kids and your fancy scroll-wheels.

In fact, using the middle mouse button in FireFox over a link, opens it in a new tab. Is it covered by this code? Seems not, AFAIK.

Given that this code is a wrapper around System.Windows.Forms.WebBrowser, a wrapper for including IE into your app, your conclusion that it does not cover Firefox is spot on. Remarkable deduction skills.

(Keyboard.Modifiers & ModifierKeys.Control) == ModifierKeys.Control)

da Doctah:

ZoomST:

In fact, using the middle mouse button in FireFox over a link, opens it in a new tab.

Cool! You just saved me something like 24 hours over the remainder of my lifetime.

jbabs:

If you ever find yourself writing a comment in your code that says "Please don't submit this to the daily WTF", it means two things:

1) you're doing it wrong.
2) it's going to end up on dailyWTF.

xorsyst:

urza9814:

What if, for (a somewhat poor) example, you're writing something like Outlook? Emails are going to be in HTML; you could write your own parser, but why reinvent the wheel? But you also don't want to launch a full browser every time the user clicks to view a message.

To continue your example, what if there's a url in the message? If I click on it, should it spawn my browser, or render the webpage in my application?

TheCPUWizard:

It looks like the code is intended to handle situations where the person has ALREADY ctrl-clicked to open a new tab, is still on the old tab (ie the new tab has not opened and gotten focus)....

Especially if the site in question is slow to load, this *may* actually be useful (the intent, not necessirly the implementation.

jbabs:

If you ever find yourself writing a comment in your code that says "Please don't submit this to the daily WTF", it means two things:

1) you're doing it wrong.
2) it's going to end up on dailyWTF.