Build failed in Jenkins: plasma-desktop_master_qt5 #48

See Changes: [scripty] SVN_SILENT made messages (.desktop file) -- Started by remote host 127.0.0.1 with note: Triggered by commit Building remotely on LinuxSlave - 4 (PACKAGER LINBUILDER) in

Build failed in Jenkins: plasma-workspace_master_qt5 #77

See Changes: [hrvoje.senjan] --deprecated -- [...truncated 1359 lines...] : In member function ‘void Klipper::sa

Build failed in Jenkins: plasma-desktop_master_qt5 #47

See Changes: [lueck] Add info about options on Advanced tab of keyboard kcm docbook -- Started by remote host 127.0.0.1 with note: Triggered by commit Building remotely on LinuxSlave - 4 (PACK

Review Request 117632: Plasmoidviewer-Frameworks: Enable the konsole and fix the spacing.

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117632/ --- Review request for Plasma. Repository: plasmate Description --- Th

Review Request 117631: Plasmoidviewer-Frameworks: The konsole button should be visible only if the konsole is enabled.

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117631/ --- Review request for Plasma. Repository: plasmate Description --- Th

Re: RFC: plasma tooltips animations

On Fri, Apr 18, 2014 at 7:45 PM, Marco Martin wrote: > as far i know, the size should be correct, that strange animation and > immediately disappearing, no. So I will have that much big tool tips? It appears in correct size only *once*. > can you report a bug with that gif? Reported, and assumi

Re: RFC: plasma tooltips animations

On Friday 18 April 2014, Bhushan Shah wrote: > On Fri, Apr 18, 2014 at 6:16 PM, Bhushan Shah wrote: > > Well, it is big enough so it appears below mouse cursor and hides so, > > hard to get screenshot.. maybe let me try gif.. :P > > So here we go.. http://i.imgur.com/Fw3dW7c.gif as far i know, th

Re: Re: Re: Defaults: panel on each screen?

On Friday 18 April 2014 15:17:52 Martin Klapetek wrote: > On Fri, Apr 18, 2014 at 2:52 PM, Martin Gräßlin wrote: > > That's a setup I have but I never really considered it as a problem. I > > have > > two screens and the only panel is on the absolute left as a vertical > > panel. > > > > If I don

Jenkins build is back to normal : kinfocenter_master_qt5 #14

See ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel

Re: RFC: plasma tooltips animations

On Fri, Apr 18, 2014 at 3:23 PM, Bhushan Shah wrote: > On Fri, Apr 18, 2014 at 6:16 PM, Bhushan Shah wrote: >> Well, it is big enough so it appears below mouse cursor and hides so, >> hard to get screenshot.. maybe let me try gif.. :P > > So here we go.. http://i.imgur.com/Fw3dW7c.gif Wow. cool

Re: RFC: plasma tooltips animations

On Fri, Apr 18, 2014 at 6:16 PM, Bhushan Shah wrote: > Well, it is big enough so it appears below mouse cursor and hides so, > hard to get screenshot.. maybe let me try gif.. :P So here we go.. http://i.imgur.com/Fw3dW7c.gif -- Bhushan Shah http://bhush9.github.io IRC Nick : bshah on Freenode

Re: Re: Defaults: panel on each screen?

On Fri, Apr 18, 2014 at 2:52 PM, Martin Gräßlin wrote: > > That's a setup I have but I never really considered it as a problem. I have > two screens and the only panel is on the absolute left as a vertical panel. > > If I don't want to move that far I normally use one of the screen edges to > act

Build failed in Jenkins: plasma-workspace_master_qt5 #76

See -- [...truncated 1366 lines...] [ 29%] Building CXX object appmenu/CMakeFiles/kded_appmenu.dir/appmenuadaptor.cpp.o [ 29%]

Build failed in Jenkins: kmenuedit_master_qt5 #2

See -- Started by user Ben Cooksley Building remotely on LinuxSlave - 1 (PACKAGER LINBUILDER) in workspace Running Prebuild steps [kmenuedit_master_qt5] $

Build failed in Jenkins: kde-runtime_frameworks_qt5 #149

See -- [...truncated 168 lines...] * KF5ItemViews * KF5Notifications * KF5IconThemes * KF5Completion * KF5JobWidgets * KF5TextWidgets * KF5XmlGui * KF5Crash * KF5UnitConversion * KF5Bookmar

Build failed in Jenkins: kinfocenter_master_qt5 #13

See -- [...truncated 395 lines...] int numScreens, scrnum; ^ Scanning dependencies of target kinfocenter Scanning dependencies of target kcm_infosummary [ 59%] [ 60%] Building CXX ob

Build failed in Jenkins: khotkeys_master_qt5 #5

See -- Started by user Ben Cooksley Building remotely on LinuxSlave - 4 (PACKAGER LINBUILDER) in workspace Running Prebuild steps [khotkeys_master_qt5] $ /b

Build failed in Jenkins: plasma-desktop_master_qt5 #46

See -- Started by user Ben Cooksley Building remotely on LinuxSlave - 4 (PACKAGER LINBUILDER) in workspace Running Prebuild steps [plasma-deskt

Re: Re: Defaults: panel on each screen?

On Friday 18 April 2014 14:24:35 Martin Klapetek wrote: > On Fri, Apr 18, 2014 at 2:09 PM, Martin Gräßlin wrote: > > On Friday 18 April 2014 13:52:20 Martin Klapetek wrote: > > > Hey, > > > > > > if there's no plasma config existing, plasma is run for the first time > > > > in a > > > > > multi

Re: RFC: plasma tooltips animations

On Fri, Apr 18, 2014 at 6:14 PM, Marco Martin wrote: > screenshot o didn't happen :p Well, it is big enough so it appears below mouse cursor and hides so, hard to get screenshot.. maybe let me try gif.. :P -- Bhushan Shah http://bhush9.github.io IRC Nick : bshah on Freenode ___

Re: RFC: plasma tooltips animations

On Friday 18 April 2014, Bhushan Shah wrote: > So now tooltips does not dance now.. :) but, > > I have *big* tooltips in Folderview, not sure if that's from plasma > side or folderview side.. > > Thank you.. :) screenshot o didn't happen :p (hard to figure out the problem otherwise) -- Marco

Re: RFC: plasma tooltips animations

Hello, On Thu, Apr 17, 2014 at 11:39 PM, Marco Martin wrote: > Ok, ask to test part 2: > now the tooltip in master (based on Dialog) should behave way better. > shouldn't dance anymore, should appear always in the proper position, in > general behave better So now tooltips does not dance now.. :

Re: Defaults: panel on each screen?

On Friday 18 April 2014, Martin Klapetek wrote: > Worth considering imho. Maybe just a panel with taskbar and clock? we can try to test to add a limited panel. inthat case i think it should use desktop scripting -- Marco Martin ___ Plasma-devel mailing

Re: Defaults: panel on each screen?

On Fri, Apr 18, 2014 at 2:09 PM, Martin Gräßlin wrote: > On Friday 18 April 2014 13:52:20 Martin Klapetek wrote: > > Hey, > > > > if there's no plasma config existing, plasma is run for the first time > in a > > multi-screen env, should plasma create a (default) panel on each screen? > > thinking

Re: Defaults: panel on each screen?

On Fri, Apr 18, 2014 at 2:16 PM, Marco Martin wrote: > On Friday 18 April 2014, Martin Gräßlin wrote: > > > On the other hand having two screens and only a panel on one might seem > > unpolished. Do we really need all of what is in the panel on both > screens? > > I think it's the exact opposite

Re: Defaults: panel on each screen?

On Friday 18 April 2014, Martin Gräßlin wrote: > On the other hand having two screens and only a panel on one might seem > unpolished. Do we really need all of what is in the panel on both screens? I think it's the exact opposite -- Marco Martin ___ P

Re: Defaults: panel on each screen?

On Friday 18 April 2014 13:52:20 Martin Klapetek wrote: > Hey, > > if there's no plasma config existing, plasma is run for the first time in a > multi-screen env, should plasma create a (default) panel on each screen? thinking out load: if plasma is without config and started in a multi-screen e

Re: Defaults: panel on each screen?

On Friday 18 April 2014, Martin Klapetek wrote: > Hey, > > if there's no plasma config existing, plasma is run for the first time in a > multi-screen env, should plasma create a (default) panel on each screen? no, i don't think so. I think we should pursue the default of "as clean as possible" an

Defaults: panel on each screen?

Hey, if there's no plasma config existing, plasma is run for the first time in a multi-screen env, should plasma create a (default) panel on each screen? Cheers -- Martin Klapetek | KDE Developer ___ Plasma-devel mailing list Plasma-devel@kde.org https

Re: An alternative for XEmbed

On Tue, Apr 15, 2014 at 11:10 PM, Marco Martin wrote: > On Tuesday 15 April 2014 18:27:08 Martin Klapetek wrote: > > On Tue, Apr 15, 2014 at 6:14 PM, Àlex Fiestas wrote: > > > Another thing to take into account is that there are patches for > gtk2/3 + > > > qt4 > > > to use statusnotifier (by Ub

Re: Review Request 117606: Make sure that the panel is not hidden when a plasmoid is expanded

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117606/#review56019 --- src/plasmaquick/appletquickitem.cpp

Re: Re: Please try to disable threaded rendering in KWin

On Friday 18 April 2014 11:45:23 Marco Martin wrote: > On Friday 18 April 2014, Martin Gräßlin wrote: > > Hi all, > > > > those who experience problems with KWin/5 (looking at e.g. Vishesh, Aleix, > > Alex) please give a try to run KWin with: > > > > QSG_RENDER_LOOP=basic > > > > This disables t

Re: Please try to disable threaded rendering in KWin

On Friday 18 April 2014, Martin Gräßlin wrote: > Hi all, > > those who experience problems with KWin/5 (looking at e.g. Vishesh, Aleix, > Alex) please give a try to run KWin with: > > QSG_RENDER_LOOP=basic > > This disables the threaded rendering in QtQuick. I'm currently using it and > my exper

Please try to disable threaded rendering in KWin

Hi all, those who experience problems with KWin/5 (looking at e.g. Vishesh, Aleix, Alex) please give a try to run KWin with: QSG_RENDER_LOOP=basic This disables the threaded rendering in QtQuick. I'm currently using it and my experience so far is that the quality is massively improved. I got t

Re: RFC: plasma tooltips animations

On Thursday 17 April 2014, Martin Klapetek wrote: > How do you tell it's a driver caused crash? With nvidia 331.x and 334.x I > never had any crash of plasma directly pointing to drivers, had only some > in QSGRender thing or similar, not sure how much the driver is relevant > there. Haven't seen

Re: Proposal to hide raw QML errors in Plasma Next

On Friday 18 of April 2014 10:04:02 Bhushan Shah wrote: > This is case, but still you are missing two stuffs.. > > 1) We still have some qDebug and kDebug kDebug doesn't count because it is deprecated code which should be replaced. qDebug is using "default" as its category. default = false wil

Review Request 117625: Remove unused dependencies

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117625/ --- Review request for Plasma. Repository: kmenuedit Description --- R

Re: Review Request 117404: Don't build tests if QtTest is not found

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117404/#review56011 --- This review has been submitted with commit 5fb488cb19d22f342a

Re: Review Request 117404: Don't build tests if QtTest is not found

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117404/ --- (Updated April 18, 2014, 8:20 a.m.) Status -- This change has been m

Re: Review Request 117404: Don't build tests if QtTest is not found

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117404/#review56010 --- Ship it! Ship It! - Martin Gräßlin On April 18, 2014, 10:0

Re: Review Request 117404: Don't build tests if QtTest is not found

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117404/ --- (Updated April 18, 2014, 8:04 a.m.) Review request for Plasma. Changes