![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
clipka <ano### [at] anonymous org> wrote:
> The scroll-wheel-switches-desktops thingie Warp is so fond of I find
> actually quite annoying, can't think of how anyone might like it - as it
> has the scroll wheel change functionality dramatically depending on what
> the mouse cursor is currently hovering over.
On the contrary, I find Windows' behavior with the mouse wheel absolutely
irritating.
*Of course* the mouse wheel behavior should depend on where the cursor
is currently, exactly in the same way as *clicking*. I'm accustomed to use
the mouse wheel in the exact same way as I use the other mouse buttons:
I point where I want the scrolling to happen, and roll the wheel, and I
expect that thing I'm pointing at to scroll, in the exact same way that
if I point to something and left-click, I expect that thing to be selected,
or if I right-click for a context menu for the pointed thing to pop up.
When Windows refuses to do this, it's extremely irritating. I constantly
find miself scrolling something else than what I want to scroll because
Windows refuses to scroll what I'm pointing at.
Having to click on something before you can scroll it with the wheel is
not only useless, but also can cause unwanted behavior because none of the
mouse buttons simply *selects* the window you click on. If you click on an
active element, that element will also be *activated*, possibly performing
an unwanted operation by mistake. And no, I don't want to have to click on
the title bar of a window before I can scroll it with the mouse wheel.
Thus it's not surprising that I find switching desktops with the mouse
wheel quite natural: If I "scroll" the desktop background, it jumps to the
virtual desktop in that direction.
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Warp wrote:
> Having to click on something before you can scroll it with the wheel is
> not only useless, but also can cause unwanted behavior because none of the
> mouse buttons simply *selects* the window you click on. If you click on an
> active element, that element will also be *activated*, possibly performing
> an unwanted operation by mistake. And no, I don't want to have to click on
> the title bar of a window before I can scroll it with the mouse wheel.
On Mac, clicking on an inactive window brings it to the front without
sending the click to the application code, so it won't activate elements.
On some apps.
Some other apps override that behavior, making it useless, since you're
never sure if a click will activate an element or not (depends on whether
that app overrode the click-through behavior or not).
Why does Apple get *almost* everything right? The details they get wrong are
usually *very* annoying.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Nicolas Alvarez wrote:
> On Mac, clicking on an inactive window brings it to the front without
> sending the click to the application code, so it won't activate elements.
That bugs the crap out of me when Mac programs run on Windows. Indeed, I
can't imagine why you'd want it to work that way.
I looked at 3 or 4 "scroll what I'm pointing at already!" programs when I
moved to Vista, and none of them work right.
--
Darren New, San Diego CA, USA (PST)
Is God willing to prevent phrogams, but not able?
Then he is not omnipotent.
Is he able, but not willing, to prevent phrogams?
Then he is malevolent.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Darren New <dne### [at] san rr com> wrote:
> Nicolas Alvarez wrote:
> > On Mac, clicking on an inactive window brings it to the front without
> > sending the click to the application code, so it won't activate elements.
> That bugs the crap out of me when Mac programs run on Windows. Indeed, I
> can't imagine why you'd want it to work that way.
> I looked at 3 or 4 "scroll what I'm pointing at already!" programs when I
> moved to Vista, and none of them work right.
What really irritates me is Windows Explorer in this regard. For example,
if I select a directory from the folder view on the left, and the directory
contents then open on the right, if I try to scroll the file listing, it
just scrolls the folder view on the left. And the other way around. In this
case there isn't even any "title bar" to click in order to select the
proper scrollable view. You have to click *on* the view, and be careful
to not to click on something you don't want to.
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Invisible schrieb:
> Also, which moron decided that clicking something twice on the task bar
> should minimize it? I never *ever* want this to happen!
Actually, it's not clicking twice hat triggers this - it's clicking on
an item that has the focus. So if an item already has the focus,
double-clicking will just minimize and restore, effectively doing nothing.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Invisible schrieb:
> Maybe I'm biased because on my ancient PC, minimising and maximising
> windows is quite a slow operation... But, in general, I never minimize
> windows at all. (Except to reach the desktop.)
... and they have even a dedicated shortcut in the taskbar for that.
So yes, minimizing windows is more of a nuisance, typically.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Darren New schrieb:
> I saw a demo of a drag-and-drop idea I've been lusting after ever since.
>
> If you pick something up to drag-and-drop it, then move diagonally over
> the corner of a window, it peels the window down like you're curling
> down the page of a book so you can see what's behind it and drop your
> thing there. You could do drag-and-drop between multiple full-screen
> windows that way.
That'd be cool, indeed.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Darren New schrieb:
> clipka wrote:
>> Another thing bothering me about KDE4 is its standard of
>> single-clicking a highlighted item to activate it, but they can't be
>> blamed for me being so accustomed to the Windows Way,
>
> That really hasn't been the "Windows Way" since they came out with
> Active Desktop 10+ years ago. If you want that behavior on Windows, you
> can turn it on too. (I thought it had been the default at least since
> 2000 or XP.)
It used to be the default when they first introduced it, but I can't
remember having seen it actually used by anyone anywhere, so I'm pretty
sure they quickly changed it back. (Can't say from my own installations;
maybe they ask and I just choose double-clicking as a subconscious
reflex reaction, maybe they default to double-clicking without asking;
what I can tell for sure though is that they don't just default to
single-clicking. Vista and 7 may be yet different though.)
>> Ah well, and did I mention that KDE4 uses a totally different font
>> size in a XDMCP login than it does when logged in locally?
>
> Don't fonts always come from the local machine? Or did they fix this in
> X by now?
I have no idea. I just noticed that old Debian "Etch" 4.0r5 Gnome got it
right without me intervening, while openSUSE KDE4 messes up.
>> And my, this one-click-to-activate thing is more addictive than I
>> thought... I guess I'll turn it back on again...
>
> any explorer window: Tools->Folder Options->General... in Windows.
> And yes, it's much more handy, especially if there's easily found areas
> of the screen where clicking does *not* select anything.
KDE4 (at least the Dolphin file manager does it right by giving
somewhere on the icons to click on in order to select instead of
activate. Not sure whether I really want it on in Windows, due to a lack
of such sugar.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
nemesis schrieb:
> waiting for the "Blender sucks" daily povray newsgroups bash tomorrow.
Can't say anything about that, 'cause I'll possibly never ever give it a
chance again :-P
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Darren New schrieb:
> I knew I got pissed easily at pretty trivially annoying stuff, but I
> never realized it was trivial *needlessly* annoying stuff that did it.
Yeah, same here I guess.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |