On 09/05/2015 03:25 PM, Anton Aylward wrote:
On 09/05/2015 08:05 AM, ianseeks wrote:
I don't experience that at all. if i alt-f2, as i type in kwrite, it auto highlights the top item in the list. So when i hit enter it launches kwrite.
Sme here.
Look, it can just be a matter of computer speed. If something is slow to start with, but your computer is faster, than it might end up being a delay that makes no difference in practice for you. Take a system that is slower, and that same difference is going to be a deal-breaker. In software terms, your algorithm is going to break. The user is going to be faster at pressing "enter" than your system is at showing an item he can press enter to. That is a flawed design. It is deeply flawed design. If that was not a user design element but some core thing, it would mean you end up with null-pointer-exceptions and the system would crash if uncaught.
alt-f2, the micro-window comes up as near instantly as makes no difference.
I enter "k" and as near instantly as makes no difference I get a long listing. I add a "w" and the list gets shorter. The "r" and there's just the one entry.
Clicking on that, the kwrite window takes less 1/5th second to come up. Why "1/5th"? That's about the smallest I can perceive that isn't actually instantaneous.
Do you know or realise that 1/5th is a very long time? If all of the world would be delayed 1/5th of a second, so all visual, tactice and auditory impulses would be delayed 1/5th of a second as opposed to what you're used to, it would creep you out completely.
Recall this has just 2G of memory right now.
You mentioned that you had a similar configuration to "My system is 4-cores, 3.5GHz". That means your system has at least 8 times the CPU processing speed. Than my system does. Or perhaps the right calculation is 4x :P. If your delays are 4x less because of this, it might mean a horribly broken algorithm might turn into "practical usable" for YOUR SYSTEM. That doesn't mean the algorithm is not flawed, the flaw just doesn't come out in your configuration (system). It also has nothing to do with KDE configuration (as if yours is superior then). It also doesn't mean that "I" (or someone else) as a "person" has a problem. Well, of course you have a problem. That was the reason for posting this thread (these threads). It is no surprise that the user has a problem, he just told you about it. He was, I guess, trying to get it resolved in some way, or at least for people to notice it, such that, if the common consensus were to be that indeed the thing is flawed, maybe it would at the very end perhaps be wise... You know. It is awareness raising that people do in these threads, perhaps. And the experience of being too fast for that KDE thing to respond in a timely manner is real. That is not something someone makes up. It is not imaginary. So you can start out with the observation that on some systems it doesn't work. Now you say "why don't I experience it on my system?". There are several reasons that could be offered: - your system is faster - you don't use your system in the same way (you admitted that you hardly use alt-f2). Now this probably doesn't apply to that keyboard-input thing. But it does apply somewhat to alt-tab switching and things popping up with delays and all. You offer in your other reply several suggestions as to not have to face this problem. But of course all those suggestions suggest changing your style of using a computer. None of them were what I asked for really. The basic premise of having a short-cut to type in a command and have it be executed, is broken. You suggest workarounds for not having to use that style of command execution: - execute it from an open shell instead - search using a different interface element (the Gecko menu as you called it) The Gecko menu is equally flawed. If I am fast enough, I can type "kwrite<enter>" and it won't do anything. The enter doesn't register. Now I just tried again. Instead of kwrite it opens quassel. Why does it open quassel? Because my MOUSE POINTER happened to be HOVERING over the Quassel "favourites" entry. Now I try again. It filters to "kwrite" and "run kwrite". I press enter. Nothing happens. It is just horribly flawed and broken. You cannot use it in a reliable manner. Opening the "Gecko menu" by itself is influenced by the location of my mouse pointer. If it accidentally hovers over one of the other tabs, one of those tabs is selected. So I cannot use it to reliably reach any of the favourites using the keyboard.
I think you are suffering either a failure of imagination or don't really know how to configure KDE and possibly even Linux) to make life easier for you. Your posts reflect a great deal of frustration.
I think you are really lacking the imagination required to be considering that someone else might not be using your style of interaction with the system, to be honest. You also, apparently, cannot imagine that using a mouse might be a hinder, seeing as I am just using a touchpad on this laptop as I'm sitting in bed and have no means of acquiring anything better for the moment. So using a keyboard becomes vital then. You also fail to imagine that all of the window-switchers are broken for me and I am constantly disoriented by them. Switching to Konsole when I am not in it (You mentioned kterminal, I guess it's the same (alt-f2 took a second to pop down) (I thought it would never come)) is not as easily done as it is on Windows. That is, if I'm not using a mouse. So if the premise is that I avoid using the mouse, (touch pad) and alt-tabbing to my always-open Konsole is not the fastest for me, then clearly it is a lack of imagination on your side as to why it is so difficult for me to get anything run there in a moment's want. Meaning, I simply cannot blindly get something run. I constantly have to take account of the ideosynchracities of the system I am working on. It is like a troublesome housemaid. You depend on her to clean your house, but 4 out of 5 times she doesn't show up. Or she shows up late. Or she forgets that she's working for you. It's just not reliable. I can't use that. For my goals, which is speedy and controlled use of a computer. Or at least that is how I go about using it. To achieve what I want. Now you may say "I" have a problem because "I" caused my mouse pointer to hover over a location where the Gecko menu would pop up. But come on. Even when I did have a mouse I always preferred keyboard interaction because it is a hell of a lot faster. People always respond (also technical people in e.g. a Dutch tech forum) to indicate that you're using your computer in a wrong way?. That was a topic about Windows 7. I complained to them (apparently) that Windows 7 was so horribly broken in its Start Menu (yes, there is a pattern here ;-)). Haha. It was about the same thing: search. You may think Linux is a different thing but Windows and KDE are clones of each other in that regard. Utter clones. Doing the exact same thing, only not much differently. And I was just mentioning I guess there and then how I hate that search and that they ruined the configuration screen. Some nut told me that pressing the Windows button (Super, in Linux terminology) and then typing my text would be very useful and sufficient and completely adequate (!!!) in running any command I want. But of course it suffers from the same flaws as the KDE I am talking about here. (I have nothing against you! I have something against this flawed methodology!!!!!!!!). First you press Win. Then you wait a second. Because it takes time to pop up, and since it is not a key combo (like win-R) you cannot combine it with the text you would type, since it would take the first character of your text as a combination with the Win key. So since there is no good way to "consume" that Win keypress, you have to artificially wait a few moments before you start typing. It is not a flowing experience. Kubuntu doesn't suffer from this because the key combination is alt-F1, which does consume. So far so good. But anyway. I mean KDE of course. Then you type, but, in contrast with KDE, it doesn't exactly search for program executable names. However, the interface program names differ from version to version (languages). So now "win, wait, "notepad" doesn't produce anything if you're on a Dutch system. Really. At the same time you never know what it is going to find. Which means you always have to pay attention to the search results before you press enter, ideally, or risking running the wrong things if you press enter blindly. Luckily Windows still has win-R but Kubuntu/KDE doesn't. Kubuntu/KDE doesn't have an alternative for alt-F2. Or alt-F1. Both are the same, do the same thing, use the same libraries probably. Why offer the same service twice? The same product? There is hardly any difference. That makes no sense. Instead of catering to two different use cases, the two things cater to almost the same use case. From a keyboard perspective, that is. So now you have like two distinct features with an 80% overlap. Great going. Someone really thought about that. Look, if you don't even use these features, who are you to argue about it?. I'm using it and it doesn't work for me. I'm sorry, I just ended up in the wrong life. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org