RE: Scrolling and painting is incredibly slow these days

and another profile, from linux this time: http://ecodip.net/scroll.zip

RE: Scrolling and painting is incredibly slow these days

and another profile, from linux this time: http://ecodip.net/scroll.zip

RE: tabular width

Jürgen wrote: Leuven, E. wrote: do we want this for 1.6 or should i wait? This is a most welcome feature, but IMHO it's too late for 1.6. sure Some minor comments: * the lyx2lyx reversion leads to dataloss. Instead of just removing the options, you'll have to revert those tabulars

RE: tabular width

i realize that this leads to dataloss, but in this case i definitely prefer dataloss and tables i can edit in lyx to big blurs of ert and no dataloss... well. I understand. But our goal with revertion to old formats is not as much comfortable UI but identical output (as much as possible).

RE: tabular width

Jürgen Spitzmüller wrote: Leuven, E. wrote: as i wrote: revert to what is supported i think that this is a clear and very standard policy So you want to remove every new feature on reversion? That's the consequence of revert to what is _natively_ supported (your interpretation, if I'm

RE: tabular width

Also, if we go that route, where do you draw the line? as i wrote: revert to what is supported i think that this is a clear and very standard policy ... this being said, i don't care too much about this reversion stuff myself

RE: tabular width

Jürgen Spitzmüller wrote: If it's just a mode (i.e. a --edwin switch), it's o.k. i would be honored of course, but... However, I think I'm not the only user who relies on backwards output compatibility. ...i would expect this to be pretty rare, so would rather suggest a --spitz switch ;-)

RE: tabular width

Jürgen wrote: Just two scenarios which I more or less found myself into in the past: 1. LyX 1.5 has a bug 2. my laptop refuses to work i understand that backward output compatibility was convenient, but you must admit that these are not typical use cases (also, in both situations (last

RE: tabular width

Jürgen wrote: Leuven, E. wrote: i understand that backward output compatibility was convenient, but you must admit that these are not typical use cases What is typical? These cases are much more typical for me than the case outline by you. So it just depends on the user's context. maybe

RE: tabular width

Jürgen wrote: >>Leuven, E. wrote: >> do we want this for 1.6 or should i wait? > > This is a most welcome feature, but IMHO it's too late for 1.6. sure > Some minor comments: > > * the lyx2lyx reversion leads to dataloss. Instead of just removing the > option

RE: tabular width

>> i realize that this leads to dataloss, but in this case i definitely prefer >> dataloss and tables i can edit in lyx to big blurs of ert and no >> dataloss... > > well. I understand. But our goal with revertion to old formats is not as much > comfortable UI but identical output (as much as

RE: tabular width

Jürgen Spitzmüller wrote: > Leuven, E. wrote: >> as i wrote: revert to what is supported >> >> i think that this is a clear and very standard policy > > So you want to remove every new feature on reversion? That's the consequence > of "revert to what is _native

RE: tabular width

> Also, if we go that route, where do you draw the line? as i wrote: revert to what is supported i think that this is a clear and very standard policy ... this being said, i don't care too much about this reversion stuff myself

RE: tabular width

Jürgen Spitzmüller wrote: > If it's just a mode (i.e. a --edwin switch), it's o.k. i would be honored of course, but... > However, I think I'm not the only user who relies on backwards output > compatibility. ...i would expect this to be pretty rare, so would rather suggest a --spitz switch

RE: tabular width

Jürgen wrote: > Just two scenarios which I more or less found myself into in the past: > > 1. LyX 1.5 has a bug > 2. my laptop refuses to work i understand that backward output compatibility was convenient, but you must admit that these are not typical use cases (also, in both situations (last

RE: tabular width

Jürgen wrote: > Leuven, E. wrote: >> i understand that backward output compatibility was convenient, but you >> must admit that these are not typical use cases > > What is "typical"? These cases are much more typical for me than the case > outline by you. So it

RE: tabular width

ping -Original Message- From: Leuven, E. [mailto:[EMAIL PROTECTED] Sent: Fri 5/16/08 13:43 To: lyx-devel@lists.lyx.org Subject: tabular width i've added setting the tabular width through the ui in the attached (also see screenshot) the patch is straightforward: add 'width

RE: tabular width

ping -Original Message- From: Leuven, E. [mailto:[EMAIL PROTECTED] Sent: Fri 5/16/08 13:43 To: lyx-devel@lists.lyx.org Subject: tabular width i've added setting the tabular width through the ui in the attached (also see screenshot) the patch is straightforward: add 'width

RE: bug 4861 (Joost?)

By the way, please take a look at this bug (you too Edwin ;-): http://bugzilla.lyx.org/show_bug.cgi?id=4846 i haven't been able to reproduce this...

RE: bug 4861 (Joost?)

Are you on Vista? nope, xp...

RE: bug 4861 (Joost?)

> By the way, please take a look at this bug (you too Edwin ;-): > > http://bugzilla.lyx.org/show_bug.cgi?id=4846 i haven't been able to reproduce this...

RE: bug 4861 (Joost?)

> Are you on Vista? nope, xp...

RE: Change bundled file directly? (Was: Summary to the individual embedding debate.)

Abdelrazak Younes wrote: I personally think supporting base64 embedding is interesting but should not be used for bundling purpose. And I do think we should make our format slowly evolve towards ODF in the 1.7 devel. That being said, I am not convinced the lyxdir folder should be along

cannot view source

an update/signal got deleted by mistake recently?

RE: Change bundled file directly? (Was: Summary to the individual embedding debate.)

Abdelrazak Younes wrote: > I personally think supporting base64 > embedding is interesting but should not be used for bundling purpose. > > And I do think we should make our format slowly evolve towards > ODF in the 1.7 devel. That being said, I am not convinced the lyxdir > folder should be

cannot view source

an update/signal got deleted by mistake recently?

the citation dialog

seems to have grown lately. perhaps someone can put it on a diet? as an aside: do we need something like the attached since the selection manager is created without a parent? Index: src/frontends/qt4/GuiCitation.cpp === ---

the citation dialog

seems to have grown lately. perhaps someone can put it on a diet? as an aside: do we need something like the attached since the selection manager is created without a parent? Index: src/frontends/qt4/GuiCitation.cpp === ---

RE: New www.lyx.org is now live

and remove the 3rd paragraph perhaps? there is a bit too much blah blah there imho and it makes the header of the news section just drop off my screen (1024x768) ... btw, thanks to everybody who contributed to the new site. it's a huge improvement! edwin

RE: New www.lyx.org is now live

and remove the 3rd paragraph perhaps? there is a bit too much blah blah there imho and it makes the header of the news section just drop off my screen (1024x768) ... btw, thanks to everybody who contributed to the new site. it's a huge improvement! edwin

RE: Embedding feature, final remarks and farewell.

Pavel Sanda wrote: that will be my last commit. that is the best solution if you cannot live with compromise. i guess he could live if people start to flame embedding philosophy when he asked in start of implementing. i had the impression bo did most of the flaming himself but you're are

RE: Re: [patch] support for beamerarticle

Juergen Spitzmueller wrote: By document class change. ok (i thought there was a document class option to do that) If you have a beamer presentation, chose the document class article (beamer) to get the handout. maybe call it beamer handout (article) ? ... no objections btw

RE: Re: [patch] support for beamerarticle

Abdel wrote: How many of you guys speak French by the way? Edwin? courrament

RE: Re: [patch] support for beamerarticle

courrament couramment i am a dismal speller, i know

RE: Embedding feature, final remarks and farewell.

Pavel Sanda wrote: >>> that will be my last commit. >> that is the best solution if you cannot live with compromise. > > i guess he could live if people start to flame embedding philosophy > when he asked in start of implementing. i had the impression bo did most of the flaming himself but

RE: Re: [patch] support for beamerarticle

Juergen Spitzmueller wrote: > By document class change. ok (i thought there was a document class option to do that) > If you have a beamer presentation, chose the > document class "article (beamer)" to get the handout. maybe call it beamer handout (article) ? ... no objections btw

RE: Re: [patch] support for beamerarticle

Abdel wrote: > How many of you guys speak French by the way? > Edwin? courrament

RE: Re: [patch] support for beamerarticle

>> courrament > > couramment i am a dismal speller, i know

RE: The fourth embedding proposal from Abdel.

Bo Peng [EMAIL PROTECTED] writes: Maybe I should wait until you guys reach an agreement? i have the impression that us guys basically agree.

RE: The fourth embedding proposal from Abdel.

"Bo Peng" <[EMAIL PROTECTED]> writes: > Maybe I should wait until you guys reach an agreement? i have the impression that "us guys" basically agree.

about captions in longtables

the new line setting code i introduced some time ago is incompatible with the way we handle captions in longtables. atm it longtable caption support in lyx is a dirty hack: we enter \caption{blah} \\% in a cell and this will effectively insert a caption and comment out the rest of the row

about captions in longtables

the new line setting code i introduced some time ago is incompatible with the way we handle captions in longtables. atm it longtable caption support in lyx is a dirty hack: we enter \caption{blah} \\% in a cell and this will effectively insert a caption and comment out the rest of the row

numbered footnotes

it happens quite often that a co-author asks me can you change blah blah blah in footnote 13? my answer then typically is footnote 13? how does it start? ... (didn't you once had this sort of working jean-marc?)

numbered footnotes

it happens quite often that a co-author asks me "can you change blah blah blah in footnote 13?" my answer then typically is "footnote 13? how does it start?" ... (didn't you once had this sort of working jean-marc?)

Re: don't know how to change this otherwise

http://www.lyx.org/trac/changeset/24172 windoze doesn't like it: Added: C:\lyx\trunk\lib\images\math\Vert.png Added: C:\lyx\trunk\lib\images\math\vert.png Error: In directory 'C:\lyx\trunk\lib\images\math' Error: Can't move source to dest Error: Can't move

RE: don't know how to change this otherwise

No idea then. Someone has to teach me how to do this properly. as i wrote: add Vert.png as vert2.png to svn and add { Vert, vert2 }, to sorted_png_map in GuiToolbar.cpp (start at line 111) regards, ed.

Re: don't know how to change this otherwise

http://www.lyx.org/trac/changeset/24172 windoze doesn't like it: Added: C:\lyx\trunk\lib\images\math\Vert.png Added: C:\lyx\trunk\lib\images\math\vert.png Error: In directory 'C:\lyx\trunk\lib\images\math' Error: Can't move source to dest Error: Can't move

RE: don't know how to change this otherwise

> No idea then. Someone has to teach me how to do this properly. as i wrote: add Vert.png as vert2.png to svn and add { "Vert", "vert2" }, to sorted_png_map in GuiToolbar.cpp (start at line 111) regards, ed.

RE: suggestion for windows installar

Joost Verburg wrote: The Qt stuff would have been the difficult part for me :) To obtain the metafile data you just need a few API calls. The attached patch works fine for me. great... Andre wrote: Cool stuff. Nevertheless, could we try stick to LyX style also in Windows-only code?

RE: suggestion for windows installar

Joost Verburg wrote: >> The Qt stuff would have been the difficult part for me :) To obtain the >> metafile data you just need a few API calls. The attached patch works >> fine for me. great... > Andre wrote: > Cool stuff. > > Nevertheless, could we try stick to LyX style also in Windows-only

RE: Re: suggestion for windows installar

Joost Verburg wrote: Done :) Everything will be installed and configured automatically. that's quick! we could perhaps have the default paste in original format and offer an additional paste as eps... Yes, that's a good idea. Can you have a look at the clipboard copy-pasting of metafile

RE: Re: suggestion for windows installar

Joost Verburg wrote: > Done :) Everything will be installed and configured automatically. that's quick! >> we could perhaps have the default paste in original >> format and offer an additional "paste as eps"... > > Yes, that's a good idea. Can you have a look at the clipboard > copy-pasting

suggestion for windows installar

i just discovered this: http://wiki.lyx.org/Windows/MetafileToEPSConverter and thought that i might be nice to have support for this in the installer (ie setting up the printer and converter) we could then add support for copy-pasting emf/wmf directly from the clipboard as eps file (and

RE: Re: suggestion for windows installar

Joost Verburg wrote: I wrote this tool (some parts are based on other GPL software). it is very convenient I'll have a look at the possibilities to install and configure the printer automatically. great I would recommend to save the EMF/WMF images in the original format. There can

suggestion for windows installar

i just discovered this: http://wiki.lyx.org/Windows/MetafileToEPSConverter and thought that i might be nice to have support for this in the installer (ie setting up the printer and converter) we could then add support for copy-pasting emf/wmf directly from the clipboard as eps file (and

RE: Re: suggestion for windows installar

Joost Verburg wrote: > I wrote this tool (some parts are based on other GPL software). it is very convenient > I'll > have a look at the possibilities to install and configure the printer > automatically. great > I would recommend to save the EMF/WMF images in the original format. > There

RE: drawing of selection

Since you asked. :-) 2nd iteration. this is the current situation: http://leuven.economists.nl/lyx/sel1.png the attached patch gives this: http://leuven.economists.nl/lyx/sel2.png Index: src/TextMetrics.cpp === ---

RE: drawing of selection

can you get the section/enumerate numbers to be highlighted as well? not atm i think. i have the impression that insets don't take into account whether they are selected or not when they paint themselves...

RE: drawing of selection

Jurgen wrote: Your second patch is all that I was asking for. perhaps, but the ignorance of insets about being selected is illustrated these two screenshots: http://leuven.economists.nl/lyx/sel2.png http://leuven.economists.nl/lyx/sel3.png

RE: drawing of selection

> Since you asked. :-) 2nd iteration. this is the current situation: http://leuven.economists.nl/lyx/sel1.png the attached patch gives this: http://leuven.economists.nl/lyx/sel2.png Index: src/TextMetrics.cpp === ---

RE: drawing of selection

> can you get the section/enumerate numbers to be highlighted as well? not atm i think. i have the impression that insets don't take into account whether they are selected or not when they paint themselves...

RE: drawing of selection

Jurgen wrote: > Your second patch is all that I was asking for. perhaps, but the ignorance of insets about being selected is illustrated these two screenshots: http://leuven.economists.nl/lyx/sel2.png http://leuven.economists.nl/lyx/sel3.png

RE: Re: New site

btw, i see this when i reduce the width of my browser window (firefox 2.0.0.13): http://leuven.economists.nl/lyx/site.png

RE: Re: New site

btw, i see this when i reduce the width of my browser window (firefox 2.0.0.13): http://leuven.economists.nl/lyx/site.png

RE: Re: drawing problems?

Abdel wrote: You should use Row::sel_beg and Row::sel_end instead of cursor().selBegin().pos() and cursor().selEnd().pos(). thanks. the attached *almost* works, but the text in the whole row where the selection starts/ends ends up being marked as selected (hope i am clear). haven't been able

RE: Re: drawing problems?

slowly learning... the attached works! comments? Index: src/Color.cpp === --- src/Color.cpp (revision 24016) +++ src/Color.cpp (working copy) @@ -102,6 +102,8 @@ { Color_background, N_(background), background, linen,

RE: Re: drawing problems?

Edwin wrote: the attached works! and the proof: http://leuven.economists.nl/lyx/selection.png

RE: Re: drawing problems?

Abdel wrote: comments? None. ok to commit?

RE: Re: drawing problems?

Abdel wrote: > You should use Row::sel_beg and Row::sel_end instead of > cursor().selBegin().pos() and cursor().selEnd().pos(). thanks. the attached *almost* works, but the text in the whole row where the selection starts/ends ends up being marked as selected (hope i am clear). haven't been

RE: Re: drawing problems?

slowly learning... the attached works! comments? Index: src/Color.cpp === --- src/Color.cpp (revision 24016) +++ src/Color.cpp (working copy) @@ -102,6 +102,8 @@ { Color_background, N_("background"), "background", "linen",

RE: Re: drawing problems?

Edwin wrote: > the attached works! and the proof: http://leuven.economists.nl/lyx/selection.png

RE: Re: drawing problems?

Abdel wrote: >> comments? > > None. ok to commit?

RE: Trunk crashes when rendering tables

On Wed, Mar 26, 2008 at 10:03 AM, Dominik Böhm [EMAIL PROTECTED] wrote: create new file, insert table of arbitrary size, View=Source Code OR View PDF OR View DVI And LyX should have crashed! should be fixed in trunk. sorry for the inconvenience.

RE: New site map

and perhaps: rename Getting LyX - Download rename Resources - Support and add installation resources to Support ?

RE: Trunk crashes when rendering tables

On Wed, Mar 26, 2008 at 10:03 AM, Dominik Böhm <[EMAIL PROTECTED]> wrote: > create new file, > insert table of arbitrary size, > View=>Source Code OR View PDF OR View DVI > > And LyX should have crashed! should be fixed in trunk. sorry for the inconvenience.

RE: New site map

and perhaps: rename "Getting LyX" -> "Download" rename "Resources" -> "Support" and add installation resources to "Support" ?

RE: Primary colours of LyX? Was: Website re-design ideas

Martin wrote: You could consider choosing for white the default background of the LyX text window. That is kind of distinctive. distinctive and it stinks. we should get rid of this before 1.6 if you ask me, and set it to system default using QPalette::Base and QPalette::Text for text (and it

RE: Primary colours of LyX? Was: Website re-design ideas

Martin wrote: > You could consider choosing for "white" the default background > of the LyX text window. That is kind of distinctive. distinctive and it stinks. we should get rid of this before 1.6 if you ask me, and set it to system default using QPalette::Base and QPalette::Text for text

layout/style warnings

don't know whether this is a problem, but when i scroll with my mouse wheel over the layout combo in the document settings dialog i see the following in the console: Cannot delete style `Chapter*' Cannot delete style `Part*' Cannot delete style `Paragraph*' Cannot delete style `Subparagraph*'

RE: layout/style warnings

This d2emult: Cannot delete style `Chapter*' Cannot delete style `Part*' Cannot delete style `Paragraph*' Cannot delete style `Subparagraph*' This broadway: Cannot delete style `Abstract' Cannot delete style `Date' This is ENTCS: Cannot copy unknown style `LaTeX' All layouts so far:

layout/style warnings

don't know whether this is a problem, but when i scroll with my mouse wheel over the layout combo in the document settings dialog i see the following in the console: Cannot delete style `Chapter*' Cannot delete style `Part*' Cannot delete style `Paragraph*' Cannot delete style `Subparagraph*'

RE: layout/style warnings

This d2emult: Cannot delete style `Chapter*' Cannot delete style `Part*' Cannot delete style `Paragraph*' Cannot delete style `Subparagraph*' This broadway: Cannot delete style `Abstract' Cannot delete style `Date' This is ENTCS: Cannot copy unknown style `LaTeX' All layouts so far:

crash in math

ctrl-m alt m f 1 lyx.exe!lyx::InsetMathNest::doDispatch(lyx::Cursor cur={...}, lyx::FuncRequest cmd={...}) Line 764 + 0x34 bytesC++ lyx.exe!lyx::Inset::dispatch(lyx::Cursor cur={...}, lyx::FuncRequest cmd={...}) Line 197 + 0x1a bytes C++

crash in math

ctrl-m alt m f 1 lyx.exe!lyx::InsetMathNest::doDispatch(lyx::Cursor & cur={...}, lyx::FuncRequest & cmd={...}) Line 764 + 0x34 bytesC++ lyx.exe!lyx::Inset::dispatch(lyx::Cursor & cur={...}, lyx::FuncRequest & cmd={...}) Line 197 + 0x1a bytes C++

RE: Re: trunk not compilable

Abdel wrote Pavel Sanda wrote: 5. painting problems of outliner when smaller window is set. see attached. Confirmed. Edwin, could you help here please? the attached gets rid of the floating buttons, but somehow the minimum sizehint of the dockwidget seems to get lost. i don't have time to

completion crash

when i type a backslash in math lyx crashes (this is windows). oddly enough the crash doesn't occur with a debug build, so no backtrace unfortunately...

RE: completion crash

When did you update from svn? I checked in a fix 30 min ago. that didn't fix it for me...

RE: completion crash

don't know whether this is useful, but i see the following when i turn all compile warnings on: 2WordList.cpp 2c:\lyx\trunk\src\support/weighted_btree.h(1328) : warning C4244: 'argument' : conversion from 'int' to 'unsigned short', possible loss of data 2

RE: Re: trunk not compilable

Abdel wrote > Pavel Sanda wrote: >> 5. painting problems of outliner when smaller window is set. see attached. > > Confirmed. Edwin, could you help here please? the attached gets rid of the floating buttons, but somehow the minimum sizehint of the dockwidget seems to get lost. i don't have

completion crash

when i type a backslash in math lyx crashes (this is windows). oddly enough the crash doesn't occur with a debug build, so no backtrace unfortunately...

RE: completion crash

> When did you update from svn? I checked in a fix 30 min ago. that didn't fix it for me...

RE: completion crash

don't know whether this is useful, but i see the following when i turn all compile warnings on: 2>WordList.cpp 2>c:\lyx\trunk\src\support/weighted_btree.h(1328) : warning C4244: 'argument' : conversion from 'int' to 'unsigned short', possible loss of data 2>

RE: Re: trunk not compilable

on loading the user guide: msvcp90d.dll!104ec1b3() [Frames below may be incorrect and/or missing, no symbols loaded for msvcp90d.dll] lyx.exe!std::_Vector_const_iteratorlyx::TocItem,std::allocatorlyx::TocItem ::operator*() Line 98 + 0x14 bytes C++

RE: Re: trunk not compilable

on loading the user guide: msvcp90d.dll!104ec1b3() [Frames below may be incorrect and/or missing, no symbols loaded for msvcp90d.dll] > > lyx.exe!std::_Vector_const_iterator >::operator*() Line 98 + 0x14 bytes C++

RE: Re: build with vs c++ 2008 and cmake

I guess nothing. I have this change in my tree that I forgot to report... that still leaves me with 1c1 : fatal error C1083: Cannot open source file: 'Files/LyX': No such file or directory and this: 2LINK : fatal error LNK1181: cannot open input file 'intl.lib'

RE: Re: build with vs c++ 2008 and cmake

Compile again and it will happily work the second time. Don't ask me why... why didn't i think of that? ;-)

RE: Re: build with vs c++ 2008 and cmake

> I guess nothing. I have this change in my tree that I forgot to report... that still leaves me with 1>c1 : fatal error C1083: Cannot open source file: 'Files/LyX"': No such file or directory and this: 2>LINK : fatal error LNK1181: cannot open input file 'intl.lib'

RE: Re: build with vs c++ 2008 and cmake

> Compile again and it will happily work the second time. Don't ask me why... why didn't i think of that? ;-)

RE: Re: [Cvslog] r22417 - /lyx-devel/branches/BRANCH_1_5_X/lib/ui/stdmenus...

Abdel wrote: Jean-Marc Lasgouttes wrote: [X] Number this line [X] Line numbering activated why not a bit less verbose: [X] Line Number

RE: Re: [Cvslog] r22417 - /lyx-devel/branches/BRANCH_1_5_X/lib/ui/stdmenus...

Abdel wrote: >Jean-Marc Lasgouttes wrote: > [X] Number this line >[X] Line numbering activated why not a bit less verbose: [X] Line Number

  1   2   3   4   5   6   7   >