On Fri, May 12, 2017 at 01:00:00PM +0200, Pavel Grunt wrote:
> It provides information about the remote cursor similar to the signal
> "cursor-set". The benefit over the signal is that the property can be
> queried at any time.
>
> Users of the "cursor-set" signal should migrate to "notify::cursor
Hi,
On Mon, May 22, 2017 at 10:27:38AM +0200, Pavel Grunt wrote:
> On Fri, 2017-05-19 at 15:56 +0200, Victor Toso wrote:
> > Hi,
> >
> > On Fri, May 12, 2017 at 01:00:00PM +0200, Pavel Grunt wrote:
> > > It provides information about the remote cursor similar to the
> > > signal
> > > "cursor-set
On Fri, 2017-05-19 at 15:56 +0200, Victor Toso wrote:
> Hi,
>
> On Fri, May 12, 2017 at 01:00:00PM +0200, Pavel Grunt wrote:
> > It provides information about the remote cursor similar to the
> > signal
> > "cursor-set". The benefit over the signal is that the property can
> > be
> > queried at an
Hi,
On Fri, May 12, 2017 at 01:00:00PM +0200, Pavel Grunt wrote:
> It provides information about the remote cursor similar to the signal
> "cursor-set". The benefit over the signal is that the property can be
> queried at any time.
>
> Users of the "cursor-set" signal should migrate to "notify::cu
It provides information about the remote cursor similar to the signal
"cursor-set". The benefit over the signal is that the property can be
queried at any time.
Users of the "cursor-set" signal should migrate to "notify::cursor".
Related:
https://bugzilla.redhat.com/show_bug.cgi?id=1411380
---
d
