On Mon, Nov 17, 2014 at 12:19 PM, Martin Klapetek wrote:
> On Sat, Oct 4, 2014 at 1:47 PM, Alex Merry wrote:
>
>> On 2014-10-04 10:08, David Faure wrote:
>>
>>> On Friday 03 October 2014 12:15:09 Alex Merry wrote:
>>>
Note that KDBusService has a known limitation where it just doesn't work
On Sat, Oct 4, 2014 at 1:47 PM, Alex Merry wrote:
> On 2014-10-04 10:08, David Faure wrote:
>
>> On Friday 03 October 2014 12:15:09 Alex Merry wrote:
>>
>>> Note that KDBusService has a known limitation where it just doesn't work
>>> with startup notifications in unique mode - the necessary infor
On 2014-10-04 10:08, David Faure wrote:
On Friday 03 October 2014 12:15:09 Alex Merry wrote:
Note that KDBusService has a known limitation where it just doesn't
work
with startup notifications in unique mode - the necessary information
is
never passed to the main application by the secondary i
On Friday 03 October 2014 12:15:09 Alex Merry wrote:
> Note that KDBusService has a known limitation where it just doesn't work
> with startup notifications in unique mode - the necessary information is
> never passed to the main application by the secondary instance.
I lost track a bit there --
On 2014-09-11 10:46, Christoph Cullmann wrote:
Hi,
for Kate, the startup info doesn't work atm in frameworks.
If you launch dolphin KF5 version and open one file => fine,
second file => dolphin blocks and startup info doesn't happen.
If you look at the logs, you see:
(1975)/(default) KXMessa
Hi,
for Kate, the startup info doesn't work atm in frameworks.
If you launch dolphin KF5 version and open one file => fine,
second file => dolphin blocks and startup info doesn't happen.
If you look at the logs, you see:
(1975)/(default) KXMessages::broadcastMessageX: KXMessages used on non-X1
