Bespin

Be-Shell/Bespin by thomas12777 1663 comments

No, bespin transition settings.
You'll have to "kquitapp plasma-desktop; sleep 1; plasma-desktop" afterwards but i've identified and "fixed" the problem (unfortunately it's part of a workaround that _was_ necessary then, but is apparently not with current Qt versions. I'll do some testing and commit the fix (removing the workaround) in case it doesn't cause major regressions (like crashing applications...) - Aug 06 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

yes, indeed. this works ... again ;-)
(i recall it was somehow broken and the event reported some junk - here at least - when the button grabbed the pointer and the cursor was outside.

Though mapToGlobal _is_ broken in 4.8 beta (check k-c-d mailing list) i've changed the code to use the now working more strainghtforward routine.

Thanks for the hints (both, broken and fix) - Aug 06 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

got it.
it's important to have that kickoff at the scree bottom. in a top panel it doesn't happen.

also it _is_ related to animations, i assume the window renders with some wrong offset when redirected into a pixmap. no idea. gonna investigate. - Aug 06 2011
BeClock

Various KDE 1.-4. Improvements by thomas12777 285 comments

Nevermind.
What should be about that option? It's present and works here (though my version is slight ahead of the release but i don't think anything in this regard)

Is the option absent or just not working? - Aug 03 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

No, nothing like this - is it related to animated tab switching? - Aug 03 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

just to be sure - you're using kwin and NOT compiz + kwin-decorator?

Otherwise there's probably a change in the Qt behaviour (i remotely recall some rumble about this) in mapToGlobal()

please edit kwin/button.cpp:229/230
->
const bool under_mouse = underMouse();
in doubt even try
const bool under_mouse = true;

this however will change behaviour and you can NO MORE ESCAPE from eg. close button clicks by dragging away the pointer! - Aug 03 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

There's currently no config entry for shadows.
I'll likely add one (in order to support sth. more like a halo than a shdow - for dark setups) as well as an effect plugin to add them to a selectable group of other windows (like gtk+ popups etc.) as well. But not tonight ;-) - Aug 02 2011
BeClock

Various KDE 1.-4. Improvements by thomas12777 285 comments

The "flashing" (fade out/in) is expected yes (3 times. does that fit your observation?)

The hiding is not. Neither is the overexposure ("darker tone than the selected")

Can you please mail me you ~/.kde/share/config/kwinrc and (esp. in case you're using the GL backend) a dump of "glxinfo"?

Wild shot for you to try before: disable blurring, see what happens. - Aug 02 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

Hehe - some things i do know ;-)
(the chances that a non showing up widget style is NOT an unresolved symbol are neglectable)

The "serious" issue here was - as predicted (sorry, i need that :-) - the unresolved symbol, but since libQtBespin is not public, it's never good to have it outdated compared to the style/deco (i might just change logics in both and if that doesn't apply to your version, you experience strange things. Maybe i should add a runtime version check with a big fat warning dialog on failure =)

The shadows should now be in pretty good shape but there hade been valid issues as you can read in the posts above (worst one being them not working on the raster graphicssystem)


No problem bothering me, btw. Not at all.
Better this way than ending up a "bespin sucks" in your mind. - Aug 01 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

No, different numbers are ok.

readelf -sw /usr/local/lib/libQtBespin.so | grep clean

readelf -sw /<where-is-my-cloudcity-repo>/build/lib/libQtBespin.so | grep clean - Aug 01 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

this usually means an unresolved symbol in the library. ensure you're linking the proper version of libQtBespin (it got a new symbol that revision)

please check where you "make install" libbespin.so and "ldd /path/to/that/libbespin.so | grep libQtBespin" - ensure that it's the same version you "make install"ed

if everything's fine here (but i doubt, given the style doesn't even show up in qtconfig?)
I'm not sure what you meant about kwin, but it links libQtBespin as well, so the bug is by 99.9% chance there.

in doubt, just try to compile from a fresh build dir. - Aug 01 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

THe reason for the glitch is that kwin/GL cannot handle shadow pixmap size changes (i guess it always keeps the texture, may be bug or intention) -> worked around in 1389 - Aug 01 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

ok, check r1387, should support non native backends. The GL shadows break on change (activation) here nevertheless, xrender works fine -> kwin or nvidia issue :-( - Jul 31 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

a) please ensure to install r1386 - 1385 has an ugly "bug" (i was probably mentally absent when writing that) which could potentially cause segfaults all over the place (depends on whether NETWM_SUPPORT has >= 66 entries ;-)

b) d'ooh - you're probably using the raster graphicssystem - i forgot to add support for that... try "kwin --replace --graphicssystem native", since the popups will in doubt share the kwin shadows, this hits everything. sorry. - Jul 31 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

No idea why you didn't see them with 4.7rc2 before but you'll have to recompile te client once you got 4.7 final - there's no runtime check on this. - Jul 28 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

There should be no shadows on them at all - ultimately they'll use the new system as well and then i'd "steal" the custom shadow.

The bug was just that the code was too agressive and put shadows on all ToolTip windows, not only the QToolTip ones and their inheritors as it should be.

-> should be hotfixed in r1384 - real fix (better and generic implementation this WE - hope for rain ;-)

Btw: are you using an nvidia chip? The shadows somtimes look strange here (i think due to GL_LINEAR stretching, does not happen with XRender) and i wonder whether this is an nvidia issue or a genral one. - Jul 28 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

Actually i just see that the new shadows are activated regardless of the kde version but only on window activation.
Since however they're broken in KWin < 4.7.0 you might (luckily) not see anything - in worst case you see quite some artefacts...

r1383 adds the version check and you should NOT use the new shadows for the decoration on early kwin versions - seriously, looks horrible ;-) - Jul 27 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

Actually David and Rob lately asked me whether we should start over some icon work. I want to, but they want me to take the lead (we need to do this, do that) and i've so far not managed to write a list of "has to be done" :-(

I've just opened a wish here:
http://sourceforge.net/tracker/?func=detail&aid=3380176&group_id=201276&atid=976910

where you can just post icons you demand most - Jul 27 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

shadows are there and operative since 4 days (r1382 ;-)

For the kwin decoration you must have KDE 4.7 (*not* rc2)
The style so far only applies them to popup menus (and docks, i think) - i guess i'll somewhen this WE write a more generic solution so i can add tooltips and combobox dropdowns (and whatever else i get aware of) - Jul 27 2011
BeReflected

Various KDE 1.-4. Improvements by thomas12777 36 comments

I simply could have said it isnted of using an error prone game... :S

Nevermind =)
Also, you're attacking sf.net - i don't care too much and they can probably take it ;-) - Jul 20 2011
BeClock

Various KDE 1.-4. Improvements by thomas12777 285 comments

I just wondered - i actually put a hint in the CMake if the headers aren't found ...
I've updated the text (but there's no functional issue)
And yes, KDE was resplit with the git migration (4.6, intersting that Ubuntu alignes the names NOW :-) - Jul 19 2011
BeReflected

Various KDE 1.-4. Improvements by thomas12777 36 comments

> Anyway quite frankly I'm not sure about this one.
Have a _very_ close look: it's NOT a preset.

Now bring in
> Glad to see you like bespin and working on improving it.

And now realize what's "wrong" about it =)
(HInt: i don't precisely "like" bespin - the relation is somewhat different)

(The scrot is btw. nearly 5 years old - from a time when KDE4 hardly existed at all - the window Decoration is emerald) - Jul 19 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

and looking at the FAQ myself, the plugin name has possibly changed to "globalmenu-gnome" - Jul 19 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

No idea, worked w/o any problem for me.
You can probably get support from the ggm maintainers:
http://code.google.com/p/gnome2-globalmenu/
(best contact their FAQ/Wiki before ;-) - Jul 19 2011
BeReflected

Various KDE 1.-4. Improvements by thomas12777 36 comments

> Glad to see you like bespin and working on improving it.

click on my name, select the artwork tab, look at entry #5 ... ;-)

I don't think i ever published the wallpaper.
-> http://imageshack.us/photo/my-images/850/verticalw.jpg/ - Jul 19 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

1. "export" - you'll have to do that everytime you login and at a shell level the application will see when it's started. (kdm should interpret ~/.xprofile, so you could place it there. Another place would be /etc/profile or /etc/profile.d/activate_ggm.sh - last option needs to be supported by your distro (ie. there's such a directory and it's full of files) and the file must usually be executable.

2. Yes, as expected. You'll have to configure the decoration for not bespin-styled applications as mentioned. There's no way to do this programatically.
You can choose from various grounds, title backgrounds & colors. You can also apply regexp matches for several configurations.

You can just type "svn log" in the bespin source directory to see what happened and iirc sf.net has a feature to "track" a project, whether this will send you mails on commits, i frankly don't know. - Jul 15 2011
BeShadowed

Various KDE 1.-4. Improvements by thomas12777 75 comments

The effects API of 4.7 has changed in major aspects.
KWin 4.7 also has a new shadow system which at least bespin will use (so i intended to let BeShadowed die - shout if you need it for other decorations)

Unfortunately it's broken in _all_ release candidated but should work ok in the release, so this is when i'll activate the code.

Until then you'll have to live w/o shadows for everything but the oxygen & aurorae decorations (which paint the shadows in the decoration) :-( - Jul 15 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

1) it works with gtk+ ones but you need to install the gnome-global-menu plugin (you don't need the menu but the plugin for the applications) and "export GTK_MODULES=globalmenu-plugin"

2) I do not know what this is supposed to mean but assume that refer to the fact that the decoration has no idea about the look of clients which are not styled by bespin (no there is no and will not be a gtk2 style, maybe gtk3 - i don't know yet. Gtk2 is simply not capable of the default bespin look, ie. invert button colors on hover.)
-> you'll have to configure the decoration for other clients: "kcmshell4 kwindecoration", select bespin and configure the decoration.
xwininfo or the "info" button for the kde multibutton are your friends to figure the matchline.

3) -> http://kde-apps.org/content/show.php/BeShadowed?content=121607
The KWIN shadow system will also change completely for 4.7, obsoleting BeShadowed. (but due to a bug present in all release clients, this is so far not supported by the kwin deco atm. Will be with 4.7.0 release)
4) "works for me", either by alt+f3 menu or "kcmshell4 kwinrules" - the special setting in oxygen is more or less only there to keep the client side shadows when there's no decoration.
For 4.7 sth. similar would be required for bespin (to keep the shadows), but we'll have to revamp the entire decoration spec anyway - so i'm likely gonna add a temp. hack that will provide shadows for undecorated windows then. - Jul 14 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

Doing this from a style workaound is nearly impossible :-(

I'd have to catch and override the widgets input handling and painting, since dolphin does this itself (and in a way that does not even work when highlighting the entire row (rather than the element) as it's done usually in bespin (dolphin more or less hardcodes the geometry & clipping)

The result would be incredibly wonky and fail the moment dolphin adjustst the widget even just slightly.
It's not like i'd like the current behaviour (using the name and ignoring the metadata region would have been sufficient) - Jun 13 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

That's pretty much how things look here.
If you set the tab color role to WindowText, isn't that what you want?
I mean, where does the dark grey come from? - Jun 13 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

If the grey is that dark, why do you set the according foreground role to black in the first place?

"What do you think"

This was exactly what caused quite some trouble with baghira's coloring :-(

It's all fine as long as the widget uses the standard palette, but the moment it deviates, you might end up seeing black on black.
Or you'd have to deny widgets own palettes in general, forcing everything to use the application palette...

KHtml's color usage (page css) sucks enough :-(
Not to mention widgets hardcoding colors (for dark on bright everywhere) or utilizing qss...
(I guess the best thing was to hardcode windows colors... *sigh*) - Jun 13 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

Nope. Most foreground colors are automatically calculated from the background color (using the opposite rule)
Custom colors was a troublemaker in baghira, so i removed then and reset all coloring to the roles.

Any particular reason for this request? - Jun 12 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

Interesting. I wasn't aware but the kcm actually shows this behavior.

I'm not sure whether this can be changed since the kcm apparently triggers this from some signal.

However just calling "bespin [config, opt. parameter]" will launch the standalone config which does not exhibit such weird behaviour ;-)
"bespin help" will show you some CLI functions you might find useful if you deal with presets.

I'll somewhen have a look on what causes this from the kcm. - Jun 06 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

The Bespin style hints the window content to the decoration. For Gtk+ applications this is abviously not possible (esp. not because bespin isn't styling them)

If you select one of the last three decoration bases (Flat/V Gradient/H Gradient) for "Default" decorations (or any special subset you which to apply this look to) the splitter will go away (and the decoration in general more behave like with Bespin styled applications)
Otherwise it's simply assume to be a good idea to have it there for a more classic look. (Since the decoration has not the least idea about what's a few pixel below) - Jun 03 2011
BeClock

Various KDE 1.-4. Improvements by thomas12777 285 comments

The xrender libs aren't linked, what means there's a good chance they were not found when cmake configured. Post installing them successfully added headers and functions but not the link.

Most simple solution (likely): delete the build dir and run the configuration again.
You could also ccmake, press "c" and ensure the xrender targets are found. - May 08 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

It's rather intel's fault :-(

I've seen this before.
The painting isn't clipped for whatever reason (it's just a stupid qpainter call - i unfortunately failed to figure and i've no intel chip to check myself)

Disable all "glassy" settings to work around this :-(

If you compile yourself and are willing to work this out (look for a fix/workaround) drop me a mail (address can be found in every header file) - i'd like to get rid of this issue. - Apr 29 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

No, the setting is hardcoded (atm and for a while ;-)
- see stylehint.cpp /SH_ItemView_ChangeHighlightOnFocus

Partially to trigger reactions. Any particular concerns or just a "i don#t like changes" feeling in your gut?

The reason is that at this moment the element does no more actually have the focus, so it shouldn't feign it.

(I also tried partial desaturation, don't ask - looks weird because it introduces a new color) - Apr 29 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

Ok, got it.
It's an application issue. The wizard makes certain assumptions about the button layout what is wrong (but also hardly documented -> Qt's fault ;-)

To workaround you have to uncheck the "maccish" box on the "input/System" page.

I've contacted the developer explaining the issue and how to fix it (it's "hard-broken" on OSX this way)

I assume the color thing in kpackagekit is on an inverterd background? That would be a hardcoded color (welcome to the windows user world where everything is black text on a rather bright background :-(
In this case it won't fix from here (you'll have to disable the inversion of modal dialogs) - sorry. You'll have to tell the packagekit developer to not hardcode any colors but use colorroles instead (while i'd bet it's a qss abuse)

If not, please make a screenshot (i'm not gonna install that) - Apr 14 2011
Batman Forever

Fonts by zhenniao 4 comments

No idea whether he's the creator, but the font (/this/ font, /this/ file, with /this/ hash value) exists since at least ~1998 ... - Apr 13 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

I'm sorry, but i've no Bl├ątand devices - so i'll need some more specific instructions.

Is this http://kde-apps.org/content/show.php/kdebluetooth4?content=84761 or some plasmoid (in doubt make a screenshot) - Apr 13 2011
Batman Forever

Fonts by zhenniao 4 comments

no harmful content, to be more precise it's exactly this font:
http://www.dafont.com/batman-forever.font

(non hollow variant, same md5sum) - Apr 11 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

Ah, ok.
No - there's never been sth. but the zoom.
The Buttons however behave different in the connected mode - the background then performs a color fade. - Mar 28 2011
Bespin

Be-Shell/Bespin by thomas12777 1663 comments

"bespin config", "Button" page. Select "Toolbuttons" (2 page toolbox - unideal design...) and pick a variant.
Notice that
a) the desaturation won't work with the monochrome (black by default) bespin icons (or any other grayscale set)
b) the "KDE or Qt" variant /might/ to lead to inconsistencies between KDE and pure Qt applications (while i guess that's meanwhile covered by the platform plugin) - Mar 27 2011
BeClock

Various KDE 1.-4. Improvements by thomas12777 285 comments

it's likely a driver bug - i assume you use fullscreen unredirection?
"kreadconfig -file kwinrc -group Compositing -key UnredirectFullscreen" - or check the setting in the GUI for KDE 4.6
Does it happen with both, GL & XRender backend?

I just learned that kwin wastes some CPU cycles in FS mode anyway since it doesn't collect "offscren" damage events, repaint requests.

4.7 will likely either not unredirect or entirely suspend compositing, depending on a hint on the window.

However there's few i could do to prevent this (neither the presence of a fullscreen client nor it's unredirection state is published to the effect plugins) -sorry :-(

---
About the panel: no, it's not plasma but a handcrafted Desktop Shell, never released. - Feb 28 2011
BeShadowed

Various KDE 1.-4. Improvements by thomas12777 75 comments

KWin's GL backend is getting some serious major changes due to the GLES support.
For the moment, you can just copy the function from 4.6 to the head of the sources.

I'll assemble an update after the next local branch change - so far i'm waiting for a call up commit some bugfix changes to 4.6 & master. - Feb 12 2011
BeClock

Various KDE 1.-4. Improvements by thomas12777 285 comments

Yes, it's konsole.
Decoration is bespin - konsole uses a (black) preset (which also triggers the matching decoration color)

However i think meanwhile more KWin decorations can actually do this. - Feb 10 2011
BE::MPC

Audioplayers by thomas12777 40 comments

2) was supposed to be fixed with 0.6 (did i upload the wrong version then?)

1) errr... don't have access to that old KDE/Qt.
-> Does it happen with any other style (or all oxygen animations turned off)? - Feb 09 2011
BeFaded

Various KDE 1.-4. Improvements by thomas12777 19 comments

No, effects cannot toggle other effects.
Use the setExposure workaround - future versions of KWin shall hopefully get rid of this issue anyway. - Jan 31 2011
BE::MPC

Audioplayers by thomas12777 40 comments

bespin. the reason is an insufficient setup of the StyleOption (since QLineEdit adds some extras i didn't think of)

I'll release a fix later on.
No idea about why you can see the playlist buttons (well, because they're actually part of the window widget, but they should be hidden with the playlist)
I couldn't reproduce this here at all (with no style) - any hint on how to do that? - Jan 30 2011
BeFaded

Various KDE 1.-4. Improvements by thomas12777 19 comments

This is a structural issue with the KWIn renderstack which allows only one plugin to expose the window.

The blur plugin exposes them by 1 or 2 px what's not sufficient for shadows.

Using shadows built into the deco or disabling the blur plugin will probably "solve" your issue.

I'll add a config value to artificially increase the repaint area, but the blur/shadow exposure clash will hit you in other places nevertheless. - Jan 30 2011