On March 17, 2014, 8:33 p.m., Thomas Lübking wrote:
src/kwindowsystem_x11.cpp, line 102
https://git.reviewboard.kde.org/r/116787/diff/5/?file=254570#file254570line102
Is this compensated anywhere?
Is it actually an issue (since the constructor should operate in the
GUI
On March 17, 2014, 9:33 p.m., Thomas Lübking wrote:
src/kwindowsystem_x11.cpp, line 102
https://git.reviewboard.kde.org/r/116787/diff/5/?file=254570#file254570line102
Is this compensated anywhere?
Is it actually an issue (since the constructor should operate in the
GUI
On March 17, 2014, 8:33 p.m., Thomas Lübking wrote:
src/kwindowsystem_x11.cpp, line 102
https://git.reviewboard.kde.org/r/116787/diff/5/?file=254570#file254570line102
Is this compensated anywhere?
Is it actually an issue (since the constructor should operate in the
GUI
On March 17, 2014, 9:33 p.m., Thomas Lübking wrote:
src/kwindowsystem_x11.cpp, line 102
https://git.reviewboard.kde.org/r/116787/diff/5/?file=254570#file254570line102
Is this compensated anywhere?
Is it actually an issue (since the constructor should operate in the
GUI
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116787/
---
(Updated March 19, 2014, 3:40 p.m.)
Status
--
This change has been
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116787/
---
(Updated March 17, 2014, 9 a.m.)
Review request for KDE Frameworks, kwin
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116787/
---
(Updated March 17, 2014, 9:04 a.m.)
Review request for KDE Frameworks,
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116787/
---
(Updated March 17, 2014, 9:09 a.m.)
Review request for KDE Frameworks,
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116787/#review52957
---
looks good to me, just a few minor nitpicks. Most is: prefer
On March 13, 2014, 10:31 p.m., Martin Gräßlin wrote:
did you try to make it not use QWidget anymore? There shouldn't be a reason
why it is QWidget.
No; I can try it as a non QWidget ... let's see how that goes.
- Aaron J.
---
On March 13, 2014, 10:31 p.m., Martin Gräßlin wrote:
did you try to make it not use QWidget anymore? There shouldn't be a reason
why it is QWidget.
Aaron J. Seigo wrote:
No; I can try it as a non QWidget ... let's see how that goes.
So, challenges a plenty :)
First, this line in
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116787/
---
(Updated March 14, 2014, 10:36 a.m.)
Review request for KDE Frameworks,
On March 13, 2014, 10:40 p.m., Thomas Lübking wrote:
You'll need a drawable, clients will require XInitThreads if that is
accessed from a different than the GUI thread, but it might be possible to
use an internal Window and move the QObject to the GUI thread on
construction.
On March 13, 2014, 11:40 p.m., Thomas Lübking wrote:
You'll need a drawable, clients will require XInitThreads if that is
accessed from a different than the GUI thread, but it might be possible to
use an internal Window and move the QObject to the GUI thread on
construction.
On March 13, 2014, 10:40 p.m., Thomas Lübking wrote:
You'll need a drawable, clients will require XInitThreads if that is
accessed from a different than the GUI thread, but it might be possible to
use an internal Window and move the QObject to the GUI thread on
construction.
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116787/
---
Review request for KDE Frameworks, kwin and Martin Gräßlin.
Repository:
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116787/#review52915
---
You'll need a drawable, clients will require XInitThreads if
17 matches
Mail list logo
