qtcurve / qtcurve

QtCurve Theme

QtCurve has recently switched hosting locations to the KDE infrastructure.

The new repo URLs are:

• read-only: git://anongit.kde.org/qtcurve

• read-write: [email protected]:qtcurve

• web: https://projects.kde.org/projects/playground/base/qtcurve/repository or http://quickgit.kde.org/?p=qtcurve.git

You can rewrite your existing clonedir/.git/config to use the new URLs (or use the 'git remote ...' family of commands) and continue to use your existing clones.

More at: https://community.kde.org/Sysadmin/GitKdeOrgManual

Merge requests via http://git.reviewboard.kde.org/

Bugs/wishes via http://bugs.kde.org

qtcurve's Issues

Compilation error with qt5

qt5/style/qrgbhelper.cpp has line:

include "private/qwidget_p.h". Should it be in <> instead of ""?

Window positioning broken with qtcurve-qt5

Using qtcurve-qt5 (2117), window positioning seems to ignore the title-bar and frame. This can result in the window being positioned beyond the edge of the screen (because of the negative offsets).

It looks like this problem was introduced with the recent wmclass workaround. When I comment out these lines (in style/qtcurve_api.cpp):

    if (widget->isWindow()) {
        XcbUtils::setWindowWMClass(widget->winId());
    }

the problem goes away.

Examining the information from xprop shows that the only significant difference seems to be that WM_NORMAL_HINTS: window gravity gets changed from NorthWest (which works) to Static (which is broken).

This is using openbox-3.5.2 with qt-5.1.1, on Arch Linux.

Bad inconsistent background for detached dockable windows

It is expected to affect every qt4/kde4 app, using such widgets. Dolphin is first, i can remember.

For usual windows, including dialogs, there is normal decoration, using standard configured background, which may be not only usual gradients, but also scanlines or even tiled image.

When dockable window is not detached, it looks amazing. It seems, that it doesn't have own background, only some simplified window header is visible. But when it is detached, it is placed above some opaque aquare unrounded area, making entire look strange if header is rounded.

This "alien" background needs at least to follow window rounding parameter. Ideal - use same background as for standard window. Even without same decoration it should not look bad. Though using completely same window base (both decoration and background) as for standard window would be best (may be with option to toggle on/off standard decoration).

---

p.s. I have seen such message from thread on kde-look mention in own history reported in 2013, but can't find it. Attempt to follow drops me to last thread page. Is it already fixed in git? I currently have release 0.8.16 on both installations, one with ubuntu, another - gentoo (on both using kde).

Minimal decoration for toolbars

When toolbars are detached, they could have same border as e.g., popup menu.

Upd: I forgot, that there is already border, which may be only relief (dark/side for all or only horizontal sides), but they can't be enabled only for detached toolbars. And even with it using of menu-like possibly rounded border wiould be nice as well. Even more - all such styles could be in one list, available for all widgets, that may have it.

PLEASE!!! Open last 3 closed issues! (may be removed, just for you)

When prepare gtk3 version of qtcurve

Hi.
When prepare gtk3 version of qtcurve?

Window buttons as part of border

Don't know, how to name it better. Some themes have buttons placed just on edge. With qtcurve following objects could be included to edge:

• If etched group is enabled, than its border may be part of edge;
• Otherwise, buttons itself.
  In all cases rounding of corners, contacting with window border, should be disabled.

Also contacting may be done not only with side, parallel to header (i don't call it appear, because e.g., bespin allowes to place header on left side with essential caption text rotation), but also with side border, leaving only one corner free (for rounding).

This contact could be done automatically if buttons distance from proper side is zero.

I will try to post mockup soon.

Upd: two mockups.

1. Buttons on top edge
   
2. Joined buttons on both top and left edges:
   

Lost kwin tabs support

I remember, at least in 2010 or 2011 year qtcurve had tabs support. They had however own look. I propose to make them looking same as tabs. I have seen some options about their look in toolbar. Did not see, how it looks, but in this case header may be considered as toolbar and tab look could match tabs settings about tabs inside toolbar.

REGRESSION: Background image not displaying on window borders

Self-explanatory; background images will no longer display on borders, even if the option is set.

Ability to export plasma themes

This feature should be almost like current export to qt3/kde3 in Legacy settings tabs, but this one is not so legacy, so may be rename that tab to some thing like "Integration" or heh, "Alien".

Since plasma themes were almost never broken, and it is matter of writing SVG files, there should not be problems. When exported default theme name is "qtcurve" (if some custom unsaved configuration used) or "qtcurve-${configuration name}", in all cases user-editable.

It is really hard to find plasma theme, matching to favorite qt4 look. More likely they could first create plasma theme, than try to get as close as possible look sometimes using pixmap-based themes. With qtcurve and sometimes other engines (bespin) inversed order may be usual, since with their graphical configurator it is so easy to get wanted look without knowing of all file formats (svg graphics scheme in plasma is also some kind of format). For plasma it is especially hard if wanted theme should follow system colors, like colorbit does.

Add menu item to list of ignored by rounding

It is possible currently for many ui classes, including popup menu, but not for item. It may be handy it item is designed to cover all menuitem part between menu sides without gaps - in screenshots, which i posted with light theme, this item has style of blured back light (almost usual highlighting, but with smoothly disappearing horizontal edges).

REGRESSION: Background images with alpha broken

Background images with transparency will render over black instead of the window color.

Make unified release

Do you currently consider making a unified release from this repo which allows one to build all the ports from a single release?

Issue with background and QML integration

When using background pixmap/gradient/transparency, it integrates poorly with QML-based applications,

Related KDE bug

Window frames should be controlled by decorator settings since KDE 4.11

Since KDE 4.11 moveResizeMaximizedWindows option was removed from KWin settings.

The idea was to move it to decorators' settings. And it's already implemented for Oxygen, for example: https://projects.kde.org/projects/kde/kde-workspace/repository/revisions/8a0e134f6a2171856d163df66761922fdaad3557

QtCurve has borderlessMax option which works almost like moveResizeMaximizedWindows but it also removes titlebar. It makes sense to split borderlessMax into 2 options:

1. Remove window frames for maximised windows
2. Remove also titlebar for frameless maximised windows

Cannot connect to X server during build

I'm getting this with the 1.8.15 release tarball in our chrooted build environment:

[ 31%] Generating shadow7-png.h
gen-image-header: cannot connect to X server

This will probably be the case for many of the distros' package build systems.

BUG: Tooltips have red glow

Some tooltips, particularly those in the QtCurve options dialogue, have a red glow around them, even when red is not used in the colour scheme or the qtcurve theme. This glow color is also unconfigurable.

Some things redefine background (was: Option for widgets to redefine background)

Testing qtcurve git version, installed with live ebuild from qt gentoo overlay, i got surprise - menubar replaced window background, which has scanlines, with pure gradient with world (wallpaper, other windows) behind.

Imho, in some cases this could be even wanted for buttons or similar widgets (using bordered background). Notebook could have it too after geting transparency.

So there could be either option in each widget-related options set or separate option set with options for all gui, like rounding option set.

Allow smooth transition between active tab and contents with different transparency

I'm not sure, wether tabs may have other contents, than currently opaque notebooks, but e.g., in rekonq and qupzilla "contents" is transparent.

If i assign gradient, disappearing towards bottom, in browsers it smoothly fades into "contents" (i mean toolbars background when tabbar is above them).

But with notebook such tab is separated by border, while only one (bottom) side of tab needs to be opaque to be joined with contents.

I'm not sure, is solution possible. As fallback there could be detection of wether tabs are in notebook or may be there is better way to know target transparency for active tab.

This is to show difference:
http://wstaw.org/m/2013/12/27/qtcurve-tabs-test1.png

qtcurve-1.8.18 - background image doesn't work anymore

I've updated today to latest qtcurve-1.8.18. Now the background image just shows a black square. 1.8.17 worked flawless so i guess something in 1.8.18 cause the problem. Below is a screen to show the issue:

Qt: 4.8.5
KDE Development Platform: 4.12.1
KWin: 4.12.1

Config:

[KWin]
BorderSize=1
InnerBorder=0
OuterBorder=0
RoundBottom=false                                                                                                                                                                                                                              
TitleBarPad=1                                                                                                                                                                                                                                  

[Settings]                                                                                                                                                                                                                                     
activeTabAppearance=flat                                                                                                                                                                                                                       
animatedProgress=false                                                                                                                                                                                                                         
appearance=flat                                                                                                                                                                                                                                
bgndAppearance=flat                                                                                                                                                                                                                            
bgndGrad=horiz                                                                                                                                                                                                                                 
bgndImage=plainrings                                                                                                                                                                                                                           
bgndOpacity=100                                                                                                                                                                                                                                
boldProgress=true                                                                                                                                                                                                                              
borderInactiveTab=false                                                                                                                                                                                                                        
borderMenuitems=false                                                                                                                                                                                                                          
borderProgress=true                                                                                                                                                                                                                            
borderSbarGroove=true                                                                                                                                                                                                                          
borderSelection=false                                                                                                                                                                                                                          
borderTab=true                                                                                                                                                                                                                                 
buttonEffect=shadow                                                                                                                                                                                                                            
centerTabText=false                                                                                                                                                                                                                            
colorMenubarMouseOver=true                                                                                                                                                                                                                     
colorSelTab=0                                                                                                                                                                                                                                  
colorSliderMouseOver=false                                                                                                                                                                                                                     
coloredMouseOver=glow                                                                                                                                                                                                                          
coloredTbarMo=false                                                                                                                                                                                                                            
comboBtn=none                                                                                                                                                                                                                                  
comboSplitter=false                                                                                                                                                                                                                            
crButton=true                                                                                                                                                                                                                                  
crColor=none                                                                                                                                                                                                                                   
crHighlight=0                                                                                                                                                                                                                                  
crSize=13                                                                                                                                                                                                                                      
customAlphas=0                                                                                                                                                                                                                                 
customMenuNormTextColor=#000000                                                                                                                                                                                                                
customMenuSelTextColor=#000000                                                                                                                                                                                                                 
customMenuTextColor=false                                                                                                                                                                                                                      
customShades=1.16,1.07,0.9,0.78,0.84,0.75                                                                                                                                                                                                      
customgradient1=3d,0,1.05,0.49,1,0.5,0.95,1,1                                                                                                                                                                                                  
customgradient2=none,0,0,0.5,0,0.9,0,0.96,1,1,1                                                                                                                                                                                                
customgradient3=3d,0,1,0.85,1,1,0.92
customgradient4=3d,0,1,1,0.98
customgradient5=3d,0,1.2,0.5,1,1,1
customgradient6=3d,0,0.9,0.5,1,1,1
darkerBorders=false
defBtnIndicator=glow
dlgOpacity=100
doubleGtkComboArrow=false
drawStatusBarFrames=false
dwtAppearance=customgradient1
dwtSettings=33
embolden=true
etchEntry=false
expanderHighlight=3
fadeLines=true
fillProgress=true
fillSlider=true
flatSbarButtons=true
focus=filled
forceAlternateLvCols=false
gbFactor=-3
gbLabel=1
glowProgress=none
grooveAppearance=inverted
groupBox=line
gtkButtonOrder=false
gtkComboMenus=false
gtkScrollViews=false
handles=sunken
hideShortcutUnderline=false
highlightFactor=0
highlightScrollViews=false
highlightTab=true
inactiveTitlebarAppearance=flat
invertBotTab=true
lighterPopupMenuBgnd=2
lvAppearance=flat
lvButton=false
lvLines=false
mapKdeIcons=true
menuBgndAppearance=flat
menuBgndGrad=horiz
menuBgndImage=none
menuBgndOpacity=100
menuDelay=225
menuIcons=true
menuStripe=none
menuStripeAppearance=customgradient2
menubarAppearance=customgradient2
menubarApps=VirtualBox,smplayer,amarok,arora,kcalc,kaffeine
menubarHiding=0
menubarMouseOver=true
menuitemAppearance=flat
noBgndGradientApps=
noBgndImageApps=
noBgndOpacityApps=dragon,smplayer,vmplayer,vmware,inkscape,totem,kaffeine,kscreenlocker,sonata
noMenuBgndOpacityApps=vmplayer,vmware,inkscape,gtk,totem,sonata
noMenuStripeApps=soffice.bin,gtk
passwordChar=9679
popupBorder=true
progressAppearance=flat
progressColor=origselected
progressGrooveAppearance=darkinverted
progressGrooveColor=dark
reorderGtkButtons=false
round=full
roundAllTabs=true
roundMbTopOnly=false
sbarBgndAppearance=flat
scrollbarType=kde
selectionAppearance=gradient
shadeCheckRadio=none
shadeMenubarOnlyWhenActive=false
shadeMenubars=origselected
shadePopupMenu=false
shadeSliders=origselected
shading=hsl
sliderAppearance=flat
sliderFill=true
sliderStyle=circular
sliderThumbs=flat
sliderWidth=15
smallRadio=true
sortedLv=none
splitterHighlight=3
splitters=flat
square=1538
statusbarApps=kde
statusbarHiding=0
stdBtnSizes=false
stdSidebarButtons=false
stripedProgress=none
stripedSbar=false
sunkenAppearance=soft
tabAppearance=flat
tabBgnd=0
tabMouseOver=glow
tbarBtnAppearance=none
tbarBtnEffect=none
tbarBtns=standard
thin=1
thinSbarGroove=true
titlebarAlignment=center-full
titlebarAppearance=flat
titlebarButtonAppearance=flat
titlebarButtons=5
titlebarEffect=shadow
titlebarIcon=title
toolbarAppearance=flat
toolbarBorders=none
toolbarSeparators=sunken
toolbarTabs=false
tooltipAppearance=flat
unifyCombo=true
unifySpin=true
unifySpinBtns=false
useHighlightForMenu=false
useQtFileDialogApps=googleearth-bin
vArrows=true
version=1.8.17
windowBorder=37
windowDrag=0
xCheck=true
xbar=false

Background image tiling

Just copying report from thread on kde-look.

I tried to use this feature to texturize background:
http://kde-look.org/content/show.php?content=158464
But since image is placed only in single instance, i was forced to multiply it by size to ensure, that it will cover entire window.

Anyway, feature to set image as background overlay, instead of background itself is great.

Improve text readability with transparency

The most popular way is to reduce transparency just behind text. The only question is how better to do it. There could be two ways for that:
simple (or coarse) - Create single blurred cloud (also could be some logarithmic gradient) for entire label in alpha channel;
blurred text - according to name, blurred text copy in alpha channel. Somewhat close to that - outline in cairo-dock's dialogs and tooltips (may be disabled).

Artifacts on mouse over gtk2 gui with kwin

Most interesting - it doesn't happen with compiz, as well as other gtk2 engines (adwaita, graybird).

Wrong "gtk-icon-sizes" string.

Hi.
I have problem with really big icons in GTK apps (see attached screenshot).

When I run GTK app there is an error (for example for gtk-chtheme):

"(gtk-chtheme:6073): Gtk-WARNING **: Error parsing gtk-icon-sizes string: 'gtk-small-toolbar=22,22:gtk-large-toolbar=32,32:gtk-dnd=16,16:gtk button=16,16:gtk-menu=32,32:gtk-dialog=oxygen,oxygen'"

I'm using QtCurve 1.8.18 in Archlinux.

issue: kwin doesn't have transparency in context menu

First time i got it after kwin manual restart with --restart option (without to relogin after qtcurve from git was installed). But even after full relogin problem is here. Decoration itself is transparent. Did not test tooltip transparency yet, for me it has constant transparency even with fully opaque gradients.

REGRESSION: Toolbar gradients with alpha broken

If the toolbar has a gradient with a step that has an alpha value of less than 100%, that step is displayed as black instead of transparent.

top corners of windows not round when in windows section, select a gradient.

Hi
Excuse me for my bad english.
top corners of windows not round when in windows section, select a gradient for appearance.
look at this picture

kwin: Shadow issue on bottom rounded corners of shaded windows

Unlike upper corners shadow is not rounded, though decoration itself does.

High cpu usage with custom background images

First, it doesn't depend on wether i use tiled image option for background type, or set dedicated option, which i could call "Overlay background", which blends image (if rgba) above basic background.

Currently there are two applications, where this issue appeared clear: gjacktransport and jack_mixer, both using gtk2. Fot first it appears however only when connection to jack is enabled. I'm not sure, what is reason - slider or may be label, displaying position at timeline. In case, when cpu load is about 10% or a bit lower, with enabled image it may reach 50% (on older laptop with athlon64 x2 at 1,9GHz it was so).

When got it with jack_mixer, i was sure it is python trouble, but when tried again with simple plain style, problem disappeared.

I hope, it could be somehow optimized. I made theme, utilizing shader image as overlay specially for such pro-audio look with dark colors, but it seems really more good to show rather than to use. Not sure about qt4 however.

Window buttons as on toolbar

On last screenshot, posted in comment for bug about toolbar decorations you may see window buttons, whose looks is indeed very close to toolbar buttons without joining, but smaller (12 - 8 pix). Window buttons settings tab includes option to enable etched background, but it is not perfect.

My proposal is to add two toolbars, on the left and right sides. They may include window buttons and separators between them, just according to kwin buttons settings.
Expected improvements:

• Ability to use any gradient for toolbar. It could be also copy of current relief like transition from 10% black to 10% white (percents are about transparency) or something better. This gradient could even have border. Old (current) option "Etched background" could just enable/disable toolbar gradient/border.
• Toolbars may use joining for groups, after proposed improvements it should look awesome.

All necessary toolbar settings could be redefined for window toolbars, just like toolbars allow to inherit or override button style for toolbuttons.

migrate titlebar and menubar

Please migrate titlebar and menubar as when I hover mouse on title of window, menu of window appear.
Thanks alot.

Per-application and per-window profiles

I recently got the fact, that in osx panther or jaguar aqua used different styles for different apps, having even some guidlines. E.g., iTunes used brushed metal, while text editors had style with white background and scanlines.

Baghira - dedicated engine for kde3/qt3 - allowed same with selection by application (command line, i guess), but not for different windows of same app.

Implementation:
One config could have several profiles, which are currently synonim for configs. I guess, it is possible to make difference not only by app name, but by window xprops too, as currently oxygen allowes (if built with x11 support, not sure, is there some universal way for that).

Compatibility / import / export:
Styles could be imported from other presets. If specified preset includes several profiles, than user may specify, what styles to import. In qtcurve config gui this dialog may include table with 3 columns: import checkbox, profile name, new name after importing (necessary of two configs have styles with same name). For legacy configs their name is used for new profiles.

upd: According to info from abandoned baghira site, there was applet to switch style for any window during work, just as kwin allowes to do it for single window.

upd2: Just for example: http://baghira.sourceforge.net/advanced_tutorial-en.php
And for oxygen: it is only for kwin. Accepts window name and class, but there could be even custom properties (allowing to specify for property not only value, but name too, with some presets).

Borders antialiasing for qt?

I recall mentioning of drawing technique, used in qtcurve, in which background was painted with antialiasing, but border is not. I honestly can't understand, how much speedup may be from such degradation, since it is just a contour (disabling it for filling would be more resonable for this case). I just looked carefully to qt4 buttons and noticed result: very tiny edge of antialiased background is visible after unsmoothed border on corners.

With gtk2 all looks fine, as it uses antialiasing. And also for qt4 corders with rounding below max (extra or below) on buttons have pure visual roundness, comparing to gtk2.

p.s. First time i guessed it is pure antialiasing quality in qt4 version, yet when i used max rounding. Looks strange, seens it is known, that qt4 supports even subpixel graphics, while for cairo it fallbacks to usual method.
gtk2:
qt4:

Improvement proposals for dial, knob and wheel widget

I don't know honestly, is it defined in qtcurve at all, or it just doesn't have default implementation. But if defined - would be nice to improve it. But looking to dependencies of VMPK (Virtual MIDI Piano Keyboard), which may have them on toolbars, causes to think, that qtcurve implements it - there are no other additional widget libraries appart qtgui.

Many known qt4 engines have good usable implementation of dial. One minimal and fine example is in skulpture. I can't show special case, demonstrating it, but there is screenshot for qsynth in official site, made using this style: http://qsynth.sourceforge.net/qsynth-index.html

But qtcurve implementation is not so comfortable. Current implementation is relatively big circle with fixed size and fixed distance from edge, where fixed means unaware of dial diameter. This makes wheel unusable with small size.

Looking to style with different themes makes to think, that handle currently uses button look (i tried with my light aquish style, which is btw not mine but for mother =).
There are several ways to make it better with small sizes:

• Scale handle with wheel;
• Handle may be placed so, that edge cuts it upd to half. This should even make its position sharper for perception;
• Also there could be some more exact linear mark, with almost same configurability for relief and other look aspects, as most borders, separators, etc. This mark could be combined with cut circle on edge, seems to be best.
• Optionally there could be some more mark, like som scale, but i'm not sure, is it to be defined by theme or it is widget's property (scale). At least in qsynth with skulpture style dials have something looking like scale, which is not displayed for qtcurve style. So scale could be also enabled/configured.

Mockup without optional scale:

This screenshot is made with qtcurve 1.8.14. There are some problems with label, also appearing with 1.8.17. There could be option to disable it as well. In some cases there is special numeric view for such purpose (again, qsynth).

Horizontal gradients

Two gradients, horizontal and vertical in simplest way could just multiply, resulting into area gradient. Another, probably better way: imagein e.g., rectangle rounded button is painted by line, placed and rotating in button's center. Line connects real border of widget, not bounding box. Gradient to draw with should be interpolation between horizontal and vertical samples.

First way could be simpler. but not so aware if real widget's geometry - i.e., only for square widgets with possibly tiny rounding or other deviations.

Issue with display of contents in rounded views

Includes two issues, which are betst visible with some rounding.

1. When border gets rounding, its orthogonal sides are placed on some distance from contents so, that rounding arc goes through unrounded contents angle.
2. Even if 1st is fixed, it will not look good if contents is above border.

Oxygen is one good example, how to do it. No idea how, may be ony contents background is expanded, but foreground is not. But i don't see problem if foreground will be covered with such small rounding, as now.

Affects both qt4 and gtk2 (twf behind designer)

[GTK] misaligned fancy background

It seems like the margin or padding or something isn't taken into the account for painting the fancy background stuff.

Pretty low importance, but I thought I'd add it here for tracking anyways.

please make shadows optional

Hi!
Sorry for my English.
QtCurve has very impressive features to provide for comfortable work at X terminals (LTSP) - simple widgets without gradients, etc.
While the window's shadow can be turned off, some widgets do not have that option.
Please make shadows optional (popup menus, combos, hints, etc.), it will be very helpful for X terminals in order to reduce traffic and improve responsiveness.
Many thanks.

Strange ugly tooltip look with rounding and flat style

First time i was sure that it is bad border stuff. But looking closer, as well as comparing with other gradients, it seems, that it is not so.

Flat rounded tooltip has unrounded opaque square above and some rounded, element behind with text color, which was guessed to resemble border, but looks well only without rounding.

Upd: screenshot

upd: Problem doesn't appear with custom gradient, cloned from flat style even without changes. Also affects raised style (or etched - anyway, in list it goes just after flat).

Optional visibility for window header.

Under header i mean currently horizontal bar above window contents, which could be removed. Essentially it is not for all, but some people (more frequently using various lightweight wm) use only border, without header. In kwin buttons settings i tried to remove text - seems untuchable :)

Option to apply gradients to some borders

I recall some themes, mostly for plasma, where side borders on buttons are affected by some gradient as well as filling. Such option could be even part of style (which is currently called custom gradient, regardless that also has associated border type).

In one case (if more are possible) it could be just a gradient, multiplied due to lighting.

Window header orientation

Another feature, likely to be with lower than normal priority. As i said in previous issue, but more completely: bespin has option for some "netbook" mode, when caption is placed on other side. Some wm (enlightenment) allow to place header on any side.

Make scanlines "gradient" inheritable

I don't know, is it possible, since there is only one case, when it is available - window and menu background. The problem is in its border type, which is not best - 3d with light part only. When i try to add border to floating menus, it adds both black outline and gradient's own border. With scanlines its look could be better. Currently i'm using inherited plain style with light-only border. This makes sence.

Proposals for toolbuttons in joined raised mode

When toolbuttons are not joined, they always have some space between them. When mode is changed to joined, it seems, that visible size of contacting button edges from same group is slightly increased so, that they barely become compact. It looks possible for joined buttons to seamlessly remove space for glued buttons. As result, compactness should increase.

And about separation look: appart separator_above_single_button style, it could be just separate buttons with zero space between them and removed rounding for contacting sides. Like this:

Current:

/——————————\
|    |:    |
\——————————/

Proposed:

/————:|————\
|    :|    |
\————:|————/

And another drawback of current implementation: if separator style is not fading, than it has raised look. For plain style it would be better for it to not have even shadow - it could be rather some shared side for both buttons.

More usage of blending for borders

First case, where it may be important - common border, claimed used for most widgets, on settings tab "Custom shades" it is last (6th). For widgets, placed above opaque parent, it looks as expected. But if placed above transparent background and it has some black area behind, than with light color scheme expected this border appears darker than its widget, but lighter than resulting background.

I guess, it is because its color is precalculated for opaque background. For transparent areas border's alpha value could affect resulting window alpha mask.

Same is appliable for menu border. When transparent menu with opaque border is above area with contrasting color, look is nice. But e.g., near to light menu above light area needs brighter border. Again, shading the pure white border above menu background should make difference always same.

Standalone qtcurve config gui

Current gui is implemented as kde systemsettings module. If gui uses only qt4 stuff without kde-specifics, could it be used both in control center and as standalone?

groupbox: Background shading with simple border

First issue i have to point is that shaded background with zero shading has same look as simple border.

More correct implementation should allow shading for both simple and relief border, as it is possible. In this case shaded background could be renamed to sunken (raised could be added as well).

Plain shaded box would be handy for relief-less plain styles.

More correct pixel positioning

I can guess, this trouble could cause original author to disable antialiasing for contours for sharp look. Same problem may be seen on recently added tooltip border - horizontal and vertical lines are thick. Tooltip borders actually look better above background with moderate colors, but above something black (xterm) problem appears clear.

Pixels are squares, and exact integer position usually points not exactly to pixels, but between them - i got this much time ago from some cairo-dock docs.

I.e., for point 10,14 exact coords parameters should be 10.5,14.5.

Transparent gradients in windows

Copying from thread on kde-look.

When i worked on plain glowing theme for dark color schemes, which uses Simple shading mode and controls, whose custom gradients consist of pure white color with transparency ≈10—30%. For buttons such gradients look as expected, but for tooltips it is just a white. Though it is not good, and 150% brightness with 40% alpha should be good as well (due to inability of first solution to follow color scheme), it just showes, that tooltip are drawn on some own, old way, responsible for both problems.

Also, when i tried to set such gradient to window background, its header looked transparent, but window body did not.

GTK2+ applications don't start

Hi,

I have problems starting up easytag if qtcurve is in use. I have 1.8.17 here, it works if I use 1.8.16 with the runCommand patch and start it in strace.