[Patch] Unified reload/stop actions

[Shaun Reich]

My personal opinion on merging the actions.. is that I don't like it :)

I have used applications that have done this before (memory serves me
not), but it's an annoyance for me at least. An aspect that really
annoys me, is when you are in the process of loading a big web page,
you hit the button (that is now set to the Stop action), but at that
very second, it finished, and you end up reloading the page.

Also, is it a good idea.. with respect to average users, to have
actions that change like that, into complete opposites. In the context
of e.g. a dialog, where it has the less/more thing, it makes sense to
change that button.. but this is only after the user actually does
something, whereas here it kind of does it out of it's own free will.

 But on the other hand, is the Stop action really used that much? On
additional thought, I'm not sure many use it, especially the "average
user". If this is true, then I suppose it would be beneficial to merge
them, avoiding clutter/confusion(?), etc.

In all honesty, I am quite skeptical on the first use-case I made
against it, wherein the action can quickly turn the other way, into
it's opposite action.....and reloading a bloaty page on a slow connect
is....unfun (although, I am blessed with a fast one :P ).

Hopefully others can offer some better opinions ;-)

-- 
--
Riverenter Vestri,
Shaun Reich


On Wed, Apr 29, 2009 at 3:29 PM, Sascha Peilicke <sasch.pe at gmx.de> wrote:
> Hi,
>
> some time ago I posted a patch on reviewboard about the unification of the
> reload and stop action (similar to Opera and Safari). David Faure commented
> quite a bit but we came to no conclusion, so I'd like to get some more
> feedback.
>
> patch URL: http://reviewboard.kde.org/r/593/
>
> p.s.:
>        please CC me, I'm not on this list
> --
> Sascha Peilicke
> http://saschpe.wordpress.com
>