| 1 |
I'm using KDE 3.5.10 and trying to start using 4.2.0, but am experiencing |
| 2 |
severe disorientation issues. Not to worry, it's expected, but the |
| 3 |
questions... |
| 4 |
|
| 5 |
1) Where's best to ask questions such as the following, here? Upstream? |
| 6 |
If upstream, where? |
| 7 |
|
| 8 |
2) Where's the equivalent to the 3.x ksysguard kicker applet, I guess it |
| 9 |
would be the plasma applet now? The various system monitor applets just |
| 10 |
aren't as flexible as a 1920x300 panel striped across the top of my dual |
| 11 |
stacked monitors, with the ksysguard panel applet taking most of it |
| 12 |
dynamically plotting user/system/nice CPU x 4 cores, temps x 4 cores and |
| 13 |
2 system locations, 1-minute load, app/buffer/cache memory, up and |
| 14 |
downstream network activity, etc. As an example of the missing info, the |
| 15 |
CPU/core system monitor plasma applet is monocolor and lack the info |
| 16 |
detail of the triple-graph user/system/nice of ksysguard. |
| 17 |
|
| 18 |
If there isn't such a thing yet I can of course file a KDE bug, but maybe |
| 19 |
I'm overlooking something. |
| 20 |
|
| 21 |
3) One of the "extra" keys on my Logitech keyboard, XF86WWW according to |
| 22 |
xev, that I have a whole menu of multi-key hotkey entries stacked on in |
| 23 |
KDE 3.5, only yields an error saying "The key you just pressed isn't |
| 24 |
supported by QT" on 4.2. Yet xev run in 4.2 sees it, and kde 3.5 |
| 25 |
obviously uses it just fine or I'd not have all those entries stacked on |
| 26 |
it. The other "extra" keys seem to work, just not that one. It's an |
| 27 |
obvious bug. File with KDE for khotkeys, or with Nokia for qt, or ?? |
| 28 |
|
| 29 |
4) I saw knewsticker in 4.1 (which without working khotkeys was a no-go), |
| 30 |
but it seems to have disappeared for 4.2. Yes, there are alternatives, |
| 31 |
but which one of them offers the "newsticker" functionality in a plasma |
| 32 |
panel that corresponds to the way I use knewsticker (note, not akregator, |
| 33 |
installed but generally unused in favor of knewsticker) on 3.5. Is it |
| 34 |
gone for good? |
| 35 |
|
| 36 |
5) Dolphin windows take WAY longer than konqueror ever did to load. Do I |
| 37 |
need to turn on a preload option somewhere? But it even takes awhile to |
| 38 |
load a fresh window after I just loaded one, so even with it all in |
| 39 |
cache, it's still taking forever. Is KDE4 still that much less |
| 40 |
optimized? I used the same CFLAGs, etc. ~amd64 in case it matters. |
| 41 |
|
| 42 |
6) Is there a simple way to import my 3.5 color scheme to 4.2? I started |
| 43 |
with a clean ~/.kde* dir in ordered to eliminate some of the cruft I've |
| 44 |
been accumulating since 3.0 era or perhaps even 2.x, so I don't know if |
| 45 |
it would have been detected automatically or not. |
| 46 |
|
| 47 |
What about the khotkeys scheme? (Obviously right now I'd have to work |
| 48 |
something out with the dead XF86WWW key, but other than that.) |
| 49 |
|
| 50 |
7) What's a good upgrade graphics card from my current Radeon 92xx AGP, |
| 51 |
that has native X/kernel drivers and supports OpenGL at 1920x2400 and |
| 52 |
larger? The Radeon 92xx doesn't support 3D and therefore OpenGL at > |
| 53 |
2048x2048. Obviously that leaves me composite/xrender only for effects. |
| 54 |
As I said, it needs to be AGP (tho PCI-X, NOT PCI-E, would work as well, |
| 55 |
but did they do graphics cards for it that are available at a reasonable |
| 56 |
price?), preferably with dual dual-channel DVI. I don't need anything |
| 57 |
for fancy games, but something under US$200 would be nice, and it *MUST* |
| 58 |
be supported by native drivers, no proprietary crap! |
| 59 |
|
| 60 |
That one should probably go to the xorg list... |
| 61 |
|
| 62 |
8) Meanwhile, I guess I need to file a suggestion that they disable all |
| 63 |
the OpenGL effects checkboxes when only xrender/composite is enabled. |
| 64 |
They can obviously detect that they can't safely activate OpenGL as it |
| 65 |
won't let me do it, but most of the effects remain available as choices |
| 66 |
but do nothing, apparently because they simply don't work with composite/ |
| 67 |
xrender only, but they don't go disabled as they should, leaving the user |
| 68 |
extremely confused when he activates an option only to see no effect at |
| 69 |
all! |
| 70 |
|
| 71 |
Is this a currently known issue? It would seem to be self-evident. I |
| 72 |
don't want to dup-report if it's already known, but I haven't checked KDE |
| 73 |
bugs on it yet. |
| 74 |
|
| 75 |
Meanwhile, I like box-switch and present-windows for the tab-switcher, |
| 76 |
the biggest effect (other than transparency) composite/xrender allows it |
| 77 |
seems. Big improvement either one. I'll have to play a bit more to |
| 78 |
decide which I like best. =:^) |
| 79 |
|
| 80 |
-- |
| 81 |
Duncan - List replies preferred. No HTML msgs. |
| 82 |
"Every nonfree program has a lord, a master -- |
| 83 |
and if you use the program, he is your master." Richard Stallman |
Archives