Re: CT painting problems
Am 24.02.2011 um 14:10 schrieb Stephan Witt: > Am 24.02.2011 um 13:36 schrieb Pavel Sanda: > >> Stephan Witt wrote: >>> Index: src/rowpainter.cpp >>> === >>> --- src/rowpainter.cpp (Revision 37780) >>> +++ src/rowpainter.cpp (Arbeitskopie) >>> @@ -899,7 +899,7 @@ >>> change_running.color(), Painter::line_solid, >>> solid_line_thickness_); >>> >>> // Change might continue with a different author or type >>> - if (change.changed() && !highly_editable_inset) { >>> + if (change.changed() /* && !highly_editable_inset */) { >>> change_running = change; >>> change_last_x = int(x_); >> >> looks better for normal insets. still something is missing - it looks as if >> there more independent painting modes. > >> one is triggered when i just press normal character - then your fix does not >> work and painting line over inset disappear. >> other one is when i hoover with mouse with inset. then regardless your fix >> works line was there (iirc). >> yet another one is when i press enter - then line is again there. > > Yes, I see. I'll have a look later. Until now I can see two problems: 1. as you noted the insets is painted with different "code paths". One cares for CT and the other not, obviously. 2. the contents of a deleted inset does not know of its state. Does anyone know how to derive the pit and pos of the enclosing paragraph of an inset (without cursor)? Currently I'm really short of time and cannot walk many hours through the code... Stephan
Re: (Regression in r37749 by forenr) Assert with ERT inset and LaTeX Error dialog open.
Enrico Forestieri wrote: > On Mon, Feb 28, 2011 at 08:48:46PM +0800, John McCabe-Dansted wrote: > > > To Reproduce: > > 1) Press Alt-Delete to insert a non-printable character > > 2) Press Ctrl-L to insert an ERT inset > > 3) Press Ctrl-D to bring up the LaTeX error dialog box. > > 4) Click inside the ERT. > > Sorry, cannot reproduce. neither me. John are you running up to date svn? pavel
Re: Approve Wiki URL password
Mathijs Miermans wrote: > In the following section I've posted 2 urls: > http://wiki.lyx.org/Windows/LyXWinTips#toc6. > > Could these be approved? I've done that. Jürgen
Approve Wiki URL password
Hi, In the following section I've posted 2 urls: http://wiki.lyx.org/Windows/LyXWinTips#toc6. Could these be approved? Best regards, Mathijs
Re: (Regression in r37749 by forenr) Assert with ERT inset and LaTeX Error dialog open.
On Mon, Feb 28, 2011 at 08:48:46PM +0800, John McCabe-Dansted wrote: > To Reproduce: > 1) Press Alt-Delete to insert a non-printable character > 2) Press Ctrl-L to insert an ERT inset > 3) Press Ctrl-D to bring up the LaTeX error dialog box. > 4) Click inside the ERT. Sorry, cannot reproduce. -- Enrico
(Regression in r37749 by forenr) Assert with ERT inset and LaTeX Error dialog open.
To Reproduce: 1) Press Alt-Delete to insert a non-printable character 2) Press Ctrl-L to insert an ERT inset 3) Press Ctrl-D to bring up the LaTeX error dialog box. 4) Click inside the ERT. I then get the following assert. This appears to be a regression in r37749 by forenr, though note that I need the compile fix found in r37751 to compile r37749. (Ubuntu 10.04 x86_64) Program received signal SIGABRT, Aborted. 0x751dfa75 in *__GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. in ../nptl/sysdeps/unix/sysv/linux/raise.c (gdb) #0 0x751dfa75 in *__GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 cpp abort.c #1 0x751e35c0 in *__GI_abort () at abort.c:92 #2 0x008e1f2e in __replacement_assert (this=0x6093, __pos=24723) at /usr/include/c++/4.4/x86_64-linux-gnu/bits/c++config.h:284 #3 std::basic_string, std::allocator >::operator[] (this=0x6093, __pos=24723) at /usr/include/c++/4.4/bits/basic_string.h:740 #4 0x008cb374 in lyx::Paragraph::isLineSeparator (this=0x1e67b00, cpp Paragraph.cpp pos=24723) at Paragraph.cpp:2835 #5 0x009da7e8 in copySelectionToStack (cur=..., cutstack=...) cpp CutAndPaste.cpp at CutAndPaste.cpp:857 For more information see: http://gmatht.homelinux.net/xp/keytest/html_out/out/t14//html//1298889710.html -- John C. McCabe-Dansted
Re: disolving child docs
Le 17/02/2011 23:07, Edwin Leuven a écrit : i have a document with several child documents using 'input' is there an easy way to "promote" the content of a child document to the master document? i.e. to get rid of the input and just have the text in the master doc? there is unfortunately no "remove and insert here" in the context menu or am i missing something? It should be as easy as implementing inset-dissolve for InsetInclude. We already have code for inserting file contents in document, so it should be highly doable. The only tricky thing is to find the right way for the inset to "commit suicide". JMarc
Re: manpage.layout
Jean-Marc Lasgouttes wrote: > It looks correct, but I would replace the message "Failed to find > \Declare line" by "Failed to find valid \Declare line", since there > is technically a \DeclareXXX line. Good point. Jürgen
Re: manpage.layout
Le 28/02/2011 08:58, Jürgen Spitzmüller a écrit : Jürgen Spitzmüller wrote: How about the attached patch? No opinions? It looks correct, but I would replace the message "Failed to find \Declare line" by "Failed to find valid \Declare line", since there is technically a \DeclareXXX line. JMarc