On Tue, 22 Aug 2000, Juergen Vigna wrote:
> >
> > You're right. I should have suggested:
> > ./configure --with-cucumber=insets
>
> That's it why didn't you suggest this earlier :)
>
> Seriously, we could add the option, BUT we have to give BBB
> warning at the end of configure
On Tue, 22 Aug 2000, Juergen Vigna wrote:
>
> > 3. Add "UndoAll" to the output of the appropriate states in all the
> >policies.
>
> I didn't really read what this UndoAll is (is there some documentation
> in the Policies file?), I think that I just need that after the first
> change the Re
On Tue, 22 Aug 2000, Allan Rae wrote:
Just for the record I made a slight error in my suggestion.
> Nice idiom, wrong application. Even if someone eventually finds the need
> for variables in the GUIRuntime class then you could use a Pimpl specific
> to the toolkits. Either way we don't need f
> While trying to work out how I could generate Postscript from LyX
> documents directly without actually opening the editor I stumbled across
> the apparently undocumented --export option. Now this would actually do
> the trick except that for some reason the editor is still opened even
> though
Version of lyx : 1.1.5fix1
First bug :
The right scrollbar : When you open a document (rather long) and
select File->Reload, the scrollbar becomes as long as the lyx's window.
Second bug :
The plan button in the toolbar : you cannot access to some parts of
your document which are at the e
While trying to work out how I could generate Postscript from LyX
documents directly without actually opening the editor I stumbled across
the apparently undocumented --export option. Now this would actually do
the trick except that for some reason the editor is still opened even
though it exits
> (gdb) p fd_form_table_options
> $1 = (FD_form_table_options *) 0x0
>
> Could you have a look at this Jürgen?
Well I guess a #ifndef NEW_TABULAR around that call would solve the
situation! Something like:
#ifndef NEW_TABULAR
if (fd_form_table_options->form_table_options->vis
Amir Karger wrote:
>
> On Sun, Aug 20, 2000 at 04:28:40PM -0300, Garst R. Reese wrote:
> > Form the CVS ChangeLog
> > * src/frontends/xforms/ButtonController.h (Ok): renamed from
> > Okay()
> > (setOk): renamed from setOkay()
> > The proper spelling of okay is either okay or OK *n
Hey Lars,
I just looked over your list of TODOs and realized there isn't enough
for you to do, os here:
I'd like to see more support for DocBook, and SGML in general. - not
that I really know what I'm talking about - I like the idea of SGML, it
makes sense. My understanding is that XML is kin
Amir Karger <[EMAIL PROTECTED]> writes:
| On Sun, Aug 20, 2000 at 04:28:40PM -0300, Garst R. Reese wrote:
| > Form the CVS ChangeLog
| > * src/frontends/xforms/ButtonController.h (Ok): renamed from
| > Okay()
| > (setOk): renamed from setOkay()
| > The proper spelling of okay is e
This is a segfault in:
Program received signal SIGSEGV, Segmentation fault.
0x80a7308 in updateAllVisibleBufferRelatedDialogs ()
at ../../src/lyx_gui_misc.C:204
204 if (fd_form_table_options->form_table_options->visible) {
(gdb) info locals
No locals.
(gdb) p fd_form_table_option
Juergen Vigna <[EMAIL PROTECTED]> writes:
| >
| > What you would have at best (with the current implementation rewritten):
| > frontend/GUIRuntime.h
| > frontend/*/GUIRuntime.C
|
| You're probably right! Lars should I change that?
Yes, I can... even if I didn't introduce the pimpl.
On Sun, Aug 20, 2000 at 04:28:40PM -0300, Garst R. Reese wrote:
> Form the CVS ChangeLog
> * src/frontends/xforms/ButtonController.h (Ok): renamed from
> Okay()
> (setOk): renamed from setOkay()
> The proper spelling of okay is either okay or OK *not* Ok. In most fonts
> Ok can be
Hi,
currently, I am writing my PhD - with Lyx, of course!!! When doing so, I
discover some deficiencies from time to time (I am a pretentious user :-))
Ok, one thing that I would like to see in a future release is the possibility
to change the format of texts by the search/replace dialogue. For
Hi,
if I enter CTRL-RETURN in math mode to get an eqnarray, the only way to get rid
of the eqnarray again is to undo the operation. But it is not possible to
remove it later. This is rather annoying.
Another problem concerns boxes: Why is there no support for \fbox{...}. I tried
to add the state
Hi,
when I insert a lyx-code paragraph, it is not possible to remove it again. What
I have to do is change the paragraph layout first. Then the auto-removal of
empty paragraphs works as expected.
Michael
--
==
Michael Schmitt
Hi,
I managed to convert your file to TeX using the wv product from CVS.
It can be found at www.abisource.com and is pretty good especially
for visually formatted docs. I attach the LaTeX output.
LyX imports it (using reLyX) but the file is incorrect, even though
the original LaTeX is correct.
On Thu, 17 Aug 2000, Juergen Vigna wrote:
> - I had a look at Menubar_pimpl.C and have seen the composeUI function in
> which you search for some commands to probably use some standard, GNOME
> menu items for them, but why to you use the command-string and not directly
> the action-int in
> 3. Add "UndoAll" to the output of the appropriate states in all the
>policies.
I didn't really read what this UndoAll is (is there some documentation
in the Policies file?), I think that I just need that after the first
change the Restore button is activated and after pressing resotore, ok
>
> You're right. I should have suggested:
> ./configure --with-cucumber=insets
That's it why didn't you suggest this earlier :)
Seriously, we could add the option, BUT we have to give BBB
warning at the end of configure that the resulting .lyx file "COULD"
be incompatible with a
>
> What you would have at best (with the current implementation rewritten):
> frontend/GUIRuntime.h
> frontend/*/GUIRuntime.C
You're probably right! Lars should I change that?
Jürgen
--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen Vigna
21 matches
Mail list logo
