Alfredo Braunstein wrote:
> Angus Leeming wrote:
>
>>> I'm not promising anything. But I will revert the change here and
>>> see if that makes a difference. Once LyX has finished compiling
>>> after Jean-Marc's regeneration of config.h that is.
>>
>> The attached patch cures the problem for me.
Angus Leeming wrote:
>> I'm not promising anything. But I will revert the change here and
>> see if that makes a difference. Once LyX has finished compiling
>> after Jean-Marc's regeneration of config.h that is.
>
> The attached patch cures the problem for me. Maybe you could confirm
> that it wo
Angus Leeming wrote:
>>> Hi, Alfredo. This is very peculiar. I too see the behaviour you
>>> describe with the HEAD version of xforms-lyx. However, the 1.3.x
>>> version behaves perfectly. I'd guess that the "'intelligent'
>>> painting
>>
>> Exactly, this is very strange. I've had a fast look at r
Alfredo Braunstein wrote:
> Angus Leeming wrote:
>
>> Hi, Alfredo. This is very peculiar. I too see the behaviour you
>> describe with the HEAD version of xforms-lyx. However, the 1.3.x
>> version behaves perfectly. I'd guess that the "'intelligent'
>> painting
>
> Exactly, this is very strange.
Angus Leeming wrote:
> Hi, Alfredo. This is very peculiar. I too see the behaviour you
> describe with the HEAD version of xforms-lyx. However, the 1.3.x
> version behaves perfectly. I'd guess that the "'intelligent' painting
Exactly, this is very strange. I've had a fast look at recent changes i
Alfredo Braunstein wrote:
> Angus Leeming wrote:
>
>>> I hope you could have a look into this.
>>
>> What version of the XForms library are you using?
>
> xforms-1.0
>
> IIRC, I'm not the only one having this problem.
>
> Regards, Alfredo
Hi, Alfredo. This is very peculiar. I too see the be
Angus Leeming wrote:
>> I hope you could have a look into this.
>
> What version of the XForms library are you using?
xforms-1.0
IIRC, I'm not the only one having this problem.
Regards, Alfredo
Alfredo Braunstein wrote:
> Angus, any idea on why XWorkArea sees after (almost) any PUSH event an
> inexistent RELEASE event with
>
> ev->xbutton.x=377
> ev->xbutton.y=0
> ob->x=3
> ob->y=103
>
> ev->xbutton seems to be unrelated with the workarea (it doesn't have the
> right offset -- from th
Angus, any idea on why XWorkArea sees after (almost) any PUSH event an
inexistent RELEASE event with
ev->xbutton.x=377
ev->xbutton.y=0
ob->x=3
ob->y=103
ev->xbutton seems to be unrelated with the workarea (it doesn't have the
right offset -- from the position it seems to be somewhere in the men
