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.
>
Dear developers,
It took me a while to set up instant preview on solaris. One problem is
that my grep does not have -E option so
grep -E 'Preview: [ST]' ${LOGFILE} > ${METRICSFILE} ||
{
echo "Failed: grep -E 'Preview: [ST]' ${LOGFILE}"
REQUIRED_VERSION ${LOGFILE}
BAIL_OUT
}
would f
On Tue, May 04, 2004 at 10:40:54PM +0100, Angus Leeming wrote:
> Thanks, John. So what's the recommended strategy to address this?
Manually save and restore the dialog state is the only one I can think
of
john
The attached patch is identical to that just submitted to the 1.4.x
tree. Please add it to you list of patches for 1.3.x, Jean-Marc.
If anyone can see what needs to be done to fix this in the Qt
frontend, then they're a better man than I.
A somewhat baffled,
AngusIndex: src/frontends/xforms/Chang
On Tue, May 04, 2004 at 10:30:37PM +0100, Angus Leeming wrote:
> Can someone clued up in Qt ascertain why interaction with the 'sort',
> 'update' or 'document' widgets invokes QRefDialog::changed_adaptor. I
> can see no reason at all, either in the .ui file or in the
> QRefDialog.C, QRef.C files.
On Tuesday 04 May 2004 10:38 pm, John Levon wrote:
> On Tue, May 04, 2004 at 10:30:37PM +0100, Angus Leeming wrote:
> > Can someone clued up in Qt ascertain why interaction with the
> > 'sort', 'update' or 'document' widgets invokes
> > QRefDialog::changed_adaptor. I can see no reason at all, eithe
Can someone clued up in Qt ascertain why interaction with the 'sort',
'update' or 'document' widgets invokes QRefDialog::changed_adaptor. I
can see no reason at all, either in the .ui file or in the
QRefDialog.C, QRef.C files.
These three buttons should not trigger the activation of the Apply
butt
Angus Leeming wrote:
> So (screenshot attached) you picture is that
Hmmmpf.
--
Angus<>
Bennett Helm wrote:
> The trouble I'm having is that if the LyX.app bundle is moved from
> /Applications (which Mac users normally are used to being able to
> do), accessing the thesaurus from within LyX causes a crash. Any
> suggestions for how to get this to work?
Post a backtrace so that we can
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
I'm trying to get aiksaurus to work with lyx-1.4.0-cvs on the Mac. My
aim is to place the aiksaurus files in the LyX.app bundle so that
LyX/Mac can be easily distributed with aiksaurus support.
I've configured aiksaurus with
"--prefix=/Applications/LyX.app/Contents/Resources" and
"--enable-sta
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 Mon, May 03, 2004 at 06:39:15PM +0200, Jean-Marc Lasgouttes wrote:
>
> For some unknown reason command-sequence is completely fucked up in
> HEAD. The following patch should improve the situation.
Thanks.
Andre'
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
On Tue, May 04, 2004 at 12:55:30PM -0400, Cengiz Gunay wrote:
> 1) Having a concept of LyX log file/window similar to the LaTeX log
>concept.
We already have a "LaTeX errors" dialog box. It could, and should, go
there.
We need to make the following changes:
o) allow our error dialog to have
Cengiz Gunay wrote:
>
> Dear lyx-devel,
>
> I just tried the 1.4.0cvs version, and as a user of LyX since 6
> years, I want to point out some problems I had with it.
>
> The pop-up warning dialog that comes at time of LaTeX generation is
> really counter-productive. Here is my story: I have a d
Dear lyx-devel,
I just tried the 1.4.0cvs version, and as a user of LyX since 6 years, I
want to point out some problems I had with it.
The pop-up warning dialog that comes at time of LaTeX generation is really
counter-productive. Here is my story: I have a document which is composed
of around
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
Ronald Florence wrote:
> The problem with the LyX on OSX (X11) page was a corrupted style.css
> file. Now fixed. You may need to empty your cache to make the page
> show up correctly.
Confirmed as working. Good detective work!
> Sorry to cause so much bother. I should stick to book writing!
The problem with the LyX on OSX (X11) page was a corrupted style.css
file. Now fixed. You may need to empty your cache to make the page
show up correctly.
Sorry to cause so much bother. I should stick to book writing!
--
Ronald Florence ron.18james.com
Angus Leeming <[EMAIL PROTECTED]> writes:
> > The LyX on OSX (X11) Howto is at
> > http://www.18james.com/lyx_on_X11.html .
>
> Hi, Ronald. Hope the book is coming on well.
>
> I note that konqueror renders this page poorly. Attached is a
> screenshot of the left hand edge of the window. Note ho
John Levon wrote:
>> // Question: should XScreen::expose always
>> post // with x, y relative to the top left
>> corner // of the window? The code below
>> would continue
>
> Dunno. If I had to say anyt
On Tue, May 04, 2004 at 01:04:48PM +0100, Angus Leeming wrote:
> // Question: should XScreen::expose always post
> // with x, y relative to the top left corner
> // of the window? The code below would continue
Dunno. If I had
Angus Leeming wrote:
> Jean-Marc Lasgouttes wrote:
>> The xforms patch seems reasonable enough. I do not know about the
>> LyX part. But doing that would be very very nice. In particular, I
>> think that would fix the bug with submenus staying on screen after
>> they are closed.
>
> Try out the p
Jean-Marc Lasgouttes wrote:
> The xforms patch seems reasonable enough. I do not know about the
> LyX part. But doing that would be very very nice. In particular, I
> think that would fix the bug with submenus staying on screen after
> they are closed.
Try out the patches I posted in reply to John
John Levon wrote:
> On Tue, May 04, 2004 at 10:05:24AM +0100, Angus Leeming wrote:
>
>> enabled XWorkArea to use the conventional X11 drawing model. (John,
>> do you have it archived, else I'll have to trawl the archives to
>> dig it out.)
>
> Sorry, long since lost
No worries. I found 'em. Att
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Ronald Florence wrote:
>> The LyX on OSX (X11) Howto is at
>> http://www.18james.com/lyx_on_X11.html .
Angus> Hi, Ronald. Hope the book is coming on well.
Angus> I note that konqueror renders this page poorly. Attached is a
Angus>
On Tue, May 04, 2004 at 10:05:24AM +0100, Angus Leeming wrote:
> enabled XWorkArea to use the conventional X11 drawing model. (John,
> do you have it archived, else I'll have to trawl the archives to dig
> it out.)
Sorry, long since lost
john
Ronald Florence wrote:
> The LyX on OSX (X11) Howto is at
> http://www.18james.com/lyx_on_X11.html .
Hi, Ronald. Hope the book is coming on well.
I note that konqueror renders this page poorly. Attached is a
screenshot of the left hand edge of the window. Note how the section
titles appear to sta
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> Angus> http://www.devel.lyx.org/download/ Jean-Marc, this link (to the
> Angus> LyX on OSX (X11) HOWTO) now goes to lyx_on_aqua.html. I guess
> Angus> that that makes the paragraph redundant.
>
> I removed it.
The LyX on OSX (X11) Howto is at ht
Jean-Marc Lasgouttes wrote:
> Angus> Hm. I find that the .ppm files exist but have zero size.
>
> Where are the ppm supposed to be? I can't find them. What program
> produces them?
In /tmp/lyx_tmpdirXXX/lyx_tmpbufY
They are produced by legacy_lyxpreview2ppm.py which calls latex,
dvip
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Jean-Marc Lasgouttes wrote:
>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>>
Angus> Jean-Marc, could I get you to test once again whether
Angus> previewing now works for you?
>> I get a nice crash now... I append the
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Angus Leeming wrote:
>> I suspect that this flicker is a manifestation of the flawed xforms
>> drawing model that John has complained of in the past. Indeed,
>> between us, we produced a patch, both for XForms and for LyX that
>> en
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> http://www.devel.lyx.org/download/ Jean-Marc, this link (to the
Angus> LyX on OSX (X11) HOWTO) now goes to lyx_on_aqua.html. I guess
Angus> that that makes the paragraph redundant.
I removed it.
JMarc
Angus Leeming wrote:
> I suspect that this flicker is a manifestation of the flawed xforms
> drawing model that John has complained of in the past. Indeed,
> between us, we produced a patch, both for XForms and for LyX that
> enabled XWorkArea to use the conventional X11 drawing model. (John,
> do
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> The link to that page on www.lyx.org/download/ is dead. The
Juergen> new URL seems to be
Juergen> http://wwwserv1.rz.fh-hannover.de/mbau/tim/hentschel/lyx/
I do not know whether somebody changed it. But the kink on LyX p
On Tuesday 04 May 2004 10:08, Angus Leeming wrote:
> >
> > See if the next patch fixes it.
>
> Works for me.
I will apply it, I noted also that is the same pattern that we have in
the previous call for copyfileobj, when copying from a temporary file.
--
José Abílio
LyX and docbook, a
> " " == <[EMAIL PROTECTED]> writes:
> Hello! I'm just in the final stages of making my thesis. So I tried
> to add a margin note at one section title saying I had to rewrite
> parts of it...
> ..but then I got a couple of errors when trying to compile it. The
> first one always is "Pa
> "Albert" == Albert Chin <[EMAIL PROTECTED]> writes:
Albert> You're right. Revised patch below.
Thanks, I applied it.
JMarc
Jose' Matos wrote:
>> It seems that 'new.close()' leaves both 'new' and 'tmp' in a closed
>> state.
>
> No the problem is the previous copyfileobj call, we need to
> "rewind"
> the tmp file to write, after copying from new to tmp the tmp pointer
> is at the end of file. Just like a tape. ;-)
>
Any use of the mouse or of the keyboard produces an annoying flicker
in the XForms frontend as the work area is redrawn. This flicker does
not occur in either the Qt or the Gtk frontend.
Try running lyx under valgrind. It's a great way of slowing things
down sufficiently to see what's going on.
I
On Monday 03 May 2004 21:38, Angus Leeming wrote:
> > Incidentally Angus could you verify that it works for you?
>
> Nope it doesn't. It seems that the problem is here:
>
> 240for file in glob.glob("%s*.ppm" % basename):
> 241tmp = mkstemp()
> 242new = t.open(file, "r")
> 243
Angus Leeming wrote:
> Bug still exists. This is scrlttr, not scrlttr2.
The bug was also present in scrlttr2. But thanks for fixing the other bug.
Regards,
Jürgen.
54 matches
Mail list logo
