Re: cmake on Mac

2010-01-26 Thread Kornel Benko
Am Montag 25 Januar 2010 schrieb Vincent van Ravesteijn - TNW: Cmake shouldn't want to compile moc_* files. It shouldn't even know that they exist. These moc_* files are #included in the normal *.cpp files and they are now compiled twice and thus giving you the previously defined here errors.

Re: Trac rights

2010-01-26 Thread Guenter Milde
On 2010-01-25, Vincent wrote: Please, can we make the keywords, priority, severity and milestone fields to be editable only by people with rights. I understand that for people taking the step to report a bug, the bug is really major, but if everyone that reports a bug sets the milestone to

[patch] bug 6218: Wrong equation references after copy and paste of a previous equation

2010-01-26 Thread Jürgen Spitzmüller
http://www.lyx.org/trac/ticket/6218 The attached patch against branch implements a duplicate check for pasted labels in math (as we already have for text). OK? Jürgen Index: src/mathed/InsetMathHull.h === ---

Re: Trac rights

2010-01-26 Thread Jean-Marc Lasgouttes
Vincent v.f.vanraveste...@tudelft.nl writes: Please, can we make the keywords, priority, severity and milestone fields to be editable only by people with rights. It seems that the following plugin can do what we want. http://trac-hacks.org/wiki/BlackMagicTicketTweaksPlugin JMarc

RE: cmake on Mac

2010-01-26 Thread Vincent van Ravesteijn - TNW
Cmake shouldn't want to compile moc_* files. It shouldn't even know that they exist. These moc_* files are #included in the normal *.cpp files and they are now compiled twice and thus giving you the previously defined here errors. Why not? They are not part of svn, so they have to be

Re: cmake on Mac

2010-01-26 Thread Kornel Benko
Am Dienstag 26 Januar 2010 schrieb Vincent van Ravesteijn - TNW: Cmake shouldn't want to compile moc_* files. It shouldn't even know that they exist. These moc_* files are #included in the normal *.cpp files and they are now compiled twice and thus giving you the previously defined here

Re: View/Update toolbar position

2010-01-26 Thread Pavel Sanda
Jürgen Spitzmüller wrote: Pavel Sanda wrote: to sum it up - i change the toolbar very often so i asked about changing the defaults either to off or to vertical position. I'd rather fix the cause (i.e., allow for multiple toolbars in a row). like this? or should we put view before extra

Re: View/Update toolbar position

2010-01-26 Thread Jürgen Spitzmüller
Pavel Sanda wrote: like this? Looks like it. Great. Maybe widen is not the most transparent tag, I don't know (samerow?). or should we put view before extra instead after standard? Personally, I have it in the second row, before extra. But this means extra needs the tag, right? Then what

Re: r33229 - lyx-devel/trunk/src

2010-01-26 Thread Pavel Sanda
v...@lyx.org wrote: + // FIXME: LyX is not ready for outlining within inset. this is a regression or it was always like this? pavel

Re: View/Update toolbar position

2010-01-26 Thread Pavel Sanda
Jürgen Spitzmüller wrote: Maybe widen is not the most transparent tag, I don't know (samerow?). looks good. or should we put view before extra instead after standard? Personally, I have it in the second row, before extra. But this means extra needs the tag, right? exactly Then what

Re: r33229 - lyx-devel/trunk/src

2010-01-26 Thread Vincent
Pavel Sanda wrote: v...@lyx.org wrote: + // FIXME: LyX is not ready for outlining within inset. this is a regression or it was always like this? pavel I don't know.. I just put back what was removed. Vincent

Re: View/Update toolbar position

2010-01-26 Thread Jürgen Spitzmüller
Pavel Sanda wrote: Then what happens if view/update is switched off? you mean by user? then nothing since the layout is driven by qsettings from that point. OK. Jürgen

Re: cmake on Mac

2010-01-26 Thread Kornel Benko
Am Montag 25 Januar 2010 schrieb Vincent van Ravesteijn - TNW: > Cmake shouldn't want to compile moc_* files. It shouldn't even know that > they exist. These moc_* files are #included in the normal *.cpp files > and they are now compiled twice and thus giving you the "previously > defined here"

Re: Trac rights

2010-01-26 Thread Guenter Milde
On 2010-01-25, Vincent wrote: > Please, can we make the keywords, priority, severity and milestone > fields to be editable only by people with rights. > I understand that for people taking the step to report a bug, the bug is > really major, but if everyone that reports a bug sets the milestone

[patch] bug 6218: Wrong equation references after copy and paste of a previous equation

2010-01-26 Thread Jürgen Spitzmüller
http://www.lyx.org/trac/ticket/6218 The attached patch against branch implements a duplicate check for pasted labels in math (as we already have for text). OK? Jürgen Index: src/mathed/InsetMathHull.h === ---

Re: Trac rights

2010-01-26 Thread Jean-Marc Lasgouttes
Vincent writes: > Please, can we make the keywords, priority, severity and milestone > fields to be editable only by people with rights. It seems that the following plugin can do what we want. http://trac-hacks.org/wiki/BlackMagicTicketTweaksPlugin JMarc

RE: cmake on Mac

2010-01-26 Thread Vincent van Ravesteijn - TNW
>> Cmake shouldn't want to compile moc_* files. It shouldn't even know >> that they exist. These moc_* files are #included in the normal *.cpp >> files and they are now compiled twice and thus giving you the >> "previously defined here" errors. >> > >Why not? They are not part of svn, so they

Re: cmake on Mac

2010-01-26 Thread Kornel Benko
Am Dienstag 26 Januar 2010 schrieb Vincent van Ravesteijn - TNW: > >> Cmake shouldn't want to compile moc_* files. It shouldn't even know > >> that they exist. These moc_* files are #included in the normal *.cpp > >> files and they are now compiled twice and thus giving you the > >> "previously

Re: View/Update toolbar position

2010-01-26 Thread Pavel Sanda
Jürgen Spitzmüller wrote: > Pavel Sanda wrote: > > to sum it up - i change the toolbar very often so i asked about changing > > the defaults either to off or to vertical position. > > I'd rather fix the cause (i.e., allow for multiple toolbars in a row). like this? or should we put view before

Re: View/Update toolbar position

2010-01-26 Thread Jürgen Spitzmüller
Pavel Sanda wrote: > like this? Looks like it. Great. Maybe "widen" is not the most transparent tag, I don't know ("samerow"?). > or should we put view before extra instead after standard? Personally, I have it in the second row, before extra. But this means extra needs the tag, right? Then

Re: r33229 - lyx-devel/trunk/src

2010-01-26 Thread Pavel Sanda
v...@lyx.org wrote: > + // FIXME: LyX is not ready for outlining within inset. this is a regression or it was always like this? pavel

Re: View/Update toolbar position

2010-01-26 Thread Pavel Sanda
Jürgen Spitzmüller wrote: > Maybe "widen" is not the most transparent tag, I don't know ("samerow"?). looks good. > > or should we put view before extra instead after standard? > > Personally, I have it in the second row, before extra. But this means extra > needs the tag, right? exactly

Re: r33229 - lyx-devel/trunk/src

2010-01-26 Thread Vincent
Pavel Sanda wrote: v...@lyx.org wrote: + // FIXME: LyX is not ready for outlining within inset. this is a regression or it was always like this? pavel I don't know.. I just put back what was removed. Vincent

Re: View/Update toolbar position

2010-01-26 Thread Jürgen Spitzmüller
Pavel Sanda wrote: > >Then what happens if view/update is switched off? > > you mean by user? then nothing since the layout is driven by qsettings > from that point. OK. Jürgen