This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/113205/ |
On October 11th, 2013, 9:51 p.m. UTC, Sune Vuorela wrote:
We are here making a 'hole' for people to do 'bad things' that wasn't possible in the past. I'm not sure we want that.On October 11th, 2013, 10:06 p.m. UTC, Mark Gaiser wrote:
Interesting. So that mean we simply can't use the new signal/slot syntax because of it? That would seem rather strange to me.. If you do a stat call, or listEntry or <any of the others>... Then you are supposed to connect to the result slot. For listEntry you are supposed to connect to the finished signal. Both of those are defined as: signals: private: AKA. Private signals. I really don't see how you can work around this besides perhaps QSignalMapper, but that would be very odd as well. I'm really curious to see how that "bit of magic" is supposed to work. Do you have some links for me there?
I'm not saying we can't use the new syntax because of it. I'm saying it needs a bit more work, and before a 'stable' version is needed. There is a solution out there. It's applied to QAIM and others.
- Sune
On October 11th, 2013, 5:59 p.m. UTC, Mark Gaiser wrote:
Review request for KDE Frameworks and kdelibs.
By Mark Gaiser.
Updated Oct. 11, 2013, 5:59 p.m.
Repository:
kdelibs
Description
Testing
Diffs
|