This is the script I've kept mentioning.
It's close to finished but there's a bug in the gtkmmconvert2 script and I
don't know enough perl to fix it. See the note at the top of
partial_conv.sh. I think Karl Nelson has a newer version so I'll try to
get that and send it to the list soon.
The sc
On Sat, 11 Mar 2000, Angus Leeming wrote:
> Ok, read and digested your recent postings. Also had a play
> with fdesign/read the documentation. Also downloaded and
> installed doc++, so that we can document this stuff.
>
> Allan > I don't want to have to repeat all the work I did
> Allan > last t
On Sat, 11 Mar 2000, Angus Leeming wrote:
> // the print form
> fl_set_input(fd_form_print->input_printer, lyxrc->printer.c_str());
> where lyxrc is a global LyXRC variable and the call
[...]
> Ultimately, therefore, create_forms() creates a vector of
> Dialogs, one of which is
On Sat, 11 Mar 2000, Angus Leeming wrote:
Oh boy. I was working on the printing form myself when I decided to write
the conversion script (which I'll post in a couple of minutes). I chose
it because it would be a good testcase for xtl also.
> I'm trying to understand form_print.[Ch] in the old
> I propose that the Dialogs constructor be modified to:
> Dialogs(LyXFunc * lyxfunc, LyXRC const & lyxrc )
LyXRC is global so I don't think it should be passed to any function.
I am not sure about the Correct Position of LyXFunc. I have a feeling
that the current relation to LyXViews is n
Here is a small patch for those systems that don't set LINGUAS, so that
the RPM still builds properly.
--
Kayvan A. Sylvan | Proud husband of | Father to my kids:
Sylvan Associates, Inc.| Laura Isabella Sylvan | Katherine Yelena
http://www.successlinks.com/kayv
Bear with me on this one. It isn't difficult, just long!
The current version of LyXGUI contains the following code
LyXGUI::init()
{
...
create_forms();
...
// the print form
fl_set_input(fd_form_print->input_printer, lyxrc->printer.c_str());
}
where l
Ahhh,
> > Was deleting some text when Lyx crashed. Is the following useful to help
track > > the bug down?
> >
> > #0 0x401e0111 in __kill ()
> > (gdb) q
>
> No, it's not useful. You should have typed "where" to see the call stack.
Is the following better
(gdb) where
#0 0x401e
On Sat, Mar 11, 2000 at 02:52:19PM +, Ben Cazzolato wrote:
> Guys
>
> Was deleting some text when Lyx crashed. Is the following useful to help track
> the bug down?
>
> #0 0x401e0111 in __kill ()
> (gdb) q
No, it's not useful. You should have typed "where" to see the call stack.
I'm trying to understand form_print.[Ch] in the old
development branch.
Some points/questions
1. Is it planned to bring PrinterParams.h over to the
current development branch?
2. What are the LyXFunc equivalents (if any) to:
comm->isAvailable()
comm->printBuffer()
3. Compiling f
Guys
Was deleting some text when Lyx crashed. Is the following useful to help track
the bug down?
Ben
Using the command
gdb /usr/bin/lyx core 2>&1 | tee lyxdump.txt
and then
more lyxdump.txt
GNU gdb 4.17.0.11 with Linux support
Copyright 1998 Free Software Foundation, Inc.
GDB is free soft
The last page of my document was a blank page with a red blank and page
separator above that paragraph. The reason I need this is because I was
printing 2 sided, odd pages first in normal order, then even pages in
reverse order.
LyX or gs ignored the blank page, which put the wrong pages on the
re
> Yes, we should not use the print form when exporting at all, that is a
> hack. I got a patch that did the export stuff correct, but I had some
> comments to that patch and asked that it be corrected before I'd
> commit it... this was never done.
> (not long ago 1month?)
>
> Lgb
Can you g
"Rachna Grover" <[EMAIL PROTECTED]> writes:
| Hi all,
|
| Greetings.
|
| I am a final year student doing Computer Science at the University of
| Botswana. My final year (which ends in April 2000) involves designing fonts
| for the Hindi language. I have used Metafont to design the fonts and
|
Angus Leeming <[EMAIL PROTECTED]> writes:
| I'm attempting to move the print dialog over to the SigC++
| stuff. My interest is in the print form, rather than how
| it's called, but if anyone out there can answer my
| question...
|
| Calling the print dialog from lyxfunc.C is easy:
| string LyXFu
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
| Hi folks,
|
| Working with the larest lyx-1.1.5cvs, upon startup I see:
|
| > Warning: language `default' not recognized!
| > Setting language to `default'.
|
| This is confusing, to say the least! What does it mean and is it something
|
Allan Rae <[EMAIL PROTECTED]> writes:
| > FD_form, declared in class FormBase is:
| > struct FD_form
| > {
| > FL_FORM *form;
| > void *vdata;
| > char *cdata;
| > long ldata;
| > };
| >
| > What are vdata, cdata and ldata? They aren't used in the
| > code.
Hi all,
Greetings.
I am a final year student doing Computer Science at the University of
Botswana. My final year (which ends in April 2000) involves designing fonts
for the Hindi language. I have used Metafont to design the fonts and
successfully done so. The last part of my project involves s
> The default command for exporting html with tth is
> tth -t < '$$FName' > '$$OutName'
> However, it should be
> tth -t -L`basename '$$FName' .tex` < '$$FName' > '$$OutName'"
> (with the latter, tth can convert the bibliography, do correct reference etc.)
>
> This has an effect only i
I'm attempting to move the print dialog over to the SigC++
stuff. My interest is in the print form, rather than how
it's called, but if anyone out there can answer my
question...
Calling the print dialog from lyxfunc.C is easy:
string LyXFunc::Dispatch(int ac, char const * do_not_use_this_arg)
{
Allan, I'm going to have a go at this pop-up in the old
development branch.
I'm attacking this one because it appears to be as
complicated as a Signal0 form can get ;) That is, not only
does it display information and hide when the Ok button is
pressed, but it also returns info to the rest of the
Ok, read and digested your recent postings. Also had a play
with fdesign/read the documentation. Also downloaded and
installed doc++, so that we can document this stuff.
Allan > I don't want to have to repeat all the work I did
Allan > last time however. If Angus and John want to do it
Allan > a
22 matches
Mail list logo
