https://bugs.kde.org/show_bug.cgi?id=358261
--- Comment #2 from Daniel <daniel...@gmail.com> --- Even using the qApp->processEvents(); as you suggested, the message list was not updated after that. But as you warned me that I am using in a synchronous mode, I changed the way to use, now I am using signal/slots and I connected the signal ModemManager::ModemMessaging::messageAdded in a custom slot and this signal is emitted OK and I can access the recently created message using the messages property (ModemManager::Sms::List messages = messaging->messages()). It means that the list contains the recently added message inside the slot called by the signal. Probably I am misusing the framework MMQt. I based my code in the source code of the example folder. In the truth that example didn't work for me. Running the example the message did not sent. Is the example running for you? If you like I can contribute with the MMQt in order to provide more examples. Thanks in advance. (Sorry for my english, I am from Brazil). -- You are receiving this mail because: You are watching all bug changes.
