> On Jan. 14, 2015, 1:15 p.m., Martin Klapetek wrote: > > Looks good, my knowledge in that area is zarro but I trust your testing.
My hesitation was because I'm working around something that should be fixed in TelepathyQt. the "supportsDTMF" call should work but the list of interfaces doesn't get initialized correctly. - Diane ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/122006/#review74037 ----------------------------------------------------------- On Jan. 11, 2015, 9:32 p.m., Diane Trout wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/122006/ > ----------------------------------------------------------- > > (Updated Jan. 11, 2015, 9:32 p.m.) > > > Review request for Telepathy. > > > Repository: ktp-call-ui > > > Description > ------- > > CallContact::supportsDTMF didn't work for me so try to directly access > to the D-Bus interface pointer. > > > Diffs > ----- > > src/call-window.cpp 6a6e7892288b2143923b488ae3a59da8f3f01268 > src/dtmf-handler.cpp 0c56b7374ca0e79d71f114328a39f63d674f9e5a > > Diff: https://git.reviewboard.kde.org/r/122006/diff/ > > > Testing > ------- > > Called [email protected] and pushed dtmf buttons. for whatever reason the > list of D-Bus Interfaces for the CallContentPtr is always empty. > > This technique worked. > > > Thanks, > > Diane Trout > >
_______________________________________________ KDE-Telepathy mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-telepathy
