---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/127462/#review94057
---
Much better! I don't think this should handle XDG*
> On March 27, 2016, 10:03 a.m., David Faure wrote:
> > Given how the socket API works, you should only call error() after a call
> > that returns false (e.g. waitForConnected, etc.). As you found out, calling
> > error() at random points in time doesn't give useful information, you get
> >
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/127488/
---
(Updated March 27, 2016, 6:21 p.m.)
Review request for KDE Frameworks.
> On March 27, 2016, 10:03 a.m., David Faure wrote:
> > Given how the socket API works, you should only call error() after a call
> > that returns false (e.g. waitForConnected, etc.). As you found out, calling
> > error() at random points in time doesn't give useful information, you get
> >
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/127462/
---
(Updated März 27, 2016, 2:22 nachm.)
Review request for KDE Frameworks
> On March 27, 2016, 10:03 a.m., David Faure wrote:
> > Given how the socket API works, you should only call error() after a call
> > that returns false (e.g. waitForConnected, etc.). As you found out, calling
> > error() at random points in time doesn't give useful information, you get
> >
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/127501/#review94042
---
Given how the socket API works, you should only call error()