On Tue, 2005-02-15 at 14:29, Angus Leeming wrote:
> Edwin Leuven wrote:
> > i just don't really understand why selections are so complicated compared
> > to copy and cut's. why not send a signal (with a string) to the frontend
> > on selection. the frontend can then push it to the selection buffer
Edwin Leuven wrote:
> i just don't really understand why selections are so complicated compared
> to copy and cut's. why not send a signal (with a string) to the frontend
> on selection. the frontend can then push it to the selection buffer (if
> it exists). and if a copy or cut follows put the str
Angus Leeming wrote:
I agree that LyX's interaction with klipper is a PITA. Can you explain the
implications of the changes below? What changes, other than klipper being
happy?
hi angus,
it's really all trial and error (little kid groping in the dark).
as you've noticed i even missed the other wa_p
Edwin Leuven wrote:
> PS i was finally too annoyed by lyx's clipboard behavior (klipper in kde
> was hanging etc...) so i removed the line above, made the changes below,
> and life has been better since...
I agree that LyX's interaction with klipper is a PITA. Can you explain the
implications of t
On Sun, Feb 13, 2005 at 08:30:57PM +, Angus Leeming wrote:
> > xev->{xselectionrequest|xselectionclear}.window
>
> ... and if a Window has two QWorkAreas?
Then we've mis-designed multiple buffer support.
john
John Levon wrote:
> On Sun, Feb 13, 2005 at 05:42:39PM +, Angus Leeming wrote:
>
>> > But each one should be a spearate QWidget, right?
>>
>> I don't see how that helps us given that lyxX11EventFilter is passed
>> only a XEvent * and must use that to distinguish the QWorkArea from
>> which t
On Sun, Feb 13, 2005 at 05:42:39PM +, Angus Leeming wrote:
> > But each one should be a spearate QWidget, right?
>
> I don't see how that helps us given that lyxX11EventFilter is passed only a
> XEvent * and must use that to distinguish the QWorkArea from which the
> event originated.
xev->{
John Levon wrote:
> On Sun, Feb 13, 2005 at 04:36:32PM +, Angus Leeming wrote:
>
>> Me too, given that eventually a LyXView will be able to hold multiple
>> QWorkAreas.
>
> But each one should be a spearate QWidget, right?
I don't see how that helps us given that lyxX11EventFilter is passed
On Sun, Feb 13, 2005 at 04:36:32PM +, Angus Leeming wrote:
> Me too, given that eventually a LyXView will be able to hold multiple
> QWorkAreas.
But each one should be a spearate QWidget, right?
> What would be the 'proper' way of doing this X11-selection
> stuff in a Qt-ish way?
Dunno. Whe
John Levon wrote:
> On Sun, Feb 13, 2005 at 02:33:19PM +, Angus Leeming wrote:
>
>> What about something that maps between an X11 window ID and a QWorkArea?
>> F.ex below. Of course, that requires a way to find the X11 window ID
>> associated with a particular QWorkArea and I've no idea if th
On Sun, Feb 13, 2005 at 02:33:19PM +, Angus Leeming wrote:
> What about something that maps between an X11 window ID and a QWorkArea?
> F.ex below. Of course, that requires a way to find the X11 window ID
> associated with a particular QWorkArea and I've no idea if that is
> possible...
There
John Levon wrote:
> On Sun, Feb 13, 2005 at 12:43:22PM +, Angus Leeming wrote:
>
>> Pretty dumm ;-) At a quick look, it looks to me like wa_ptr (work area
>> pointer?) is a hack. Also at a quick look, it means that QWorkArea is
>
> Right, it's a horrible hack because we don't have access to
On Sun, Feb 13, 2005 at 12:43:22PM +, Angus Leeming wrote:
> Pretty dumm ;-) At a quick look, it looks to me like wa_ptr (work area
> pointer?) is a hack. Also at a quick look, it means that QWorkArea is
Right, it's a horrible hack because we don't have access to a work-area
in the context we
Edwin Leuven wrote:
> Edwin Leuven wrote:
>> can anyone explain to me what this line:
>>
>> wa_ptr = this;
>>
>> in "void QWorkArea::haveSelection(bool)"
>>
>> does?
>
> stupid question?
Pretty dumm ;-) At a quick look, it looks to me like wa_ptr (work area
pointer?) is a hack. Also at a quic
Edwin Leuven wrote:
can anyone explain to me what this line:
wa_ptr = this;
in "void QWorkArea::haveSelection(bool)"
does?
stupid question?
15 matches
Mail list logo
