Rob Lahaye wrote:
> I would, if I only understood what this is about.
> Everything seems to be fine here, so I don't know what to fix.
The only help I can give you is that my screen is 800x600
dpi = 74
Zoom = 150
Roman = Utopia
My assumption was that there was something different about those two
i
Garst R. Reese wrote:
> "Garst R. Reese" wrote:
>
>>Martin Vermeer wrote:
>>
>>>BTW, in the current (unpatched) document dialog, some string entry
>>>fields don't display their content when you enter it. E.g. in the
>>>paper tab the bottom margin field.
>>>
>>>The reason appears to be that if the
This patch removes the grfx namespace and replaces it with
lyx::graphics.
namespace alias is used to reduce the hassle work developers.
Both xforms and qt are fixed.
Please comment.
? newfile1.lyx
? qt-build
? string-build
? xforms-build
Index: src/buffer.C
"Garst R. Reese" wrote:
>
> Martin Vermeer wrote:
> >
> > BTW, in the current (unpatched) document dialog, some string entry
> > fields don't display their content when you enter it. E.g. in the
> > paper tab the bottom margin field.
> >
> > The reason appears to be that if the field is not high e
On Thu, Jul 03, 2003 at 03:04:09PM +0200, Andre Poenitz wrote:
> > If allright, then please apply the patch.
>
> Is fine with me.
>
> Others?
Yes, fine.
Our handling of OACR is hopelessly inconsistent in both frontends, but
this change does not make things significantly worse.
regards,
john
On Thu, Jul 03, 2003 at 09:59:20PM +0900, Rob Lahaye wrote:
> Andre Poenitz wrote:
> > How can I close the preamble without using the mouse?
> >
> > There are neither shortcuts to 'ok' nor to 'cancel'...
>
> As for Xforms:
>
>Close/Cancel: Escape-key.
>Apply: Alt-A
>OK: is indeed mis
Andre Poenitz wrote:
> How can I close the preamble without using the mouse?
>
> There are neither shortcuts to 'ok' nor to 'cancel'...
As for Xforms:
Close/Cancel: Escape-key.
Apply: Alt-A
OK: is indeed missing; how about Alt-O, as does the attached patch?
(OK used to be the Ent
On Thu, Jul 03, 2003 at 01:45:02PM +0200, Lars Gullik Bj?nnes wrote:
> | btw, I bet disabling the invocation of collect2 by hand helps this a
> | *lot*
>
> Ok, tell me more.
collect2 is completely unnecessary on Linux afaik. There was a patch
posted to disable the collect2 phase where possible.
John Levon <[EMAIL PROTECTED]> writes:
| On Thu, Jul 03, 2003 at 01:22:58PM +0200, Lars Gullik Bj?nnes wrote:
|
| > | You seem to have forgotten that this makes linking the debug enabled
| > | version in 256 MB Ram almost impossible.
| >
| > Oh... I remember what I want to remember.
|
| btw, I
On Thu, Jul 03, 2003 at 01:22:58PM +0200, Lars Gullik Bj?nnes wrote:
> | You seem to have forgotten that this makes linking the debug enabled
> | version in 256 MB Ram almost impossible.
>
> Oh... I remember what I want to remember.
btw, I bet disabling the invocation of collect2 by hand helps t
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Thu, Jul 03, 2003 at 12:48:53PM +0200, Lars Gullik Bjønnes wrote:
| > | But that would mean we pull in std::string in 74 files or so, even when
| > | configuring --with-included-string, wouldn't it?
| >
| > so we should ditch included-string as well
On Thu, Jul 03, 2003 at 11:51:45AM +0100, John Levon wrote:
> On Thu, Jul 03, 2003 at 12:28:55PM +0200, Andre Poenitz wrote:
>
> > Thanks for the info.
> >
> > Manually resizing the LyX window seems to work though.
>
> Have you valgrinded this ?
No.
But I have now removed the delete/new sequen
On Thu, Jul 03, 2003 at 12:48:53PM +0200, Lars Gullik Bjønnes wrote:
> | But that would mean we pull in std::string in 74 files or so, even when
> | configuring --with-included-string, wouldn't it?
>
> so we should ditch included-string as well then.
You seem to have forgotten that this makes lin
On Thu, Jul 03, 2003 at 09:18:56AM +0200, Andre Poenitz wrote:
> Who is actually responsible for the dialogs?
For xforms: Rob and Angus
For Qt: Me, Edwin, Juergen S
Or something like that
regards
john
On Thu, Jul 03, 2003 at 12:28:55PM +0200, Andre Poenitz wrote:
> Thanks for the info.
>
> Manually resizing the LyX window seems to work though.
Have you valgrinded this ?
john
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Thu, Jul 03, 2003 at 11:59:51AM +0200, Lars Gullik Bjønnes wrote:
| > | Dependencies with the rest of LyX which I want to avoid.
| > | (Not just "Lsstream.h" but "LString.h" etc...)
| > |
| > | The price is copying a single file for four-year-old com
On Thu, Jul 03, 2003 at 12:31:50PM +0200, Edwin Leuven wrote:
> i guess this one's for andre,
>
> i often use dcolumn to align columns on the decimal point
>
> where i define a custom column alignment in the preamble as follows
>
> \usepackage{dcolumn}
> \newcolumntype{d}[1]{D{.}{.}{#1}}
>
> an
On Thu, Jul 03, 2003 at 12:17:08PM +0200, Juergen Vigna wrote:
> I don't have the time *sight* to test this stuff, but just for the
> public info the above code is not there because of "multiple BV",
> the code above is there because LyXScreen resize operations deleted
> the LyXText instance!
Than
i guess this one's for andre,
i often use dcolumn to align columns on the decimal point
where i define a custom column alignment in the preamble as follows
\usepackage{dcolumn}
\newcolumntype{d}[1]{D{.}{.}{#1}}
an then add a latex argument in the table, f.e. d{5} in the 3rd column in the
attac
Andre Poenitz wrote:
This is arguably a step back on the path to 'multiple BufferView' as
now there's just a single 'active' BufferView again (complete rebreak when
changing BufferViews), but the current 'solution' contained (among others)
- bool clear = false;
- if (!lt) {
-
On Thu, Jul 03, 2003 at 11:59:51AM +0200, Lars Gullik Bjønnes wrote:
> | Dependencies with the rest of LyX which I want to avoid.
> | (Not just "Lsstream.h" but "LString.h" etc...)
> |
> | The price is copying a single file for four-year-old compilers.
> | No big deal IMO.
>
> So we should do thi
Alfredo Braunstein <[EMAIL PROTECTED]> writes:
| > It is not really supposed to stay a pointer, but to be a list of
| > BufferViews using this buffer.
| Isn't this more cleanly implemented with signals (or eventually, with
| lyxfuncs if I ever get to understand how they work)? I don't understand
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Thu, Jul 03, 2003 at 11:26:58AM +0200, Jean-Marc Lasgouttes wrote:
| > Andre> On Thu, Jul 03, 2003 at 02:00:10AM -0700, Kayvan A. Sylvan
| > Andre> wrote:
| > >> C++ Compiler: g++ (2.95.1) [...] g++ -DHAVE_CONFIG_H -I. -I.
| > >> -I../../src -I./../ -
On Thu, Jul 03, 2003 at 11:55:12AM +0200, Alfredo Braunstein wrote:
> > There is a bv field in FuncRequest for starters.
>
> And how does calling BufferView through FuncRequest (through/passing
> BufferView again) leads to cleaner code as opposed to calling it directly?
*shrug*
Perhaps it doesn'
Andre Poenitz wrote:
> On Thu, Jul 03, 2003 at 11:42:59AM +0200, Alfredo Braunstein wrote:
>> > Then there are a couple of buffers, each could be looked at from
>> > different views. This would make a nice tree, wouldn't it? Now all
>> > requests can be fed it at the root of that tree, i.e. at the
On Thu, Jul 03, 2003 at 11:42:59AM +0200, Alfredo Braunstein wrote:
> > Then there are a couple of buffers, each could be looked at from different
> > views. This would make a nice tree, wouldn't it? Now all requests can be
> > fed it at the root of that tree, i.e. at the LyXView or the LyXFunc. As
Andre Poenitz wrote:
>> - gets the LyXView from the BufferView
>> - get the LyXFunc from the LyXView
>> - pass this LyXFunc to LaTeX
>> - LaTeX dispatch its messages there
>
> Well, _I_'d ignore the possibility of different LyXViews for the next few
> years (I have done so for a while now, and I
I just wanted to revert most of the no-update changes in BRANCH_NOUPDATE
and start over with 'just insettext'.
But I got:
- Forwarded message from [EMAIL PROTECTED] -
Envelope-to: [EMAIL PROTECTED]
Delivery-date: Thu, 03 Jul 2003 11:32:05 +0200
Date: Thu, 3 Jul 2003 11:32:02 +0200
Subje
On Thu, Jul 03, 2003 at 11:26:58AM +0200, Jean-Marc Lasgouttes wrote:
> Andre> On Thu, Jul 03, 2003 at 02:00:10AM -0700, Kayvan A. Sylvan
> Andre> wrote:
> >> C++ Compiler: g++ (2.95.1) [...] g++ -DHAVE_CONFIG_H -I. -I.
> >> -I../../src -I./../ -I../../boost +-I/usr/X11R6/include -O2
> >> -fpermiss
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> On Thu, Jul 03, 2003 at 02:00:10AM -0700, Kayvan A. Sylvan
Andre> wrote:
>> C++ Compiler: g++ (2.95.1) [...] g++ -DHAVE_CONFIG_H -I. -I.
>> -I../../src -I./../ -I../../boost +-I/usr/X11R6/include -O2
>> -fpermissive -ftemplate-depth
On Thu, Jul 03, 2003 at 02:00:10AM -0700, Kayvan A. Sylvan wrote:
> C++ Compiler: g++ (2.95.1)
> [...]
> g++ -DHAVE_CONFIG_H -I. -I. -I../../src -I./../ -I../../boost
> +-I/usr/X11R6/include -O2 -fpermissive -ftemplate-depth-30 -W -Wall -c -o
> +texparser.o `test -f texparser.C
On Thu, Jul 03, 2003 at 10:25:43AM +0200, Alfredo Braunstein wrote:
> Then there's something fishy going on right now, because the current (say,
> converter) code does this:
>
> - gets the/a BufferView from the buffer through Buffer::getUser (getUser is
> conceptually wrong per se IMHO - not much
Configuration
Host type: i686-pc-linux-gnu
Special build flags:warnings assertions xforms-image-loader
C Compiler: gcc
C Compiler flags: -g -O2
C++ Compiler: g++ (2.95.1)
C++ Compiler flags:
Lars Gullik Bjønnes wrote:
> Alfredo Braunstein <[EMAIL PROTECTED]> writes:
>
> | - gets the/a BufferView from the buffer through Buffer::getUser (getUser
> | is conceptually wrong per se IMHO - not much different from
> | current_view)
>
> It is not really supposed to stay a pointer, but to be
Alfredo Braunstein <[EMAIL PROTECTED]> writes:
| - gets the/a BufferView from the buffer through Buffer::getUser (getUser is
| conceptually wrong per se IMHO - not much different from
| current_view)
It is not really supposed to stay a pointer, but to be a list of
BufferViews using this buffer.
Martin Vermeer wrote:
> Ah. That's not right. Perhaps we should continue to call it "Note",
> not "blind". What would be most suitable name? I think this string is
> defined in factory.C line 74. You could try changing it.
I think "Note" is best. People are used to it. But the complete inset (i.e.
Andre Poenitz wrote:
>> Does LyXFunc::dispatch is able to dispatch the message to all bv's the
>> buffer is connected to (and not others)? Would this be wanted?
>
> As we don't have multiple views right now: |all| == 1, so 'yes'. But I
> don't know how this scales up. Does this information need t
On Thu, Jul 03, 2003 at 09:53:53AM +0200, Alfredo Braunstein wrote:
> Andre Poenitz wrote:
>
> > I just wonder whether the whole signal business does not somehow
> > undermine the 'LFUN everywhere' approach. For peaceful coexistence I'd
> > expect that any 'unusual' signal gets delivered to LyXFu
Andre Poenitz wrote:
> I just wonder whether the whole signal business does not somehow
> undermine the 'LFUN everywhere' approach. For peaceful coexistence I'd
> expect that any 'unusual' signal gets delivered to LyXFunc::dispatch which
> in turn figures out the BufferView, and calls dispatch()
On Thu, Jul 03, 2003 at 07:12:53AM +0300, Munzir Taha Obeid wrote:
> > really simple way out...
> It works!
> I am not sure why a percent sign not a space but it _almost_ work.
> If I understand you properly, I made a small file in lyx and exported it to
> TeX. I edited the file by adding the perc
On Wed, Jul 02, 2003 at 10:39:47PM +0200, Alfredo Braunstein wrote:
> This patch
>
> - introduces two new signals in buffer: busy and message. I've renamed
> parseError to error because it's used more generally than for parse errors.
> It could still use a better name maybe.
>
> - adds all three
On Wed, Jul 02, 2003 at 06:45:38PM +0100, John Levon wrote:
> On Wed, Jul 02, 2003 at 06:35:26PM +0200, Andre Poenitz wrote:
>
> > How can I close the preamble without using the mouse?
>
> Workaround is Alt-A Escape
>
> The existence of Apply at all in that dialog is baffling
Well, it seems to
42 matches
Mail list logo
