MMCall objects from CallAdded signal

[Aleksander Morgado]

Hey,

>>> This means that the CallAdded D-Bus signal is emitted immediately while
>>> the PropertiesChanged D-Bus signal is emitted some time later, whenever
>>> the main loop becomes idle.  As a consequence, the MMModemVoice's
>>> "call-added" GObject signal is emitted before the MMModemVoice's call
>>> list contains the relevant MMCall object.
>>>
>>
>> That should be easily fixed with a g_dbus_object_skeleton_flush() to
>> force the emission of the PropertiesChanged right away, after adding
>> the call object to the list and even before emitting the CallAdded
>> signal.
>
> Ah, even better, thanks! :-)
>

Tracking this as
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/81


-- 
Aleksander
https://aleksander.es