> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Lars Gullik Bjønnes wrote:
>> I think we should do this now... Will make it easier to change
>> layout format later as well...
Georg> OK, this is the complete patch that is going in.
Georg> I also fixed a broken 'Input stnumarticle.i
Jean-Marc Lasgouttes wrote:
>> "Georg" == Georg Baum
>> <[EMAIL PROTECTED]>
>> writes:
>
> Georg> Jean-Marc Lasgouttes wrote:
>>> Does it handle .inc files?
>
> Georg> Yes: It is called for inc files, since they go through
> Georg> LyXTextClass::Read, and the script converts them sin
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Jean-Marc Lasgouttes wrote:
>> Does it handle .inc files?
Georg> Yes: It is called for inc files, since they go through
Georg> LyXTextClass::Read, and the script converts them since they
Georg> have the same syntax as .layout files. O
Jean-Marc Lasgouttes wrote:
> Does it handle .inc files?
Yes: It is called for inc files, since they go through LyXTextClass::Read,
and the script converts them since they have the same syntax as .layout
files. Or do I miss a reason why it might not work?
Georg
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
|
| Georg> There was a discussion how to call it from LyX, but nobody
| Georg> commented on my questions whether we want it in 1.4.0 IMO, it
| Georg> should be included.
|
| Does it handle
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> There was a discussion how to call it from LyX, but nobody
Georg> commented on my questions whether we want it in 1.4.0 IMO, it
Georg> should be included.
Does it handle .inc files?
Georg> I prefer this approach over doing the conve
Angus Leeming wrote:
> I think that it's important to not overwrite the existing layout file
> (well done ;)) but you might pop up a dialog to inform the user where he
> can grab the converted file from. Only delete it if he doesn't want to
> grab it.
The problem is that lyxtextclass.C is also us
Georg Baum wrote:
> This reminds me of the layout file converter that I sent some days ago.
[...snip...]
> I would really like to put this in. Cooments?
I think that this is a fantastic idea and that it can't break anything that
isn't broken already (user's 1.3 layout files used by lyx 1.4).
I th
Am Montag, 17. Oktober 2005 16:40 schrieb Bennett Helm:
> Opening old beamer presentations results in a crash. The problem is
> that the beamer.layout file contains the following line:
>
> MaxCounterCounter_Section
>
> (In fact, any .layout file with this line in it will cause LyX to
Opening old beamer presentations results in a crash. The problem is
that the beamer.layout file contains the following line:
MaxCounterCounter_Section
(In fact, any .layout file with this line in it will cause LyX to
crash.) Commenting out this line in the .layout file enables
ever
On Mon, May 17, 2004 at 10:38:54AM +0100, Angus Leeming wrote:
> There's a strange flash as the screen is redrawn at the current cursor
> position (I assume) followed by another redraw at the inset location.
> The dialog is *not* opened. Click on it again and everything behaves
> as you'd expect.
>
Alfredo Braunstein wrote:
> I also think so, but maybe we should think a bit more about pluses
> and cons. For instance, what about clicking in button insets? Right
> now it has the effect of popping the dialog *and* setting the cursor
> after it. What's the logic? Is there an useability advantage
Angus Leeming wrote:
> It always used to do this and I'm a crusty old bugger who doesn't like
> change?
;-) Gotcha
> So, no, not really ;-)
>
> We're not M$ after all, so backwards-compatibility for the sake of
> backwards-compatibility shouldn't be the 'be all and end all'. Do it
> your way.
Jean-Marc Lasgouttes wrote:
> inset-toggle has the behaviour of opening the inset without entering
> there (and that's why I opposed to putting cursor inside). But now
> that I think of it, if you click on an element in the text, it means
> that you want to set the cursor there. So if one clicks o
> "Alfredo" == Alfredo Braunstein <[EMAIL PROTECTED]> writes:
Alfredo> Maybe just to see what's inside? Like: "I'm editing here...
Alfredo> hmmm let's see what's on the footnote down there... *click*
Alfredo> -- now I've lost the position where I was editing...
inset-toggle has the behaviour
Robin S. Socha wrote:
> Alfredo Braunstein <[EMAIL PROTECTED]> writes:
>> Robin S. Socha wrote:
>
>>> Not having used LyX for roughly 18 months, I found the new behaviour
>>> quite counter-intuitive.
>>
>> Could you elaborate? Do you find couter-intuitive the fact that the
>> cursor is not placed
Alfredo Braunstein <[EMAIL PROTECTED]> writes:
> Robin S. Socha wrote:
>> Not having used LyX for roughly 18 months, I found the new behaviour
>> quite counter-intuitive.
>
> Could you elaborate? Do you find couter-intuitive the fact that the cursor
> is not placed inside?
Yes, obviously. I mean,
Alfredo Braunstein wrote:
> Angus Leeming wrote:
>
>> Alfredo Braunstein wrote:
>>> So the question is: do we want opening an inset to automatically
>>> put the cursor inside? Or should we *not* call fitCursor when
>>> opening/closing footnotes? (are there other LFUNs that need it)?
>>
>> I thin
Robin S. Socha wrote:
> Not having used LyX for roughly 18 months, I found the new behaviour
> quite counter-intuitive.
Could you elaborate? Do you find couter-intuitive the fact that the cursor
is not placed inside?
If what you find couterintuitive is just the jumping, then of course we
agree,
Angus Leeming wrote:
> Alfredo Braunstein wrote:
>> So the question is: do we want opening an inset to automatically put
>> the cursor inside? Or should we *not* call fitCursor when
>> opening/closing footnotes? (are there other LFUNs that need it)?
>
> I think that we do want to put the cursor i
Robin S. Socha wrote:
>>> I think that we do want to put the cursor inside.
>>
>> I don't think so. Opening is opening and moving the cursor is
>> moving the cursor.
>
> May I humbly comment that currently opening an inset positions the
> cursor in the first line of the buffer - and that is
> coun
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>> Alfredo Braunstein wrote:
>>> So the question is: do we want opening an inset to automatically
>>> put the cursor inside? Or should we *not* call fitCursor when
>>> opening/closing footnotes? (are there
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Alfredo Braunstein wrote:
>> So the question is: do we want opening an inset to automatically
>> put the cursor inside? Or should we *not* call fitCursor when
>> opening/closing footnotes? (are there other LFUNs that need it)?
Angu
Angus Leeming <[EMAIL PROTECTED]> writes:
> Alfredo Braunstein wrote:
>> So the question is: do we want opening an inset to automatically put
>> the cursor inside? Or should we *not* call fitCursor when
>> opening/closing footnotes? (are there other LFUNs that need it)?
>
> I think that we do want
Alfredo Braunstein wrote:
> So the question is: do we want opening an inset to automatically put
> the cursor inside? Or should we *not* call fitCursor when
> opening/closing footnotes? (are there other LFUNs that need it)?
I think that we do want to put the cursor inside.
--
Angus
Robin S. Socha wrote:
> ssertion triggered in virtual void InsetText::draw(PainterInfo&, int, int)
> const by failing check "!text_.paragraphs().begin()->rows.empty()" in file
> insettext.C:192
The bug responsible for this is the following: all handled LFUNS (including
opening/closing footnotes)
Configuration
Host type: i686-pc-linux-gnu
Special build flags:warnings assertions use-aspell
compression
C Compiler: gcc
C Compiler flags: -g -O2
C++ Compiler: g++ (3.3.3)
C++ Compiler flags:
27 matches
Mail list logo
