Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> I am doing the GuiApplication part.
Good.
JMarc
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
On second thinking it should be fine. Only those LFUNs handled by
GuiView should be affected so I think this is OK.
Ack from me.
Actually, I wanted to it now to avoid that new code like that appear
in LyXFunc.
Pavel Sanda <[EMAIL PROTECTED]> writes:
> Jean-Marc Lasgouttes wrote:
>> Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>>
>> > On second thinking it should be fine. Only those LFUNs handled by
>> > GuiView should be affected so I think this is OK.
>> >
>> > Ack from me.
>>
>> Actually, I wanted
Jean-Marc Lasgouttes wrote:
> Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>
> > On second thinking it should be fine. Only those LFUNs handled by
> > GuiView should be affected so I think this is OK.
> >
> > Ack from me.
>
> Actually, I wanted to it now to avoid that new code like that appear
>
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> On second thinking it should be fine. Only those LFUNs handled by
> GuiView should be affected so I think this is OK.
>
> Ack from me.
Actually, I wanted to it now to avoid that new code like that appear
in LyXFunc.
Thanks. Applied.
JMarc
Jean-Marc Lasgouttes wrote:
While investigating bug 4607 (that Abdel solved in the meantime), I
came up with this patch to handle LyXView::getStatus.
I post it here to insist on how things are supposed to work.
LyXView::getStatus has been changed to return true if it has something
to say, and fa
While investigating bug 4607 (that Abdel solved in the meantime), I
came up with this patch to handle LyXView::getStatus.
I post it here to insist on how things are supposed to work.
LyXView::getStatus has been changed to return true if it has something
to say, and false otherwise. This is how di
