Friday, December 1. 2006
KDE Misfeature
Please look at the above screenshot. Yes, I know, it hurts. No, I did not draw this with The Gimp. This is an actual Amarok screenshot, running under KDE 3.5.5. How the hell did those ugly squares appear all over the screen, is it a virus? No, it's a KDE feature!
How to reproduce: Fire up a KDE application (Konqueror, Amarok, or KMail will do) and press the ctrl key. It's not even a new feature; it has been there since KDE 3.3 or somesuch. And this feature even has a name, which I can't be bothered to look up.
Questions naturally coming to my mind:
How the hell could this "feature" pass the KDE usability team?
Is the person who invented it ashamed of it?
In Amarok development, whenever someone comes up with an idea like that, we'd go like: "Dude, are you out of your mind?"
Food for thought?
Trackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
you rock, markey!
This seriously annoys me - and I can't imagine something that's so easy to accidentally do can be good for accessibility.
This seriously annoys me - and I can't imagine something that's so easy to accidentally do can be good for accessibility.
Well, that doesn't happen on my Amarok (but it's a feature in Konqueror for web browsing).
But I know it's useful for some people I know who have difficulty using the mouse (due to physical circumstances) and being able to hit keys like that allows them to, say, browse the web easily. It's the main reason why they used Opera in the past (now Konqueror) when that was available.
So whoever did come up with that accessibility feature should be proud that they have enabled other people using KDE easier. Besides, for browsing, it's a fast way to hit links/focus fields (if you get lazy of hitting '/' and typing the first chars of the link)...
But I know it's useful for some people I know who have difficulty using the mouse (due to physical circumstances) and being able to hit keys like that allows them to, say, browse the web easily. It's the main reason why they used Opera in the past (now Konqueror) when that was available.
So whoever did come up with that accessibility feature should be proud that they have enabled other people using KDE easier. Besides, for browsing, it's a fast way to hit links/focus fields (if you get lazy of hitting '/' and typing the first chars of the link)...
I'm glad I'm not the only one that find the Access Keys "feature" annoying 
It's one of those things that really should have a global mechanism for disabling it on the system.
It's one of those things that really should have a global mechanism for disabling it on the system.
I don't understand this mis-feature. From time to time some KDe ore KDE application dev blogs about it and even points out how to disable it (only via direct config file editing btw!). But it's still there.
Someone who knows how, please DO something about it and kill this feature now...
Thanks!
Someone who knows how, please DO something about it and kill this feature now...
Thanks!
Take back the point for every user for whom control is not on the bottom corner of the keyboard (my sunray keyboard for example)
Sorry, but this feature just needs to be off by default, or the first time it is activated it needs to pop up and ask if you want to leave it on from now on or something. I too have searched for hours through k/board setup panels and never found a way to make it stop without resorting to .config hacking
Sorry, but this feature just needs to be off by default, or the first time it is activated it needs to pop up and ask if you want to leave it on from now on or something. I too have searched for hours through k/board setup panels and never found a way to make it stop without resorting to .config hacking
The problem you are having has 2 levels:
1. CTRL as a DEFAULT choice for it, and
2. Existence of that feature in KDE.
Noone, and I hope you don't argue against #2.
It appears you are arguing against #1, which is a fair target.
CTRL is the easiest button on a keybord to get right - its on the corner, and, it's also a modifier key. 2 points for CTRL
There is an odd chance that a temporarily-fully-functioning individual may find those squares annoying and is too lazy to go into Keyboard Shortcuts panel to change it. 0.5 point for your camp. (-0.5 for laziness)
Even the remaining 0.5 points are at question, because you seemingly miss the horrid, unreasonably clattered appearance of Amarok UI, while whining about those squares.
1. CTRL as a DEFAULT choice for it, and
2. Existence of that feature in KDE.
Noone, and I hope you don't argue against #2.
It appears you are arguing against #1, which is a fair target.
CTRL is the easiest button on a keybord to get right - its on the corner, and, it's also a modifier key. 2 points for CTRL
There is an odd chance that a temporarily-fully-functioning individual may find those squares annoying and is too lazy to go into Keyboard Shortcuts panel to change it. 0.5 point for your camp. (-0.5 for laziness)
Even the remaining 0.5 points are at question, because you seemingly miss the horrid, unreasonably clattered appearance of Amarok UI, while whining about those squares.
For those of us who have looked through all the zillion damned keyboard-related config options, could you point out where in "Keyboard Shortcuts" this option is? I've looked. Also in Keyboard Layout, Accessibility, and Peripherals->Keyboard. Nowhere.
Everytime someone says the Amarok UI is cluttered I look at and think wtf?
Like seriously, it has so few buttons. I think you people mean something else or something. I'm sure you have a legitimate criticism in there somewhere, but it can't be cluttered.
Like seriously, it has so few buttons. I think you people mean something else or something. I'm sure you have a legitimate criticism in there somewhere, but it can't be cluttered.
I have to counter: I love that feature. It's great for mouseless browsing.
to #1
I see there may be some use for this feature for some people in specific situations. But it annoys the hell out of many other users. Opera manged to implement this kind of accessibility without getting in the way of most of it's users. KDE should come up with something better than using CTRL, which is needed for lots of operations.
I see there may be some use for this feature for some people in specific situations. But it annoys the hell out of many other users. Opera manged to implement this kind of accessibility without getting in the way of most of it's users. KDE should come up with something better than using CTRL, which is needed for lots of operations.
I like it!
There are some stiuations where you want to use keyboard or cant use mouse. Also It is a right policy to have a common feature. For example you cant copy&paste from manual pages of quanta using menus, which is annoying.
I'm against of cancelling this feature but there can be an option to enable/disable, which could be disabled for default.
There are some stiuations where you want to use keyboard or cant use mouse. Also It is a right policy to have a common feature. For example you cant copy&paste from manual pages of quanta using menus, which is annoying.
I'm against of cancelling this feature but there can be an option to enable/disable, which could be disabled for default.
Uhm...that's an accessibility feature. You just need to disable it....I know it doesn't do it on my computer because I disabled it...I have the (bad?) habit of holding shift-alt for a few seconds after I change vdesktops (I use shift-alt-arrows to move around vdesks) while I look at things before moving to a different vdesk, and that kind of behavior activates sticky keys or some other accessibility thing...so I just disable all accessibility options in KDE and live happily.
In other words...it is a feature...one that most of us don't need, but that those that need it actually really need it to be able to use the computer...and, IMNSHO, this is one of those times when having it activated for the few is better than not having it activated because it means the most need to do a few extra clicks to disable it.
In other words...it is a feature...one that most of us don't need, but that those that need it actually really need it to be able to use the computer...and, IMNSHO, this is one of those times when having it activated for the few is better than not having it activated because it means the most need to do a few extra clicks to disable it.
This feature is one of the few things that are making KDE worthy for me. KDE is keyboard friendly.
If we'll lose this feature because of mousefuckers that just plain sucks.
If we'll lose this feature because of mousefuckers that just plain sucks.
I have to come to this features rescue too. Its one of the features that keeps me in kde. I absolutely love using it when surfing mouseless (when i dont have an external mouse with me when using the laptop).
Now i can understand that its annoying if you dont use it.
Now i can understand that its annoying if you dont use it.
Daniel,
could you tell me where I can unmap this feature from CTRL so that I can set it up to something I don't use every two seconds as a modifier. If I knew how I'd gladly map it to F12 or something else I don't use constantly. Unfortunately I can't find an option where I can get rid of it. Looked through the KDE keyboard shortcuts, but I can't find it.
Though maybe it's not much use if we go down into the discussion much more. I think it's not important how many users like and how many dislike the feature. It's understandable that there are users who like to navigate a website via the keyboard. But it's obvious as well that the way this is done right now is getting in the way and even confusing some people. The exact number of people doesn't matter too much - interesting is that even people whose blogs are aggregated at planet.kde.org have trouble with it. I'd assume those guys are at least 'educated users'. To me this sounds like an actual usability issue.
So my main point simply is that the feature should (and could) be implemented in a way that is still easily accessible to disabled people but won't interfer with normal operation of KDE for other users.
When you can tell me how I can disable it completely via keyboard shortcuts or any other means, that would help me personally, but still others will have the same issue and may not find the way to disable it.
could you tell me where I can unmap this feature from CTRL so that I can set it up to something I don't use every two seconds as a modifier. If I knew how I'd gladly map it to F12 or something else I don't use constantly. Unfortunately I can't find an option where I can get rid of it. Looked through the KDE keyboard shortcuts, but I can't find it.
Though maybe it's not much use if we go down into the discussion much more. I think it's not important how many users like and how many dislike the feature. It's understandable that there are users who like to navigate a website via the keyboard. But it's obvious as well that the way this is done right now is getting in the way and even confusing some people. The exact number of people doesn't matter too much - interesting is that even people whose blogs are aggregated at planet.kde.org have trouble with it. I'd assume those guys are at least 'educated users'. To me this sounds like an actual usability issue.
So my main point simply is that the feature should (and could) be implemented in a way that is still easily accessible to disabled people but won't interfer with normal operation of KDE for other users.
When you can tell me how I can disable it completely via keyboard shortcuts or any other means, that would help me personally, but still others will have the same issue and may not find the way to disable it.
Just added this to
http://wiki.kde.org/tiki-index.php?page=Secret+Config+Settings
(all the way on the bottom. Plz help phrasing it better, just edit that page)
You are still on the hook for missing the deformity of Amarok behind the yellow squares, though
http://wiki.kde.org/tiki-index.php?page=Secret+Config+Settings
(all the way on the bottom. Plz help phrasing it better, just edit that page)
You are still on the hook for missing the deformity of Amarok behind the yellow squares, though
Apologies, was too haste, the shortcut is NOT in the Keyboard Shortcuts, though it really should... 
Here is the command to solve the problem
kwriteconfig --file ~/.kde/share/config/konquerorrc --group "Access Keys" --key Enabled --type bool false
Thx. to http://www.kdedevelopers.org/node/1569
Here is the command to solve the problem
kwriteconfig --file ~/.kde/share/config/konquerorrc --group "Access Keys" --key Enabled --type bool false
Thx. to http://www.kdedevelopers.org/node/1569
The day this feature disappears from KDE I'll stop using KDE... I've never had nicer way to browse web without mouse... so think twice what you want.
Yeah I know you don't care what I think.. but there's still people who can't use mouse. Damn you "normal" people.
Yeah I know you don't care what I think.. but there's still people who can't use mouse. Damn you "normal" people.
Erm, it's pretty obvious how this is NECESSARY from an accessibility point of view. Believe it or not, the idea of being able to handle a mouse effectively is quite a challenge and simply not realistically possible for many users. KDE should have keyboard-equivalent options for all actions.
Seems unnecessarily arrogant to presuppose that while you lack such a disability, that others shouldn't.
They're called.... access keys. And yes, they are a W3 standard. KHTML is one of the first to support it.
> Is the person who invented it ashamed of it?
Maybe if you actually knew what you were talking about in this case your flaming might have some ground. Considering you don't, well, nothing. A question that now naturally comes to mind: are you ashamed of your post? Hint: you should be. There's really no need for this type of putting-down in the Open Source community.
Past that, it's insanely useful. I'll make you a good bet that I can switch through web pages with access keys a lot faster than you can try to do it with your mouse.
Seems unnecessarily arrogant to presuppose that while you lack such a disability, that others shouldn't.
They're called.... access keys. And yes, they are a W3 standard. KHTML is one of the first to support it.
> Is the person who invented it ashamed of it?
Maybe if you actually knew what you were talking about in this case your flaming might have some ground. Considering you don't, well, nothing. A question that now naturally comes to mind: are you ashamed of your post? Hint: you should be
. There's really no need for this type of putting-down in the Open Source community.Past that, it's insanely useful. I'll make you a good bet that I can switch through web pages with access keys a lot faster than you can try to do it with your mouse.
Its pretty clear that this feature is very useful for mouseless browsing.
The two things that should purhaps be done are fairly obviously...
1) find away to presents things in a way that it is easier for users to understand....
2) make it easier to configure how this feature works.
The two things that should purhaps be done are fairly obviously...
1) find away to presents things in a way that it is easier for users to understand....
2) make it easier to configure how this feature works.
>How the hell could this "feature" pass the KDE usability team?
> Is the person who invented it ashamed of it?
Dude, you are being rude!!!
Flaming will only get you blaming!!!
Being nice is the way to be wise!!!
first of all ARE you part of KDE usability team..? I hope not..
The access keys feature is too good to be removed.. that's not going to happen.. wanna test that.. try browsing the web without using your *mouse*. let's see how long you'd play with your TAB and Enter keys..
The only problem I see with the "Square" Boxes are 1. they look ugly because they are not transparent
2. they don't point exactly to the link.. it should be like a balloon tip which would show exact link..
I would suggest a little more smart behavior for that..
pressing and holding the associated key say 'A' should highlight the associated 'link' like a tooltip or highlighting the link or box or button with color or bold text.
> Is the person who invented it ashamed of it?
Dude, you are being rude!!!
Flaming will only get you blaming!!!
Being nice is the way to be wise!!!
first of all ARE you part of KDE usability team..? I hope not..
The access keys feature is too good to be removed.. that's not going to happen.. wanna test that.. try browsing the web without using your *mouse*. let's see how long you'd play with your TAB and Enter keys..
The only problem I see with the "Square" Boxes are 1. they look ugly because they are not transparent
2. they don't point exactly to the link.. it should be like a balloon tip which would show exact link..
I would suggest a little more smart behavior for that..
pressing and holding the associated key say 'A' should highlight the associated 'link' like a tooltip or highlighting the link or box or button with color or bold text.
Well, you appear to hate this feature but I, opposite to you, do LOVE this. It's the best way to not using the mouse! I'm used to work on my laptop using as few as i can the touchpad because the keyboard is MUCH faster.
Anyway, if you accidentally turn on this feature and want it off back you just need to press "ctrl" again
Cheers
Anyway, if you accidentally turn on this feature and want it off back you just need to press "ctrl" again
Cheers
In Amarok development, whenever someone comes up with an idea like that, we'd go like: "Dude, are you out of your mind?"
You do, eh? So where were you when your code was (is?) redirecting all buys from the music store that you link to in Amarok through the account of one of the developers? Surely redirecting buys from MY credit-card through account of one of your developers is a lot worse thing than a few squares popping up when one presses ctrl... (not saying that this is a great feature, but lets have some fair perspective here)
You do, eh? So where were you when your code was (is?) redirecting all buys from the music store that you link to in Amarok through the account of one of the developers? Surely redirecting buys from MY credit-card through account of one of your developers is a lot worse thing than a few squares popping up when one presses ctrl... (not saying that this is a great feature, but lets have some fair perspective here)
Err, that only happened in the svn version for testing. It's /never/ been in a released version. At the time buying through magnatune had a gigantic boldfaced warning anyways.
Please stop the FUD.
On topic: I find the feature useful in konqueror. I think its stupid to be enabled in all khtml kparts. Amarok doesn't need it, but its forced because khtml does it.
Please stop the FUD.
On topic: I find the feature useful in konqueror. I think its stupid to be enabled in all khtml kparts. Amarok doesn't need it, but its forced because khtml does it.
Microsoft Office 2007 uses a variation on this to provide keyboard access to the ribbon, and I don't think the idea behind the feature is daft - the implementation could be improved perhaps.
In response to the original post:
> How the hell could this "feature" pass the KDE usability team?
The team who help out with usability in KDE are not a board of people who are responsible for blocking or approving changes. They are a group of people with experience or interest in user interface design who can provide guidance and feedback. As a developer, you should know this.
>Is the person who invented it ashamed of it?
Insulting developers will never lead to a productive discussion on the subject.
In response to the original post:
> How the hell could this "feature" pass the KDE usability team?
The team who help out with usability in KDE are not a board of people who are responsible for blocking or approving changes. They are a group of people with experience or interest in user interface design who can provide guidance and feedback. As a developer, you should know this.
>Is the person who invented it ashamed of it?
Insulting developers will never lead to a productive discussion on the subject.
Ok, yes, there should be a way to turn it off, but it's an AWESOME feature. I use it all the time.
Accesibility, angry man?
Accesibility, angry man?
Have you filed a bug?
I use this feature in konqueror all the time. I wasn't aware it is enabled in amarok.
I probably agree with disabling by default.
bugs.kde.org seem like a better place to bring these things up.
I use this feature in konqueror all the time. I wasn't aware it is enabled in amarok.
I probably agree with disabling by default.
bugs.kde.org seem like a better place to bring these things up.
Ivor Hewitt proposed a nice patch to use double Ctrl click to activate these but its lost in the way, it was a cool idea :-/
Yesterday, I read an article about MS Office 2007. A "brand-new" feature was described: As soon as you press and hold the Alt or Ctrl key, all icons in the menu having a keyboard shortcut popup the corresponding character. Although there version looks much nicer than the KDE boxes, I think they just copied once again.
Of course, this shall be no proof of necessity. But it would not have become a mainstream feature if they had not tested the useability well. (OK, maybe they did not ).
If the KDE boxes would be a little more decent, this really good feature would annoy you less.
Of course, this shall be no proof of necessity. But it would not have become a mainstream feature if they had not tested the useability well. (OK, maybe they did not
).If the KDE boxes would be a little more decent, this really good feature would annoy you less.
KDE Misfeature ? Are you kidding ?
I find it feature very usefull and as someone said, it is also in konqueror.
But, i don't know why Kaffeina doesn't have this one.
Ummm,
btw. Why ?
( i begin to believe that he is kidding )
I find it feature very usefull and as someone said, it is also in konqueror.
But, i don't know why Kaffeina doesn't have this one.
Ummm,
btw. Why ?
( i begin to believe that he is kidding )
I agree with the general consensus here, that this is a really needed feature, though I don't use it myself, I sure as hell don't go screaming about it's removal beeing necessary for man's survival.
However, it could do with a few tweaks, I'll give you that. Like turning it off by default, like all other accessibility features, and most importantly, clean up the code a bit, cause if I press Ctrl on this page, I get a [7] for each reply link on it. Which one is it going to click? I don't know.
But always remember to think about other people, and their needs. It's the K Desktop Environment, not the Mark Kretschmann Solo Project. We don't all use the same features. I don't blog on the internet, but you don't see me storming the barricades, wanting to remove all blogging software, cause it's stupid...
However, it could do with a few tweaks, I'll give you that. Like turning it off by default, like all other accessibility features, and most importantly, clean up the code a bit, cause if I press Ctrl on this page, I get a [7] for each reply link on it. Which one is it going to click? I don't know.
But always remember to think about other people, and their needs. It's the K Desktop Environment, not the Mark Kretschmann Solo Project. We don't all use the same features. I don't blog on the internet, but you don't see me storming the barricades, wanting to remove all blogging software, cause it's stupid...
Yet another useless and stupid rant from markey... I wonder who you are for ranting like that when you're not even able to use thread properly in amarok.
markey, you are probably the most stupid ignorant asshole on the net.
This future is for many extremely usefull in being able to browse the net. The one who invented it should be proud and you should be ashamed!
This future is for many extremely usefull in being able to browse the net. The one who invented it should be proud and you should be ashamed!
I've had those appear in Akregator without pressing ctrl. They were a bitch to get rid of. I had to edit some .kde/ files to get rid of them. Whoever let that feature be included in the main KDE releases and enabled by default is an idiot. I'm not saying it shouldn't be included, it should just be a kcontrol option that is disabled by default.
Sorry, i'm too annoyed to read all those comments and therefor i'm sure that i has been said already:
It's a feature of the KHTML-part in Amarok, and it's for accessibility. In KOnqueror i love this feature, although not disabled in any way. Simply for using the keyboard, sometimes much faster than doing it with the mice. I guess you have to have the focus in the KHTML-Part to make the squares appear. However, pressing Ctrl again makes them go away so what are you complaining about?
It's a feature of the KHTML-part in Amarok, and it's for accessibility. In KOnqueror i love this feature, although not disabled in any way. Simply for using the keyboard, sometimes much faster than doing it with the mice. I guess you have to have the focus in the KHTML-Part to make the squares appear. However, pressing Ctrl again makes them go away so what are you complaining about?
This feature is quite important for people who can't use a mouse, so I wouldn't have it removed, or even change its shortcut to something more complex. It also works very well, despite not looking as nice as it could.
The only real discussion is if it should be enabled by default. If it wasn't enabled I wouldn't have discovered it in the first place, and you should be able to disable it if you don't need it. On the other hand, most accessibility features are disabled by default, so that is also an option.
(I also agree that the original post was way too agressive and poorly informed.)
The only real discussion is if it should be enabled by default. If it wasn't enabled I wouldn't have discovered it in the first place, and you should be able to disable it if you don't need it. On the other hand, most accessibility features are disabled by default, so that is also an option.
(I also agree that the original post was way too agressive and poorly informed.)
I like this feature as well. However, it drives my insane that it is hooked to the ctrl key as I use ctrl+arrows to skip around multiple words/paragraphs at a time. In short:
1- I press and hold ctrl because I'm thinking about changing a block of words, jumping to the previous/next paragraph, etc.
2- I chance my mind, release ctrl, and resume typing.
3- Step two simultaneously activates the access keys and provides a random letter, so the browser follows some random link on the page.
It is incredibly frustrating. I really wish there was some way to assign it to a different key. I added a comment to this regard to a relevant bug report sometime ago, but no luck so far. : (
http://bugs.kde.org/show_bug.cgi?id=89382
1- I press and hold ctrl because I'm thinking about changing a block of words, jumping to the previous/next paragraph, etc.
2- I chance my mind, release ctrl, and resume typing.
3- Step two simultaneously activates the access keys and provides a random letter, so the browser follows some random link on the page.
It is incredibly frustrating. I really wish there was some way to assign it to a different key. I added a comment to this regard to a relevant bug report sometime ago, but no luck so far. : (
http://bugs.kde.org/show_bug.cgi?id=89382
The person who put this feature in there is one who needs to be proud. Using a mouse is not something that is for everybody. IT is neede to be ableto usa a computer with out a mouse! Your second comment is really distastefull. It is not the way you make things improve.
I travel to work by train and have my laptop with me. I use this feature on a daily basis so think before you shout out loud about usability. It is a shame that this blog appeared on planetkde.
I Like it! I use in in Konqueror all the time. Especially when i'm on the road and don't have a mouse attached. You can browse with a speed, that is not possible with touchpad or trackstick. It's a real advantage over firefox, which misses such a feature.
To all the people that use this feature:
I've looked at this feature, and while it is an excellent idea, I don't understand how it can be usable for navigating real webpages. For example, it is not usable for me for the following reasons:
1. Links and fields are assigned identifiers from the 26 letters and
10 numbers. That means any screen with more than 36 elements is not
fully acccessible. Many websites I use have more than 36 links
visible at any one time. For example, most webmail sites have hundreds of links.
2. Access keys are sometimes assigned incorrectly. Two different
links will have the same associated access key, making it impossible
to click a desired one.
3. Closely spaced links cause boxes to overlap, obscuring some access
key letters.
So how do you guys use this feature with those problems? Is there a trick I don't know about?
I've looked at this feature, and while it is an excellent idea, I don't understand how it can be usable for navigating real webpages. For example, it is not usable for me for the following reasons:
1. Links and fields are assigned identifiers from the 26 letters and
10 numbers. That means any screen with more than 36 elements is not
fully acccessible. Many websites I use have more than 36 links
visible at any one time. For example, most webmail sites have hundreds of links.
2. Access keys are sometimes assigned incorrectly. Two different
links will have the same associated access key, making it impossible
to click a desired one.
3. Closely spaced links cause boxes to overlap, obscuring some access
key letters.
So how do you guys use this feature with those problems? Is there a trick I don't know about?
The accessibility features could be modal rather than triggered by a quick hit. People using them will keep using them for some length of time (including those on a train, etc.), so it'd make sense to have a modal keyboard navigation mode.
I suppose hitting escape would make Emacs people too angry... But after hitting some key to switch modes, the browser part could respond to the same keystrokes as lynx, links, or w3m. It should not invent a whole new set of keystrokes, though.
I suppose hitting escape would make Emacs people too angry... But after hitting some key to switch modes, the browser part could respond to the same keystrokes as lynx, links, or w3m. It should not invent a whole new set of keystrokes, though.
I do like this feature. Well, if it makes sense in Amarok might be a question but I love it in Konqueror.
greets, Chris (who will now Press Control, s to submit this post)
greets, Chris (who will now Press Control, s to submit this post)
@Leo S
Its evident that U don't use that feature,
As you go to explain those defects in the feature you ends saying
WTF that is working ?
I suppost that U don't bother to wonder : How we can improve this ?
If you don't need that, Why Improve this ?
Therefore, U can only suggest to remove it at all.
Right ?
Its evident that U don't use that feature,
As you go to explain those defects in the feature you ends saying
WTF that is working ?
I suppost that U don't bother to wonder : How we can improve this ?
If you don't need that, Why Improve this ?
Therefore, U can only suggest to remove it at all.
Right ?
Well yes I don't use that feature. And the reason is that it is not usable for me. The idea is good but the implementation makes it impossible to use for me. Stop putting words into my mouth saying I want it removed. I was just asking if I'm missing some hidden feature to make the access keys actually usable. It seems you use them, so how do you get around the deficiencies?
I hate that 'feature'.
I have lost countless forum posts because of it. You are happily typing away, you want to hit shift, but your finger slips - and the next moment your precious text is gone. Away, weg. Lost in the dephts of binary nirvana. No way to get it back, nothing. Or it just creates an immature post, or jumps 'randomly' somewhere.
In short, it is one of the worst features ever. Why shift? Why not 'windows' or 'menu' key? That keys aren't on my keyboard, so it could not annoy me.
And why is it on by default? Such a feature that is only interessting for a very few and selected people, should be buried deep in the guts of kcontrol. With a big warning sign 'Attention, this feature will annoy the crap out of you. Do you really want to procede?' with the choices 'no, never', 'no', 'maybe not' and, 'oh well, I exactly know what I want, so give it to me'.
I have lost countless forum posts because of it. You are happily typing away, you want to hit shift, but your finger slips - and the next moment your precious text is gone. Away, weg. Lost in the dephts of binary nirvana. No way to get it back, nothing. Or it just creates an immature post, or jumps 'randomly' somewhere.
In short, it is one of the worst features ever. Why shift? Why not 'windows' or 'menu' key? That keys aren't on my keyboard, so it could not annoy me.
And why is it on by default? Such a feature that is only interessting for a very few and selected people, should be buried deep in the guts of kcontrol. With a big warning sign 'Attention, this feature will annoy the crap out of you. Do you really want to procede?' with the choices 'no, never', 'no', 'maybe not' and, 'oh well, I exactly know what I want, so give it to me'.
Amarok Links
Calendar
|
September '08 |
|
||||
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 | 30 | |||||
Quicksearch
Archives
Categories
Syndicate This Blog
Blog Administration
We Listen To...
Powered by
