Dear Qt 3/Win Free developers,
first of all thank you very much for fixing the font metrics bug that
increased the usability of "LyX/Qt3/Win Free" significantly!
However, I have identified another problem with your Qt port that is
related to drawing dotted lines.
For drawing table cell boundar
Hello LyXers,
LyXWin uses the LaTeX-XFT fonts in TrueType (ttf) format to render math
constructs. But these fonts are not correctly scaleable, e.g. the equal
sign "=" disappears when using different zooms for the screen font.
Ekkehart Schlicht (schlicht-at-lmu.de) send me now a modified cmr10
fo
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
>> Thanks for the fix in validate. Should I do the same in 1.3.x?
Andre> Yes, please.
OK.
Andre> Well, not requiring ams in these cases creates an interesting
Andre> situation: What version is used depends on whether other places
Andr
I attach two (small) screen shots of LyX when it starts up under both linux
and windows. The windows version uses the Qt Free/Win32 port. Apart from
the rather obvious mess of the splash screen, notice also that the windows
version doesn't display the deactivated icons.
--
Angus<><>
Andreas Vox wrote:
>> Andreas,
>> perhaps you'd try out the attached patch
> Thanx, that works.
Then I'll commit it.
Angus
--
Angus
Good evening, Ruurd.
I wonder if you could help out a Windows novice --- me?
My question concerns the way that Windows treats LyX --- as
a Windows GUI app or as a console one. At the moment, Windows
believes that LyX is a console app because it has a "main"
function rather than a "WinMain".
You'v
Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Andreas,
>
> perhaps you'd try out the attached patch
...
Thanx, that works.
>
> The patch should apply to a clean CVS head. You'll still need to set
> path_prefix manually, just as you've done previously.
It was still set from the last try :-)
Michael Schmitt wrote:
There is really no defskip. I have
the choice between Small-, Med-, Bigskip, and Length.
Right. And whatever you choose in the document setting dialog becomes
"defskip". I.e. either smallskip, medskip or bigskip becomes the default
skip for the entire document.
Thanks for
Juergen Spitzmueller wrote:
>> The table dialogue window has no possibility anymore to add/delete
>> lines/columns. Is this a mistake or a feature?
>
> I think the one who removed it (John?) did it intentionally, since there
> is the tabular tollbar now. But I'm not sure.
Hmmm. But that can be tu
On Thu, Jan 13, 2005 at 03:34:24AM +0100, Uwe StÃhr wrote:
> >...because manuals should be as dry as dust, and so boring that nobody
> >looks at them?
>
> Yes of course ;-) I mean commands like "If you use Export->PostScript
> you can start drinking a coffee" (translated from the german docs). If
Jean-Marc,
we decided recently that if LyX failed to create a temp directory then it
should inform the user and exit. Looking at the code, I see that's exactly
what the 1.4.x code base does. The 1.3.x code, however, is a little
different because of the existence of the LyXRC::use_temp_dir boolean.
Hartmut Haase wrote:
> The table dialogue window has no possibility anymore to add/delete
> lines/columns. Is this a mistake or a feature?
I think the one who removed it (John?) did it intentionally, since there is
the tabular tollbar now. But I'm not sure.
Jürgen
BTW: It would be nice if you'd
The table dialogue window has no possibility anymore to add/delete
lines/columns. Is this a mistake or a feature?
--
Hartmut
Hungerhilfe: http://www.thehungersite.com
Das heutige Motto:
With clothes the new are best, with friends the old are best.
Andreas Vox wrote:
> If configure doesn't find some essential binaries, I would like that a
> warning pops up which tells the user to amend the path in
> Preferences->Paths.
>
> This procedure would be applicable to all platforms, only the "usual
> suspects" paths for configure would differ.
>
>
Angus Leeming <[EMAIL PROTECTED]> writes:
>
> So, this PATH consists of the default PATH that is given to LyX when the
> binary is launched via LaunchServices, prepended with the path to the LyX
> executable which we add ourselves, right?
Yes.
>
...
> > But it still gives the same "env PATH ="
Andreas,
perhaps you'd try out the attached patch which attempts to resolve
your problems with my stripping out of the hard coded additions to
the PATH environment variable for MacOSX, replacing it with a
LyXRC::path_prefix variable.
This attempt runs /configure after the various lyxrc
files
Andreas Vox wrote:
> Bad news again:
Why's this bad news? All information is good.
> 2005-01-16 02:41:17.640 SystemUIServer[274] app path =
> /Applications/LyX.app
> /Applications/LyX.app/Contents/MacOS/LyX
>
> env PATH =
> /Applications/LyX.app/Contents/MacOS/:/usr/bin:/bin:/usr/sbin:/sbin:/
>
17 matches
Mail list logo
