SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm testing KDE 4.2.4 in Slackware (current) and a I notice if I click a lot between device notifier,application launcher (the new), system operations dialog (the i in the task bar), show me desktop and the workplaces. All thing breaks lose and the (i) on taskbar stays on but i can not see the file operations dialog anymore. The device notifier list and the application launcher disappears also.
Is this a bug or I'm getting too hard on it?
Patient: "Doctor, it hurts when I do this!"
Doctor: "Well, don't do it then."
Probably a bit of both. Obviously, it shouldn't get itself in a mess, but I think that currently with KDE you're lucky if it works when you use it as intended. If you start stress testing UI elements, then I'm not surprised if it gets a little confused. I'm sure the KDE guys will work on the robustness of the UI as time goes on.
If you start stress testing UI elements, then I'm not surprised if it gets a little confused. I'm sure the KDE guys will work on the robustness of the UI as time goes on.
I do not see how one can stress test a UI element since, as far as I understand, it processes messages one at a time and it makes absolutely no difference how often it is clicked. Thus, the "work on the robustness of a UI" sounds like "compensating for fundamental design faults" to me.
I did not analyze the code, but from the end user perspective KDE 4 looks like Windows - having fundamental problems that can be forced to pop-up less frequently by debugging and patching but cannot be eliminated.
However, I believe KDE is the only option for those who are not happy with XFCE and there is no sense in looking back.
I do not see how one can stress test a UI element since, as far as I understand, it processes messages one at a time and it makes absolutely no difference how often it is clicked.
A single element perhaps not. I'm not that familiar with the KDE codebase either, but I get the feeling that the KDE/plasma desktop design is more of a collection of individual parts that interact and cooperate with each other (i.e. A big ball of wibbly-wobbly-codey-wodey stuff).
As you say, the messages are put on a queue and taken off in sequence, but once they've been received the individual processes still need to act on them, and that's where you can experience these race conditions. So it's probably quite possible to get weird interactions when clicking this and that and this and that and that and this and the other, rapidly.
I've used WindowMaker for a good few years now and am happy with it. I'm a firm believer in the UNIX philosophy of writing small tools that "Do one thing, and do it well". I guess most people would consider me a luddite. Clearly, KDE is the exact opposite of this, and not to my tastes at all, but if they want to have a go at creating a complex and highly integrated desktop to rival Windows 7 and OS-X then I wish them well and I'm not going to criticise them if they make a few errors on the way.
...I get the feeling that the KDE/plasma desktop design is more of a collection of individual parts that interact and cooperate with each other (i.e. A big ball of wibbly-wobbly-codey-wodey stuff).
"wibbly-wobbly-codey-wodey stuff"
I am going to add that phrase to my technical vocabulary.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.