I think that INSTALL.Win32 should state that Microsoft is happy to have
msvcp80.dll and msvcr80.dll distributed with the LyX installer. See
attached, which I'd recommend be committed.
--
AngusIndex: INSTALL.Win32
===
---
I really like the little menu that appears when I right-click on the
scrollbar:
Scroll here
---
Top
Bottom
---
Page up
Page down
---
Scroll up
Scroll down
Unfortunately, all but the Top and Bottom entries currently lie about what
they do. Unless one page in your world is
Michael Gerz wrote:
A little warning to all pdflatex users (at least to those using the
latest MikTeX 2.5):
pdflatex prefers PNG files over PDF files
Since LyX outputs graphics file names without file extension _and_
generates PNG files for internal use, pdflatex erroneously picks
Peter Kümmel wrote:
Seriously:
Do you think you-as a main developer of lyx- will
have problems to build Qt 4.x by your own?
(I assume it's a question of your principles
because even I have mangaged to compile Qt4.2
on linux, wasn't it ./configure make? :) )
Or do you only think about the
Michael Gerz wrote:
A little warning to all pdflatex users (at least to those using the
latest MikTeX 2.5):
pdflatex prefers PNG files over PDF files
Since LyX outputs graphics file names without file extension _and_
generates PNG files for internal use, pdflatex erroneously picks
Peter Kümmel wrote:
Seriously:
Do you think you-as a main developer of lyx- will
have problems to build Qt 4.x by your own?
(I assume it's a question of your principles
because even I have mangaged to compile Qt4.2
on linux, wasn't it ./configure & make? :) )
Or do you only think about the
Abdelrazak Younes [EMAIL PROTECTED] writes:
By default, when a float is created, the paragraph style is justified
whereas it should be centred. This is pretty annoying as the inserted
table or figure will be justified to the left.
I believe we do as LaTeX does, which is surely a better
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> By default, when a float is created, the paragraph style is justified
> whereas it should be centred. This is pretty annoying as the inserted
> table or figure will be justified to the left.
I believe we do as LaTeX does, which is surely a better
Bennett Helm [EMAIL PROTECTED] writes:
There is a pending patch which was said to crash OS X. I am still
waiting for feedback from Bennett, but I fell we can live without
this fix for now.
Sorry -- it slipped my mind.
I've tested it with both .bst and .bib files in a path with
Bernhard Roider [EMAIL PROTECTED] writes:
i agree to license my contributions to LyX under the GPL version 2 or later.
Thank you and welcome aboard!
Angus
Andreas Vox [EMAIL PROTECTED] writes:
Now, when I try to run it from the commandline it crashes with this
error:
You need to add a lyxerr call to get_binary_path to output what your file name
is.
Angus
Bennett Helm <[EMAIL PROTECTED]> writes:
> > There is a pending patch which was said to crash OS X. I am still
> > waiting for feedback from Bennett, but I fell we can live without
> > this fix for now.
>
> Sorry -- it slipped my mind.
>
> I've tested it with both .bst and .bib files in a
Bernhard Roider <[EMAIL PROTECTED]> writes:
> i agree to license my contributions to LyX under the GPL version 2 or later.
Thank you and welcome aboard!
Angus
Andreas Vox <[EMAIL PROTECTED]> writes:
> Now, when I try to run it from the commandline it crashes with this
> error:
You need to add a lyxerr call to get_binary_path to output what your file name
is.
Angus
Bernhard Roider [EMAIL PROTECTED] writes:
Uwe Stöhr already denoted this small bug in his mail from 03
Jan 2007 - but the discussion then was only about the status of
status.15x
After saving a new file or save as.. the filename is not
updated in the tab. This patch fixes this.
Bernhard, I
Bernhard Roider <[EMAIL PROTECTED]> writes:
> Uwe Stöhr already denoted this small bug in his mail from 03
> Jan 2007 - but the discussion then was only about the status of
> status.15x
>
> After saving a new file or "save as.." the filename is not
> updated in the tab. This patch fixes this.
Jean-Marc Lasgouttes wrote:
It may also be (on windows) that the function call we use for fonts
(AddFontResource) is not adapted. Now that we know that win9x is not
supported (it that true?), we could switch to use AddFontResourceEx
that allows to declare private fonts (or we could use a
Bo Peng [EMAIL PROTECTED] writes:
You then need to make sure your restoreState work with all our backend
code for toolbars (addToolbar etc).
I would rather go another way. Namely, figure out
So, what's the disadvantage of doing what Abdel proposes and letting each
frontend deal with what
Bo Peng [EMAIL PROTECTED] writes:
When I have a very wide float table, there is no horizontal scroll bar
to scroll to the end of the table so I have to use tab keys to move
around. Even worse, the legend below the table go beyond the screen
and there is no way to edit that part.
Is there an
Jean-Marc Lasgouttes wrote:
> It may also be (on windows) that the function call we use for fonts
> (AddFontResource) is not adapted. Now that we know that win9x is not
> supported (it that true?), we could switch to use AddFontResourceEx
> that allows to declare private fonts (or we could use a
Bo Peng <[EMAIL PROTECTED]> writes:
> > > You then need to make sure your restoreState work with all our backend
> > > code for toolbars (addToolbar etc).
> I would rather go another way. Namely, figure out
So, what's the disadvantage of doing what Abdel proposes and letting each
frontend deal
Bo Peng <[EMAIL PROTECTED]> writes:
> When I have a very wide float table, there is no horizontal scroll bar
> to scroll to the end of the table so I have to use tab keys to move
> around. Even worse, the legend below the table go beyond the screen
> and there is no way to edit that part.
> Is
Uwe Stöhr [EMAIL PROTECTED] writes:
* The installer sets InstantPreview-graphics a bit larger as this was
often requested by users.
So only windows users have bad eyesight?
I've never understood why the default is 0.9 instead of 1.0 scaling.
Seems to be a relict of the times when
Michael Gerz [EMAIL PROTECTED] writes:
Question of the day:
Why don't we strip leading spaces in DEPM() if there is only one paragraph?
And how many paragraphs do you end up with if you remove spaces from the one
and only paragraph and that paragraph contains only spaces ?
(I know next
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> >* The installer sets InstantPreview-graphics a bit larger as this was
> > often requested by users.
> > So only windows users have bad eyesight?
> I've never understood why the default is 0.9 instead of 1.0 scaling.
> Seems to be a relict of the
Michael Gerz <[EMAIL PROTECTED]> writes:
>
> Question of the day:
>
> Why don't we strip leading spaces in DEPM() if there is only one paragraph?
And how many paragraphs do you end up with if you remove spaces from the one
and only paragraph and that paragraph contains only spaces ?
(I know
Bo Peng [EMAIL PROTECTED] writes:
I just built lyx-15svn-20070124.exe from the current snapshot (r16842)
following instructions in INSTALL.win32. I have uploaded the file to
ftp://ftp.lyx.org/incoming, can anyone move it to an appropriate place
so that I can announce it in the user list? Since
Bo Peng <[EMAIL PROTECTED]> writes:
> I just built lyx-15svn-20070124.exe from the current snapshot (r16842)
> following instructions in INSTALL.win32. I have uploaded the file to
> ftp://ftp.lyx.org/incoming, can anyone move it to an appropriate place
> so that I can announce it in the user list?
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
Angus (The type attribute is currently missing.)
Better now?
You be the judge ;-)
http://jigsaw.w3.org/css-validator/validator?uri=http://www.lyx.org/
Angus
Abdelrazak Younes [EMAIL PROTECTED] writes:
This patch implement this by using exception instead of direct call.
Objection?
Not in principle, no. But all user-derived exceptions should derive from
std::exception. You're opening a can of worms by doing otherwise.
Angus
+ } catch
I have a problem with instant preview of equations (which
I shut off). I find that defined math symbols don't show up.
If I define
\newcommand\Pc{P^c}
and then have an equation
\Pc = P^c
the left-hand side will show up in the preview, but not the
right.
Uwe Stöhr [EMAIL PROTECTED] writes:
a displeased Uwe
p.s. for this email I define: Wednesday = Friday
And so you should. You've performed a sterling service from outside for too
long. I for one think you're ann absolute star.
Angus
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> Angus> (The type attribute is currently missing.)
> Better now?
You be the judge ;-)
http://jigsaw.w3.org/css-validator/validator?uri=http://www.lyx.org/
Angus
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> This patch implement this by using exception instead of direct call.
> Objection?
Not in principle, no. But all user-derived exceptions should derive from
std::exception. You're opening a can of worms by doing otherwise.
Angus
> + } catch
> I have a problem with instant preview of equations (which
> I shut off). I find that defined math symbols don't show up.
>
> If I define
>
> \newcommand\Pc{P^c}
>
> and then have an equation
>
> \Pc = P^c
>
> the left-hand side will show up in the preview, but not
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> a displeased Uwe
> p.s. for this email I define: Wednesday = Friday
And so you should. You've performed a sterling service from outside for too
long. I for one think you're ann absolute star.
Angus
Stephen Buonopane [EMAIL PROTECTED] writes:
1) Open a new file in LyX 1.4.
2) Press the insert graphics button on the toolbar
3) Select a graphics file (anything will do)
4) Press Apply and wait for the preview to appear in the LyX window.
Don't close the graphics window or bring the main
The w3c css validation engine can no longer find the lyx style sheets.
Please adjust the html to something like:
link href=foo.css media=all rel=stylesheet type=text/css /
(The type attribute is currently missing.)
Regards,
Angus
Stephen Buonopane <[EMAIL PROTECTED]> writes:
> 1) Open a new file in LyX 1.4.
> 2) Press the insert graphics button on the toolbar
> 3) Select a graphics file (anything will do)
> 4) Press Apply and wait for the preview to appear in the LyX window.
> Don't close the graphics window or bring the
The w3c css validation engine can no longer find the lyx style sheets.
Please adjust the html to something like:
(The type attribute is currently missing.)
Regards,
Angus
The implications of this fix are marginal. I don't see any
difference in a typical document.
Maybe not. But the translation changes you've made are absolutely
wrong.
- docstring const abst = _(Abstract: );
+ docstring const abst = _(Abstract) + from_ascii(: );
Not all languages will
> The implications of this fix are marginal. I don't see any
> difference in a typical document.
Maybe not. But the translation changes you've made are absolutely
wrong.
> - docstring const abst = _("Abstract: ");
> + docstring const abst = _("Abstract") + from_ascii(": ");
Not all
Peter Kümmel wrote:
Peter Kümmel wrote:
Does any expert have an idea?
The Usual Suspects ;)
(sorry for the breaking-the-rules smiley)
Peter
See frontends/Dialogs.C:
void Dialogs::updateBufferDependent(bool switched) const
211 {
212 std::mapstring,
Enrico Forestieri wrote:
On Fri, Jan 19, 2007 at 05:11:13PM +0100, Jean-Marc Lasgouttes wrote:
I have been maintaining stable branches since LyX 1.1.5. I have to
admit that the fun part of it has vanished. Therefore I would be glad
to find someone to take this role from 1.5.1 onwards (I'll
John McCabe-Dansted wrote:
I cannot compile svn trunk revision 16774 on Fedora Core 4. Below is
the error I get. My config.log is at
http://www.csse.uwa.edu.au/~john/config.log. This appears to be the
result of some qt4 not being installed, but configure does not
complain.
Hi, John. This is
Peter Kümmel wrote:
Peter Kümmel wrote:
Does any expert have an idea?
"The Usual Suspects" ;)
(sorry for the breaking-the-rules smiley)
Peter
See frontends/Dialogs.C:
void Dialogs::updateBufferDependent(bool switched) const
211 {
212 std::map
Enrico Forestieri wrote:
On Fri, Jan 19, 2007 at 05:11:13PM +0100, Jean-Marc Lasgouttes wrote:
I have been maintaining stable branches since LyX 1.1.5. I have to
admit that the fun part of it has vanished. Therefore I would be glad
to find someone to take this role from 1.5.1 onwards (I'll
John McCabe-Dansted wrote:
I cannot compile svn trunk revision 16774 on Fedora Core 4. Below is
the error I get. My config.log is at
http://www.csse.uwa.edu.au/~john/config.log. This appears to be the
result of some qt4 not being installed, but configure does not
complain.
Hi, John. This is
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
Georg PS: You did not answer the question I was most interested in:
Georg How are we supposed to convert the special caron to unicode?
From what I know special caron is for 4 letters: l L d t. I think it
corresponds to crossed-out letters.
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> Georg> PS: You did not answer the question I was most interested in:
> Georg> How are we supposed to convert the special caron to unicode?
>
> From what I know special caron is for 4 letters: l L d t. I think it
> corresponds to crossed-out
Kornel Benko [EMAIL PROTECTED] writes:
It is very fishy here.
If I replace the call with:
string a();
Buffer buffer(a, false);
then it compiles.
On the other hand
string a();
Buffer buffer(a, false);
yields to
CutAndPaste.C:676: error: no matching
Kornel Benko <[EMAIL PROTECTED]> writes:
> It is very fishy here.
> If I replace the call with:
> string a("");
> Buffer buffer(a, false);
> then it compiles.
>
> On the other hand
> string a();
> Buffer buffer(a, false);
> yields to
> CutAndPaste.C:676: error: no
[EMAIL PROTECTED] writes:
On Fri, 12 Jan 2007, Abdelrazak Younes wrote:
[EMAIL PROTECTED] wrote:
I've been meaning to get into the development (source wise) of LyX for a
long time, and maybe now is the time.
As compilation takes quite a while, I need a fast machine for this.
Ronald Florence [EMAIL PROTECTED] writes:
I've been away from this too long to be of much help, but I think the
Mac way of doing this would be to put the users current LyX home
directory in ~/Library/Preferences/LyX.plist...
An alternative that you might consider is to link ~/Library/
Abdelrazak Younes [EMAIL PROTECTED] writes:
Abdelrazak Younes wrote:
Could someone please test this under Linux?
Enrico, if you could test it under Cygwin as well, that would be great.
Take this patch if you want to see some debug outputs. It's working
perfectly here and it's really a
Bennett Helm wrote:
Bennett,
if you define in words just what you want, I can whip up the script
for you.
I thought I did! But let me try to be clearer
Sorry, I thought that Ronald was suggesting an alternative strategy.
The object is first to find where .lyxpipe.in is located. The
<[EMAIL PROTECTED]> writes:
>
> On Fri, 12 Jan 2007, Abdelrazak Younes wrote:
>
> > [EMAIL PROTECTED] wrote:
> >> I've been meaning to get into the development (source wise) of LyX for a
> >> long time, and maybe now is the time.
> >>
> >> As compilation takes quite a while, I need a fast
Ronald Florence <[EMAIL PROTECTED]> writes:
> I've been away from this too long to be of much help, but I think the
> Mac way of doing this would be to put the users current LyX home
> directory in ~/Library/Preferences/LyX.plist...
> An alternative that you might consider is to link
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> Abdelrazak Younes wrote:
> > Could someone please test this under Linux?
> >
> > Enrico, if you could test it under Cygwin as well, that would be great.
>
> Take this patch if you want to see some debug outputs. It's working
> perfectly here and
Bennett Helm wrote:
Bennett,
if you define in words just what you want, I can whip up the script
for you.
I thought I did! But let me try to be clearer
Sorry, I thought that Ronald was suggesting an alternative strategy.
The object is first to find where .lyxpipe.in is located. The
Georg Baum [EMAIL PROTECTED] writes:
I was a little scared by the changes found in development/FORMAT, and
I'm starting to think that it would be easier to parse the generated
TeX directly.
Definitely not. Proper TeX parsing is a nightmare.
That's surely true. But it (TeX) is a stable
Georg Baum <[EMAIL PROTECTED]> writes:
> > I was a little scared by the changes found in development/FORMAT, and
> > I'm starting to think that it would be easier to parse the generated
> > TeX directly.
> Definitely not. Proper TeX parsing is a nightmare.
That's surely true. But it (TeX) is a
Georg Baum [EMAIL PROTECTED] writes:
Am Dienstag, 9. Januar 2007 19:53 schrieb Bo Peng:
I don't think that we need a separate devel wiki.
I do not see an immediate use of devel wiki, but can doxygen generated
source doc be hosted somewhere?
That should definitely be done. The
Georg Baum <[EMAIL PROTECTED]> writes:
>
> Am Dienstag, 9. Januar 2007 19:53 schrieb Bo Peng:
> > > I don't think that we need a separate devel wiki.
> >
> > I do not see an immediate use of devel wiki, but can doxygen generated
> > source doc be hosted somewhere?
>
> That should definitely be
Abdelrazak Younes [EMAIL PROTECTED] writes:
Each sample counts as 0.01 seconds.
% cumulative self self total
time seconds secondscalls ms/call ms/call name
7.41 0.02 0.02 268500 0.00 0.00
lyx::InsetBase::inMathed() const
I don't
Abdelrazak Younes [EMAIL PROTECTED] writes:
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
The scanning of the bibtex files should be independent of the loaded
Buffer. Imagine you have two Buffers using the same bibtex file, the
same scanning will need to be done twice for no reason.
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> > Each sample counts as 0.01 seconds.
> > % cumulative self self total
> > time seconds secondscalls ms/call ms/call name
> > 7.41 0.02 0.02 268500 0.00 0.00
> > lyx::InsetBase::inMathed()
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> Jürgen Spitzmüller wrote:
> > Abdelrazak Younes wrote:
> >> The scanning of the bibtex files should be independent of the loaded
> >> Buffer. Imagine you have two Buffers using the same bibtex file, the
> >> same scanning will need to be done twice
if (sel.empty()) {
- const int old_pos = cur.pos();
cur.insert(new InsetMathHull(hullSimple));
BOOST_ASSERT(old_pos == cur.pos());
cur.nextInset()-edit(cur, true);
old_pos is not unused as can be seen
Enrico Forestieri wrote:
PS: I see that following the current fashion you started
using utf8, but please fix the headers of your mailer as it currently
adds: Content-Type: text/plain; charset=us-ascii such that mutt
mangles your name...
The Content-Type header refers to the body of the mail.
>>> if (sel.empty()) {
>>> - const int old_pos = cur.pos();
>>> cur.insert(new InsetMathHull(hullSimple));
>>> BOOST_ASSERT(old_pos == cur.pos());
>>> cur.nextInset()->edit(cur, true);
>> old_pos is not
Enrico Forestieri wrote:
> PS: I see that following the current fashion you started
> using utf8, but please fix the headers of your mailer as it currently
> adds: Content-Type: text/plain; charset=us-ascii such that mutt
> mangles your name...
The Content-Type header refers to the body of the
Abdelrazak Younes [EMAIL PROTECTED] writes:
Either CMake does it right or maybe it is delegating that stuff to
MSVC... in the first case, then you can maybe borrow some idea from it?
Here is what's written in the Command line section of the project
properties (in one line):
/nologo
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> Either CMake does it right or maybe it is delegating that stuff to
> MSVC... in the first case, then you can maybe borrow some idea from it?
>
> Here is what's written in the "Command line" section of the project
> properties (in one line):
>
>
Uwe Stöhr [EMAIL PROTECTED] writes:
Currently the lyx.exe has no icon when it is built it with
SCons under Win. This is a minor problem but I was often asked
about this the last time.
In the installer I register LyX with an icon but this only has
an effect on the main application. That means
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> Currently the lyx.exe has no icon when it is built it with
> SCons under Win. This is a minor problem but I was often asked
> about this the last time.
> In the installer I register LyX with an icon but this only has
> an effect on the main application. That
Enrico Forestieri wrote:
After the n-th attempt, I succeeded in remaining within gdb after the
crash, so I could see where the crash was occurring (line 339 in insetbox.C)
and thus the fix is obvious.
Well done!
Index: src/support/docstring.C
Bo Peng wrote:
Another related problem is that when the mouse click back, lyx scrolls
back to the paragraph with the text cursor. I am having a look at it.
This one is weird and I have not found the problem.
Symptom:
1. start lyx, open a doc, open another window
2. from window A, click at
Enrico Forestieri wrote:
After the n-th attempt, I succeeded in remaining within gdb after the
crash, so I could see where the crash was occurring (line 339 in insetbox.C)
and thus the fix is obvious.
Well done!
Index: src/support/docstring.C
Bo Peng wrote:
Another related problem is that when the mouse click back, lyx scrolls
back to the paragraph with the text cursor. I am having a look at it.
This one is weird and I have not found the problem.
Symptom:
1. start lyx, open a doc, open another window
2. from window A, click at
Open the User Guide.
Open a new Window. (FileNew Window)
Select text in the second window (not enough to cause a crash...)
Expected: the same text that is highlighted in blue in the second window
should also be highlighted in blue in the first window. At least, that's
how emacs does it and emacs
Open the User Guide.
Open a new window (FileNew Window)
Click on the Table of Contents inset in each window to bring up two TOC
dialogs.
Using the TOC dialog of the 2nd window, click on 1.2 Getting started to
navigate to that part of the document.
Using the TOC dialog of the 1st window, click on
Angus Leeming wrote:
Today's version of LyX 1.5 on a bang uptodate RH4 linux machine.
Repro:
*Open the User Guide.
*Open the TOC dialog by clicking on the TOC inset.
*Navigate to section 4.1 by clicking on the entry in the TOC dialog.
*Set the cursor by clicking in the with preceding
Angus Leeming wrote:
Start LyX
Open the User Guide with HelpUser's Guide
Hightlight text using the left mouse button. Attempting to select more
than the first screenful results in a crash. See attached screen shot.
That's three bugs in 5 minutes. Time to stop playing before I upset you
all
Angus Leeming wrote:
Open the User Guide.
Open a new window (FileNew Window)
Click on the Table of Contents inset in each window to bring up two TOC
dialogs.
Using the TOC dialog of the 2nd window, click on 1.2 Getting started to
navigate to that part of the document.
Using the TOC dialog
Angus Leeming wrote:
Open the User Guide.
Open a new Window. (FileNew Window)
Select text in the second window (not enough to cause a crash...)
Expected: the same text that is highlighted in blue in the second window
should also be highlighted in blue in the first window. At least, that's
Angus Leeming wrote:
Angus Leeming wrote:
Open the User Guide. Click on the footnote inset
by the LyX Team foot
to expand it. The resulting bounding box expands beyond the right hand
border of the screen. See attached screenshot.
Interestingly, cutting 'by the LyX Team
Open the User Guide.
Open a new Window. (File>New Window)
Select text in the second window (not enough to cause a crash...)
Expected: the same text that is highlighted in blue in the second window
should also be highlighted in blue in the first window. At least, that's
how emacs does it and emacs
Open the User Guide.
Open a new window (File>New Window)
Click on the Table of Contents inset in each window to bring up two TOC
dialogs.
Using the TOC dialog of the 2nd window, click on "1.2 Getting started" to
navigate to that part of the document.
Using the TOC dialog of the 1st window, click
Angus Leeming wrote:
> Today's version of LyX 1.5 on a bang uptodate RH4 linux machine.
>
> Repro:
> *Open the User Guide.
> *Open the TOC dialog by clicking on the TOC inset.
> *Navigate to section 4.1 by clicking on the entry in the TOC dialog.
> *Set t
Angus Leeming wrote:
> Start LyX
> Open the User Guide with Help>User's Guide
> Hightlight text using the left mouse button. Attempting to select more
> than the first screenful results in a crash. See attached screen shot.
>
> That's three bugs in 5 minutes. Time to stop p
Angus Leeming wrote:
> Open the User Guide.
> Open a new window (File>New Window)
> Click on the Table of Contents inset in each window to bring up two TOC
> dialogs.
> Using the TOC dialog of the 2nd window, click on "1.2 Getting started" to
> navigate to tha
Angus Leeming wrote:
> Open the User Guide.
> Open a new Window. (File>New Window)
> Select text in the second window (not enough to cause a crash...)
>
> Expected: the same text that is highlighted in blue in the second window
> should also be highlighted in blue in the f
Angus Leeming wrote:
> Angus Leeming wrote:
>
>> Open the User Guide. Click on the footnote inset
>> by the LyX Team
>> to expand it. The resulting bounding box expands beyond the right hand
>> border of the screen. See attached screenshot.
>
> Int
What's the plan with the icons? I see that there's a desire to standardize
their sizes, but what's the preferred size? 22x22 or 20x20? Please don't
pipe in with 16x16 or somesuch. The files in lib/images seem to fall into
three flavours: 20x20, 22x22 and 24x24. Those in lib/images/math are much
What's the plan with the icons? I see that there's a desire to standardize
their sizes, but what's the preferred size? 22x22 or 20x20? Please don't
pipe in with 16x16 or somesuch. The files in lib/images seem to fall into
three flavours: 20x20, 22x22 and 24x24. Those in lib/images/math are much
Today's version of LyX 1.5 on a bang uptodate RH4 linux machine.
Repro:
*Open the User Guide.
*Open the TOC dialog by clicking on the TOC inset.
*Navigate to section 4.1 by clicking on the entry in the TOC dialog.
*Set the cursor by clicking in the with preceding the a+b/c fraction, so
wi|th,
Today's version of LyX 1.5 on a bang uptodate RH4 linux machine.
Repro:
Open the User Guide.
Move the mouse over the foot note inset on the second line:
by the LyX Team [foot]
Expected: the foot text does not move although the button background
changes colour.
Actual: the foot text
Today's version of LyX 1.5 on a bang uptodate RH4 linux machine.
Repro:
*Open the User Guide.
*Open the TOC dialog by clicking on the TOC inset.
*Navigate to section 4.1 by clicking on the entry in the TOC dialog.
*Set the cursor by clicking in the "with" preceding the a+b/c fraction, so
"wi|th",
Today's version of LyX 1.5 on a bang uptodate RH4 linux machine.
Repro:
Open the User Guide.
Move the mouse over the foot note inset on the second line:
by the LyX Team [foot]
Expected: the "foot" text does not move although the button background
changes colour.
Actual: the "foot" text
301 - 400 of 20061 matches
Mail list logo