Lars Gullik Bjønnes wrote:
> | On the other hand, having Qt and XForms behave as similarly as
> | possible will save us heartache later on. If this is small, I'd
> | say: go for it and finish the job.
>
> To have Qt and XForms and behave similarly is not a requirement.
But does make it easier to
On Wednesday 05 May 2004 4:07 pm, Martin Vermeer wrote:
> On Tue, May 04, 2004 at 05:48:12PM +0100, Angus Leeming spake
thusly:
> > Lars Gullik Bjønnes wrote:
> > > | Maybe we should do as John has done in the Qt frontend
> > > | already and have separate widgets to display messages and to
> > > |
Martin Vermeer <[EMAIL PROTECTED]> writes:
| On Tue, May 04, 2004 at 05:48:12PM +0100, Angus Leeming spake thusly:
|
>> Lars Gullik Bjønnes wrote:
>> > | Maybe we should do as John has done in the Qt frontend already and
>> > | have separate widgets to display messages and to input commands?
>>
On Tue, May 04, 2004 at 05:48:12PM +0100, Angus Leeming spake thusly:
> Lars Gullik Bjønnes wrote:
> > | Maybe we should do as John has done in the Qt frontend already and
> > | have separate widgets to display messages and to input commands?
> >
> > I'd like that.
> >
> > OTOH it is time to fr
On Wed, May 05, 2004 at 08:23:08AM +0200, Andre Poenitz wrote:
> > On Tue, May 04, 2004 at 09:07:37PM +0200, Andre Poenitz wrote:
> >
> > > > Maybe we should do as John has done in the Qt frontend already and
> > > > have separate widgets to display messages and to input commands?
> > >
> > > Bt
On Wednesday 05 May 2004 7:23 am, Andre Poenitz wrote:
> Isn't there the minibuffer to type in andd the status bar the same
> kind of thing? Once we press M-x it's a text entry, otherwise a
> static label...
You're probably right. However, nothiing is going to change in this
area before lyx 1.5 d
On Wednesday 05 May 2004 7:29 am, Andre Poenitz wrote:
> On Tue, May 04, 2004 at 08:38:36PM +0100, Angus Leeming wrote:
> > Have you tried the Qt frontend, Andre?
>
> Not lately. I just checked that it compiled (it did - in almost
> exactly two hours on a PII 333)
I know the feeling. I have an old
On Tue, May 04, 2004 at 08:38:36PM +0100, Angus Leeming wrote:
> Have you tried the Qt frontend, Andre?
Not lately. I just checked that it compiled (it did - in almost exactly
two hours on a PII 333)
Andre'
On Tue, May 04, 2004 at 08:37:57PM +0100, John Levon wrote:
> On Tue, May 04, 2004 at 09:07:37PM +0200, Andre Poenitz wrote:
>
> > > Maybe we should do as John has done in the Qt frontend already and
> > > have separate widgets to display messages and to input commands?
> >
> > Btw, I discovered
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
wasn't that "status" in wone widget, and input and info in another
widget?
>>>
>> | Sorry, I don't follow you. I thought that the idea was for a
>> | widget to show feedback on and for a widget to input commands in.
>
Angus Leeming wrote:
> So (screenshot attached) you picture is that
Hmmmpf.
--
Angus<>
Lars Gullik Bjønnes wrote:
>>> wasn't that "status" in wone widget, and input and info in another
>>> widget?
>>
> | Sorry, I don't follow you. I thought that the idea was for a
> | widget to show feedback on and for a widget to input commands in.
>>
> | What's your vision?
>
> Two visible widgets
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>
>> Angus Leeming <[EMAIL PROTECTED]> writes:
>>
>> | My take on this: QWidgetStack is the way to go if we want to
>> | emulate emacs' minibuffer. Ie, a single 'apparent' widget that
>> | both displays messages and receives i
Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | My take on this: QWidgetStack is the way to go if we want to
> | emulate emacs' minibuffer. Ie, a single 'apparent' widget that
> | both displays messages and receives input. However, John has
> | argued that these requi
Angus Leeming <[EMAIL PROTECTED]> writes:
| My take on this: QWidgetStack is the way to go if we want to emulate
| emacs' minibuffer. Ie, a single 'apparent' widget that both displays
| messages and receives input. However, John has argued that these
| requirements are best served by two, separ
On Tuesday 04 May 2004 8:07 pm, Andre Poenitz wrote:
> On Tue, May 04, 2004 at 04:15:49PM +0100, Angus Leeming wrote:
> > Maybe we should do as John has done in the Qt frontend already
> > and have separate widgets to display messages and to input
> > commands?
>
> Btw, I discovered today that ther
On Tue, May 04, 2004 at 09:07:37PM +0200, Andre Poenitz wrote:
> > Maybe we should do as John has done in the Qt frontend already and
> > have separate widgets to display messages and to input commands?
>
> Btw, I discovered today that there's a Qt "WidgetStack" (or similar)
> Why don't we use th
On Tue, May 04, 2004 at 04:15:49PM +0100, Angus Leeming wrote:
> Maybe we should do as John has done in the Qt frontend already and
> have separate widgets to display messages and to input commands?
Btw, I discovered today that there's a Qt "WidgetStack" (or similar)
Why don't we use this for mini
Lars Gullik Bjønnes wrote:
> | Maybe we should do as John has done in the Qt frontend already and
> | have separate widgets to display messages and to input commands?
>
> I'd like that.
>
> OTOH it is time to freeze up...
Agreed. It turned out that fixing the XForms layout engine code to not
res
On Tue, May 04, 2004 at 04:01:02PM +0100, Angus Leeming wrote:
> But, you cannot set this breakpoint when the binary is not
> running already. GDB is unable to detect the shared libraries
> which the program depends on. So I do a 'break main' first,
> run the program and set the real breakpoint a
Angus Leeming <[EMAIL PROTECTED]> writes:
| Maybe we should do as John has done in the Qt frontend already and
| have separate widgets to display messages and to input commands?
I'd like that.
OTOH it is time to freeze up...
--
Lgb
Angus Leeming wrote:
> Hm. I've discovered that a single press of a cursor key leads
> to:
>
> expose 633x752+0+0
> paint 633x752+0+0
> work_area_handler, received X11 expose event 633x752+37+67
> paint 633x752+0+0
>
> XScreen::expose posts an XEvent that is received by the second call
> to
On Tuesday 04 May 2004 4:15 pm, John Levon wrote:
> On Tue, May 04, 2004 at 04:01:02PM +0100, Angus Leeming wrote:
> > But, you cannot set this breakpoint when the binary is not
> > running already. GDB is unable to detect the shared libraries
> > which the program depends on. So I do a 'break main
John Levon wrote:
> On Tue, May 04, 2004 at 03:13:03PM +0100, Angus Leeming wrote:
>
>> I've tracked down the first call to paint which is from
>> fl_unfreeze_form. I have not been able to ascertain what is calling
>> fl_unfreeze_form. Any ideas on how I might? Put that another way.
>> How do I t
On Tue, May 04, 2004 at 03:13:03PM +0100, Angus Leeming wrote:
> I've tracked down the first call to paint which is from
> fl_unfreeze_form. I have not been able to ascertain what is calling
> fl_unfreeze_form. Any ideas on how I might? Put that another way. How
> do I tell gdb to stop execution i
Hm. I've discovered that a single press of a cursor key leads to:
expose 633x752+0+0
paint 633x752+0+0
work_area_handler, recevied X11 expose event 633x752+37+67
paint 633x752+0+0
XScreen::expose posts an XEvent that is received by the second call to
XWorkArea::paint. It's able, therefore, to
26 matches
Mail list logo
