I missed some with the previous search. I hadn't included files
backup on the server (thinking that as they were on a mounted
partition they had appeared in the locate). So I have the following
additional files:
2.10 5
2.15 48
2.16 22
2.17 4
218 33
220 34
A small n
On Thu, 25 Jul 2002, José Abílio Oliveira Matos wrote:
[...]
> Later I would to have some of those relics that all of you have in the
> attic, all those ancient lyx files, to be able to verify the translation
> process. After all we speaking of history. ;-)
>
> For no reason I would Allan to b
On Sun, Jul 28, 2002 at 02:24:46PM +1000, Amir Michail wrote:
> We are working on a design recovery tool for
> interactive graphical applications.
Hey, cool project. I had much a similar idea to help me learn lyx
internals a while ago, but it was of a much smaller scope, and I
never had time to
Hi,
We are working on a design recovery tool for
interactive graphical applications.
See http://www.cse.unsw.edu.au/~drt
Here are some screenshots of the prototype:
http://www.cse.unsw.edu.au/~amichail/gui1.png
http://www.cse.unsw.edu.au/~drt/screenshot/index.html
We would like to support LyX
On Sat, 27 Jul 2002, John Levon wrote:
> Which xforms version ? Have you tried the versions in OpenSource/
> directory on the xforms ftp site ?
Sorry, this information was missing. I tried xforms 0.89-5 and 1.0RC4.
> Can't we ask xforms somehow ? (we could ask X)
Sure. I think that when the i
On Sat, Jul 27, 2002 at 05:09:49PM -0300, Joao Luis M. Assirati wrote:
> I discovered that the problem is a bug (feature???) in
> xforms: fl_add_input cannot display text higher that its height. So, when
Which xforms version ? Have you tried the versions in OpenSource/
directory on the xforms f
Hello,
On Fri, 26 Jul 2002, Joao Luis M. Assirati wrote:
> When starting the xserver
> with 100 dpi fonts (with option option -dpi 100) the minibuffer doesn't
> show any text (but you can see the cursor moving as you type in).
I discovered that the problem is a bug (feature???) in
xforms: fl_a
Dekel Tsur wrote:
> Selecting "default" placement in the float dialog will generate
> \begin{float}.
[...]
> No. The Extra->Float Placement box will still have an effect, because we
> change the value of \fps@figure
OK. Fine with me.
Since you know better what to do: can you change this, please?
On Sat, Jul 27, 2002 at 12:05:19AM +0200, Juergen Spitzmueller wrote:
>
> But the user has to be able to use a \begin{float} without options in ANY
> case, which he can't currently.
Selecting "default" placement in the float dialog will generate
\begin{float}.
> > That is because the code for
