Peter Kümmel wrote:
I found a bug in the Qt4 version:
1. start lyx
2. new document
3. insert new table
4. mark whole table
5. right mouse click -> crash
Confirmed for qt3:
Assertion triggered in CursorSlice LCursor::anchor() const by failing
check "anc
hor_.depth() >= depth()" in file D:\de
Peter Kümmel wrote:
I found a bug in the Qt4 version:
1. start lyx
2. new document
3. insert new table
4. mark whole table
5. right mouse click -> crash
Confirmed.
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Juergen Spitzmueller wrote:
Peter Kümmel wrote:
It seems this could be done by a lyx newbie like me.
You're clearly not a newbie, but it could even be done by a newbie.
Adding a RC_TABLE_LINES to LyXRC and then using
lyxrc.read(RC_TABLE_LINES) in
Jean-Marc Lasgouttes wrote:
"Peter" == Peter Kümmel <[EMAIL PROTECTED]> writes:
Peter> Lars Gullik Bjønnes wrote:
I have no idea why you think having just one frontend is some kind
of silver bullet.
Peter> Ever heard about "lowest common denominator"? When you use more
Peter> front ends you
Jose' Matos wrote:
On Friday 23 June 2006 17:43, Andre Poenitz wrote:
No. But xforms could be removed right away.
Is there any reason for it to here?
What is the reason for not removing it now?
As a compromise I propose to mark it in the same level as gtk, people don't
try to break it
On Friday 23 June 2006 17:43, Andre Poenitz wrote:
> No. But xforms could be removed right away.
Is there any reason for it to here?
What is the reason for not removing it now?
As a compromise I propose to mark it in the same level as gtk, people don't
try to break it on purpose, keep it w
On Fri, Jun 23, 2006 at 06:33:03PM +0200, Peter Kümmel wrote:
> Lars Gullik Bjønnes wrote:
> > Peter Kümmel <[EMAIL PROTECTED]> writes:
> >
> > | Juergen Spitzmueller wrote:
> > | > Jean-Marc Lasgouttes wrote:
> > | >> 1.6: qt4, gtk and maybe qt3.
> > | >
> > | > And qt5.
> > |
> > | And the ol
Jean-Marc Lasgouttes wrote:
>> "Peter" == Peter Kümmel <[EMAIL PROTECTED]> writes:
>
> Peter> Lars Gullik Bjønnes wrote:
>>> I have no idea why you think having just one frontend is some kind
>>> of silver bullet.
>
> Peter> Ever heard about "lowest common denominator"? When you use more
> Pe
On Fri, Jun 23, 2006 at 12:32:59AM +0200, Enrico Forestieri wrote:
> On Thu, Jun 22, 2006 at 08:39:37PM +0200, Enrico Forestieri wrote:
>
> > When trying to import xxx.tex (attached) lyx (both 1.4 and 1.5) crashes.
> > The file xxx.lyx (attached, too) is produced, so it is lyx that is
> > crashin
On Thu, Jun 22, 2006 at 02:39:21PM -0500, Bo Peng wrote:
> >We have abondoned Coding_Rules(?) a long time ago and used 'do whatever
> >the majority in src/* does'
>
> Because it is easier to change the rules than change source code. BTW,
> the style I like is:
>
> class ThisClass
> {
> int thisF
On Fri, Jun 23, 2006 at 02:58:03PM +0200, Lars Gullik Bjønnes wrote:
> Edwin Leuven <[EMAIL PROTECTED]> writes:
>
> | Jose' Matos wrote:
> | > On Friday 23 June 2006 13:30, Jose' Matos wrote:
> | >> Surprisingly (at least to me) there was a so clear cut between those two
> | >> options.
> | > t
On Fri, Jun 23, 2006 at 08:44:21AM +0200, Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> | We have abondoned Coding_Rules(?) a long time ago and used 'do whatever
> | the majority in src/* does'
>
> No.
Have a look at the archives.
Andre'
On Fri, Jun 23, 2006 at 11:06:20AM +0200, Lars Gullik Bjønnes wrote:
> | I always have to force myself to put it to the right.
>
> When you get used to it, it feels a lot more natural.
I think you agree that I have written enough code with 'const' on the
right and still like it more on the left.
On Fri, Jun 23, 2006 at 12:00:11PM +0200, Peter Kümmel wrote:
> This is the responsibility of the system window manager. If this
> functionality was drawn into Qt it would restrict the freedom with
> which differing windowing/layout approaches are applied.
>
> This would be easy to implement, but
On Fri, Jun 23, 2006 at 01:37:19PM +0200, Lars Gullik Bjønnes wrote:
> No. I am saying that we should change the code rules when we see a
> need. That might be allowing "this_is_a_variable", but that has not
> really ben discussed yet.
We could do that. A head count in src suggests a small majorit
On Fri, Jun 23, 2006 at 02:09:38PM +0200, Lars Gullik Bjønnes wrote:
> Well... my point is that we cannot delete frontends just because it is
> easier to work with just one.
Guess what you do with apple trees.
> Do you really belive LyX is a driver for distros to use Qt4?
No. But xforms could be
On Fri, Jun 23, 2006 at 09:44:38AM +0200, Abdelrazak Younes wrote:
> Lars Gullik Bjønnes wrote:
> >Andre Poenitz <[EMAIL PROTECTED]> writes:
> >
> >| We have abondoned Coding_Rules(?) a long time ago and used 'do whatever
> >| the majority in src/* does'
> >
> >No.
>
> Is that an answer to a quest
> "Peter" == Peter Kümmel <[EMAIL PROTECTED]> writes:
Peter> Lars Gullik Bjønnes wrote:
>> I have no idea why you think having just one frontend is some kind
>> of silver bullet.
Peter> Ever heard about "lowest common denominator"? When you use more
Peter> front ends you could only support th
Lars Gullik Bjønnes wrote:
> Peter Kümmel <[EMAIL PROTECTED]> writes:
>
> | Juergen Spitzmueller wrote:
> | > Jean-Marc Lasgouttes wrote:
> | >> 1.6: qt4, gtk and maybe qt3.
> | >
> | > And qt5.
> |
> | And the old story goes on: lyx supports too much frontends.
>
> I have no idea why you think
Lars Gullik Bjønnes wrote:
> Peter Kümmel <[EMAIL PROTECTED]> writes:
>
> | Juergen Spitzmueller wrote:
> | > Jean-Marc Lasgouttes wrote:
> | >> 1.6: qt4, gtk and maybe qt3.
> | >
> | > And qt5.
> |
> | And the old story goes on: lyx supports too much frontends.
>
> I have no idea why you think
Peter Kümmel <[EMAIL PROTECTED]> writes:
| Juergen Spitzmueller wrote:
| > Jean-Marc Lasgouttes wrote:
| >> 1.6: qt4, gtk and maybe qt3.
| >
| > And qt5.
|
| And the old story goes on: lyx supports too much frontends.
I have no idea why you think having just one frontend is some kind of
silver
Jean-Marc Lasgouttes wrote:
>> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
>
> Juergen> Jean-Marc Lasgouttes wrote:
>>> 1.6: qt4, gtk and maybe qt3.
>
> Juergen> And qt5.
>
> It depends how slow we manage to be.
It's always so slow because no clear cut is made.
Juergen Spitzmueller wrote:
> Jean-Marc Lasgouttes wrote:
>> 1.6: qt4, gtk and maybe qt3.
>
> And qt5.
And the old story goes on: lyx supports too much frontends.
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> The longer term vision is that xforms and qt3 goes away, but
| Lars> that qt4 and gtk stays.
|
| Agreed (provided that we do have people who are dedicated to gtk).
Of cou
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Jean-Marc Lasgouttes wrote:
>> 1.6: qt4, gtk and maybe qt3.
Juergen> And qt5.
It depends how slow we manage to be.
JMarc
Jean-Marc Lasgouttes wrote:
> 1.6: qt4, gtk and maybe qt3.
And qt5.
SCNR,
Jürgen
> "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> The longer term vision is that xforms and qt3 goes away, but
Lars> that qt4 and gtk stays.
Jean-Marc> Agreed (provided that we do have people who are dedicat
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> This patch fixes bug 2655 (off by one error). It goes in trunk
Georg> right now. Jean-Marc, also OK for 1.4.2?
Yes, definitely.
JMarc
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> The longer term vision is that xforms and qt3 goes away, but
Lars> that qt4 and gtk stays.
Agreed (provided that we do have people who are dedicated to gtk).
JMarc
Juergen Spitzmueller wrote:
> Probably both.
I mean: a bug and a misnaming. It's not limited to Qt4, though.
Jürgen
Also sprach Peter Kümmel:
> I don't see this options here. Maybe because of my latex installation?
It's not yet implemented. But there is a booktabs branch. And I think we
should set up the proper interface for those enhancements now. Else, we have
to change it again.
> A other point: in the ta
Juergen Spitzmueller wrote:
> Peter Kümmel wrote:
>> I also think a overall default behavior must not be changed in a dialog
>> for one special table. But the Table dialog really misses on option to
>> remove/add ALL lines, which then also applies to added columns and rows.
>
> Please do not think
Peter Kümmel wrote:
> I also think a overall default behavior must not be changed in a dialog
> for one special table. But the Table dialog really misses on option to
> remove/add ALL lines, which then also applies to added columns and rows.
Please do not think "borders/no borders" only. Think of
I found a bug in the Qt4 version:
1. start lyx
2. new document
3. insert new table
4. mark whole table
5. right mouse click -> crash
Juergen Spitzmueller wrote:
> I was talking about the tabular *create* dialog.
But I see now this is still there.
Jürgen
Abdelrazak Younes wrote:
> Juergen Spitzmueller wrote:
>> Peter Kümmel wrote:
>>> It seems this could be done by a lyx newbie like me.
>>
>> You're clearly not a newbie, but it could even be done by a newbie.
>>
>>> Adding a RC_TABLE_LINES to LyXRC and then using
>>> lyxrc.read(RC_TABLE_LINES) in t
Abdelrazak Younes wrote:
> No, a default behavior doesn't need any choice. That's very bad UI wise.
Why default behaviour? Depending on the content, I might want either a
booktabs, an empty or a grid table. That's the choice I get from word
processors.
> But you could configure in the Preferenc
This patch fixes bug 2655 (off by one error). It goes in trunk right now.
Jean-Marc, also OK for 1.4.2?
Georg
Log:
* src/mathed/math_gridinset.C
(doDispatch): fix off by one error when checking cur.idx() (bug 2655)Index: src/mathed/math_gridinset.C
==
Abdelrazak Younes wrote:
Edwin Leuven wrote:
Abdelrazak Younes wrote:
Edwin Leuven wrote:
Abdelrazak Younes wrote:
Yes, rather than fixing the symptom we should fix the origin of
the problem.
afaics, every time we contruct a painter:
QPainter qp(qwa_->paintDevice());
Wait, there is somet
Edwin Leuven wrote:
> i call this pretty clear cut
>
> NO LINES:
>
> Paul Rubin
> Andre Poenitz
> Helge Hafting
> Juergen Spitzmueller
> Stephan Witt
> Oscar Lopez
> Ingar Pareliussen
> Myself
>
> LINES:
>
> Lars
> A.Scott Edward Hodel
> Todd Denniston
You forgot those who wanted three horiz
Juergen Spitzmueller wrote:
Peter Kümmel wrote:
It seems this could be done by a lyx newbie like me.
You're clearly not a newbie, but it could even be done by a newbie.
Adding a RC_TABLE_LINES to LyXRC and then using
lyxrc.read(RC_TABLE_LINES) in the ctor?
Also an item in the "look and feel"
Edwin Leuven wrote:
Abdelrazak Younes wrote:
Edwin Leuven wrote:
Abdelrazak Younes wrote:
Yes, rather than fixing the symptom we should fix the origin of
the problem.
afaics, every time we contruct a painter:
QPainter qp(qwa_->paintDevice());
Wait, there is something fishy here. My origin
Peter Kümmel wrote:
> It seems this could be done by a lyx newbie like me.
You're clearly not a newbie, but it could even be done by a newbie.
> Adding a RC_TABLE_LINES to LyXRC and then using
> lyxrc.read(RC_TABLE_LINES) in the ctor?
> Also an item in the "look and feel" ui interface?
>
> Or is
Edwin Leuven wrote:
> so i don't understand why you are blocking this...
This has been mentioned already: Most of us agree that the current default
is bad, but if you ask what should be done instead there is no such good
agreement anymore. Furthermore, this default has been like that for years.
T
Jean-Marc Lasgouttes wrote:
>> "Georg" == Georg Baum
>> <[EMAIL PROTECTED]>
>> writes:
>
> Georg> This patch adds support for \intop and \ointop. It goes in
> Georg> later if nobody objects.
>
> Georg> Jean-Marc, also for 1.4? I think it is safe.
>
> Why not just
>
> \def\intop{\in
Juergen Spitzmueller wrote:
> This feature is so
> easy to implement, I guess while arguing on the issue, we could have be done
> with implementing already.
It seems this could be done by a lyx newbie like me.
Adding a RC_TABLE_LINES to LyXRC and then using
lyxrc.read(RC_TABLE_LINES) in the cto
Edwin Leuven <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Good. so then you are 8 people that can collaborate to create an
| > solution that is acceptable to all. _And_ at the same time gives LyX
| > a new feature.
|
| if this is a joke, then you are the only one that is laughing.
Juergen Spitzmueller wrote:
> That's not a fair bill.
I said I use no lines usually, not that I want to change the default to that.
I agree with José that if we change we go for flexibility. This feature is so
easy to implement, I guess while arguing on the issue, we could have be done
with im
Edwin Leuven wrote:
> NO LINES:
[...]
> Juergen Spitzmueller
That's not a fair bill.
I said I use no lines usually, not that I want to change the default to that.
I agree with José that if we change we go for flexibility. This feature is so
easy to implement, I guess while arguing on the issue
Lars Gullik Bjønnes wrote:
Good. so then you are 8 people that can collaborate to create an
solution that is acceptable to all. _And_ at the same time gives LyX
a new feature.
if this is a joke, then you are the only one that is laughing...
Edwin Leuven <[EMAIL PROTECTED]> writes:
| Jose' Matos wrote:
| > On Friday 23 June 2006 13:30, Jose' Matos wrote:
| >> Surprisingly (at least to me) there was a so clear cut between those two
| >> options.
| > there was _not_ a clear cut...
|
| i call this pretty clear cut
|
| NO LINES:
|
|
Peter Kümmel wrote:
I would say "There Can Be Only One"
we need to make a choice for trunk
Jose' Matos wrote:
On Friday 23 June 2006 13:30, Jose' Matos wrote:
Surprisingly (at least to me) there was a so clear cut between those two
options.
there was _not_ a clear cut...
i call this pretty clear cut
NO LINES:
Paul Rubin
Andre Poenitz
Helge Hafting
Juergen Spitzmueller
Stephan
Lars Gullik Bjønnes wrote:
> Peter Kümmel <[EMAIL PROTECTED]> writes:
>
> | Qt3 is a short term solution, in the long run it is a dead end.
> |
> | At the latest when KDE 4 is out the majority of the distros have Qt4.
> | Also Qt4 could optionally ship with LSB systems.
> |
> | But LyX fiddles w
On Friday 23 June 2006 13:30, Jose' Matos wrote:
> Surprisingly (at least to me) there was a so clear cut between those two
> options.
there was _not_ a clear cut...
Today is a "no smiley day, not as I and Abdel seem to be doing a no no day.
--
José Abílio
Peter Kümmel <[EMAIL PROTECTED]> writes:
| Qt3 is a short term solution, in the long run it is a dead end.
|
| At the latest when KDE 4 is out the majority of the distros have Qt4.
| Also Qt4 could optionally ship with LSB systems.
|
| But LyX fiddles with four frontends. I want to see a longter
Jose' Matos wrote:
I am sorry but that is the point. You changing one arbitrary default by
another arbitrary default.
no lines is not an arbitrary default, it is the minimal (default) tabular
Surprisingly (at least to me) there was a so clear cut between those two
options.
i have troub
Lars Gullik Bjønnes wrote:
> Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>
> | Lars Gullik Bjønnes wrote:
> | > Peter Kümmel <[EMAIL PROTECTED]> writes:
> | > |
> | > | Yes, I would drop all other front ends from trunk immediately.
> | > |
> | > So we should keep only the one that is possible
Abdelrazak Younes wrote:
I am [not] saying that we should delete them but maybe not force all and every
change to happen on all frontend at the same time. We should choose one
(qt4) and let the other frontends be developed by those interested in them.
i couldn't agree more
On Friday 23 June 2006 13:12, Edwin Leuven wrote:
>> I also see that most peoble would like to retain the ability to insert
>> tabulars with lines...
>
>
>
> sure, more is better, but that is besides the point
I am sorry but that is the point. You changing one arbitrary default by
another arbit
Abdelrazak Younes wrote:
I am saying that we should delete them but maybe not force all and every
I am _not_ saying ...
Abdelrazak Younes wrote:
> Lars Gullik Bjønnes wrote:
>> Peter Kümmel <[EMAIL PROTECTED]> writes:
>>
>> |
>> | Yes, I would drop all other front ends from trunk immediately.
>> |
>>
>> So we should keep only the one that is possible to use on most distros
>> and platforms then? Qt3 it is. I'll co
On Thu, Jun 22, 2006 at 04:33:16PM -0700, Bryan Gmyrek wrote:
> In LyX version 1.4.1 on Mac OS X 10.4.6 the labels of equations
> overlays the equation. This is different from bug # 681
> Screen shot here:
> http://www.flickr.com/photos/[EMAIL PROTECTED]/172899674/
I think this happens because
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Peter Kümmel <[EMAIL PROTECTED]> writes:
| > |
| > | Yes, I would drop all other front ends from trunk immediately.
| > |
| > So we should keep only the one that is possible to use on most
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Man... isn't that what we are discussing right now? What is the
| difference between this and a "real" discussion?
Putting on the correct hat perhaps.
I have only been discussing:
- Do we have code rules
- What do they say, and do w
Lars Gullik Bjønnes wrote:
do you get lines if you import that into lyx with tex2lyx?
of course not
I also see that most peoble would like to retain the ability to insert
tabulars with lines...
sure, more is better, but that is besides the point
if people have to choose between no lines
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Peter Kümmel <[EMAIL PROTECTED]> writes:
| > |
| > | Yes, I would drop all other front ends from trunk immediately.
| > |
| > So we should keep only the one that is possible to use on most
| > distros
| > and platform
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Lars Gullik Bjønnes wrote:
| > | > Andre Poenitz <[EMAIL PROTECTED]> writes:
| > | > | We have abondoned Coding_Rules(?) a long time ago a
Lars Gullik Bjønnes wrote:
Peter Kümmel <[EMAIL PROTECTED]> writes:
|
| Yes, I would drop all other front ends from trunk immediately.
|
So we should keep only the one that is possible to use on most distros
and platforms then? Qt3 it is. I'll commence with the deleteion of the
others right a
Edwin Leuven <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > "stupid" is not objective. so you have to remove that
|
| i don't see why:
|
| 1. if i insert a tabular in latex
|
| \begin{tabular}{ccc}
| & & \\
| & & \\
| \end(tabular)
|
| i don't have any lines
|
| so why does
Lars Gullik Bjønnes wrote:
"stupid" is not objective. so you have to remove that
i don't see why:
1. if i insert a tabular in latex
\begin{tabular}{ccc}
& & \\
& & \\
\end(tabular)
i don't have any lines
so why does lyx add lines?
2. why are lines the way they are in lyx? historical acc
Peter Kümmel <[EMAIL PROTECTED]> writes:
|
| Yes, I would drop all other front ends from trunk immediately.
|
So we should keep only the one that is possible to use on most distros
and platforms then? Qt3 it is. I'll commence with the deleteion of the
others right away.
|
| Often it sounds li
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Lars Gullik Bjønnes wrote:
| > | > Andre Poenitz <[EMAIL PROTECTED]> writes:
| > | > | We have abondoned Coding_Rules(?) a long time ago and used 'do
| > | > whatever
Edwin Leuven <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > p1: Changing user visible defaults is bad
| > p2: This patch changes user visible defaults
| > -
| > This patch is bad
|
|
| p1. changing stupid user visible defaults is good
| p2. t
Abdelrazak Younes wrote:
> And the good news is that, with this patch and msvc2005, the UserGuide
> PageDown scrolling test is now at *18* seconds whereas it was at *34*
> seconds previously! It is now faster than qt3 on my machine (which is 22s).
Great, I also get a huge speedup, from 31 to 19 se
On Friday 23 June 2006 11:00, Peter Kümmel wrote:
> Abdelrazak Younes wrote:
> > Peter Kümmel wrote:
>
>
>
> I didn't know the 'no-smiley day', but it looks
> interesting, and I think I like it.
The concept is best expressed here:
http://www.lyx.org/news/2726.php#item3
--
José Abílio
Andre Poenitz wrote:
> On Tue, Jun 20, 2006 at 01:09:15PM +0200, Peter Kümmel wrote:
>> +if (width != -1 && height != -1 && posx != -1 && posy != -1) {
>> +view.initNormalGeometry(QRect(posx, posy, width, height));
>> +view.resize(width, height);
>> +view.mo
Abdelrazak Younes wrote:
Edwin Leuven wrote:
Abdelrazak Younes wrote:
Yes, rather than fixing the symptom we should fix the origin of
the problem.
afaics, every time we contruct a painter:
QPainter qp(qwa_->paintDevice());
Wait, there is something fishy here. My original patched used to
ca
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>> I do not know whether this is related to your patch(es): try to
>> insert a collapsable inset in a tabular cell; the right margin of
>> the inset is outside of the screen.
Martin> I suppose the speed-up patch exposed this bug,
Umm
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Andre Poenitz <[EMAIL PROTECTED]> writes:
| > | We have abondoned Coding_Rules(?) a long time ago and used 'do
| > whatever
| > | the majority in src/* does'
| > No.
|
| Is that an answer t
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
I didn't know the 'no-smiley day', but it looks
interesting, and I think I like it.
> We should keep one (qt4 of course)
Yes, I would drop all other front ends from trunk immediately.
>> 2 operating systems,
>
> 3. You forgot MacOSX!
>
>> Qt
Lars Gullik Bjønnes wrote:
"Bo Peng" <[EMAIL PROTECTED]> writes:
| > We have abondoned Coding_Rules(?) a long time ago and used 'do whatever
| > the majority in src/* does'
|
| Because it is easier to change the rules than change source code. BTW,
| the style I like is:
|
| class ThisClass
|
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Andre Poenitz wrote:
| > On Wed, Jun 21, 2006 at 10:24:31AM +, Angus Leeming wrote:
| >> I think it's just because we decided it improves readability. These things
| >> should be read from right to left:
| >>QRect
Edwin Leuven wrote:
Edwin Leuven wrote:
we could check for default values instead at the beginning of
setQPainterPen, but this seems a bit fragile
this seems to work fine (since we call this one only after creating a
painter):
void QLPainter::setQPainterPen(QPainter & qp, LColor_color col,
Lars Gullik Bjønnes wrote:
p1: Changing user visible defaults is bad
p2: This patch changes user visible defaults
-
This patch is bad
p1. changing stupid user visible defaults is good
p2. this patch changes stupid user visible defaults
-
> "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> "Sven" == Sven Schreiber <[EMAIL PROTECTED]> writes:
Sven> Hi all, when I shove an entire subsection into a note inset, the
Sven> numbering of the other non-note subsections remains as if
Sven> nothing was "commented out",
Edwin Leuven wrote:
Abdelrazak Younes wrote:
Yes, rather than fixing the symptom we should fix the origin of the
problem.
afaics, every time we contruct a painter:
QPainter qp(qwa_->paintDevice());
Wait, there is something fishy here. My original patched used to cache
also the current
> "Sven" == Sven Schreiber <[EMAIL PROTECTED]> writes:
Sven> Hi all, when I shove an entire subsection into a note inset, the
Sven> numbering of the other non-note subsections remains as if
Sven> nothing was "commented out", i.e. numbers on screen do not match
Sven> the printed output.
Sven>
Edwin Leuven <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| >
| > I do not think such a change of defaults is acceptable without
| > providing for a mechanism to retain the same defaults.
|
| to me this looks like you are pointing a gun with a blank
|
| really, where's the logic?
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Andre Poenitz wrote:
| > On Wed, Jun 21, 2006 at 10:24:31AM +, Angus Leeming wrote:
| >> I think it's just because we decided it improves readability. These things
| >> should be read from right to left:
| >>QRect const &
| >>A reference
Edwin Leuven wrote:
we could check for default values instead at the beginning of
setQPainterPen, but this seems a bit fragile
this seems to work fine (since we call this one only after creating a
painter):
void QLPainter::setQPainterPen(QPainter & qp, LColor_color col,
Painter::line
Lars Gullik Bjønnes wrote:
I do not think such a change of defaults is acceptable without
providing for a mechanism to retain the same defaults.
to me this looks like you are pointing a gun with a blank
really, where's the logic?
Edwin Leuven <[EMAIL PROTECTED]> writes:
| the majority of the people who responded were clearly in favor of
| defaulting to tables without lines
|
| it makes more sense in any case so unless someone is going to point a
| shotgun at me, i am going to shove in the attached...
I do not think suc
Got no replies on this on the users list, so I'm trying again on lyx-devel.
-sven
Original-Nachricht
Betreff: bug?: section numbering in note-insets
Datum: Thu, 15 Jun 2006 14:33:13 +0200
Von: Sven Schreiber <[EMAIL PROTECTED]>
An: LyX Users
Hi all,
when I shove an entire subse
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Hello,
One more brick to the wall: 16/17 seconds for UserGuide now.
Abdel.
Your recent two patches are very interesting.
Are they already in your branch? (Wanna see the
speedup by myself. :) )
Yes, they are in my branch.
By the way look in the
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Andre Poenitz <[EMAIL PROTECTED]> writes:
| > | We have abondoned Coding_Rules(?) a long time ago and used 'do
| > whatever
| > | the majority in src/* does'
| > No.
|
| Is that an answer to a question, an imperative a
Peter Kümmel wrote:
Peter Kümmel wrote:
Haven't we discussed the patch on the list? I don't wanna explain all
the stuff again in the log message.
. don't wanna see here my comments again ;)
Sorry, this was a very emotional reply on a harmless request,
but I didn't expect that this patch
On Friday 23 June 2006 08:44, Abdelrazak Younes wrote:
> Does your "No" weight more than our three "Yes"?
That is one of the privileges of the BDFL (python jargon).
> The weather is hot today...
Foggy around here, so not much. But then we always expected our lost king to
appear in a foggy m
Abdelrazak Younes wrote:
Yes, rather than fixing the symptom we should fix the origin of the
problem.
afaics, every time we contruct a painter:
QPainter qp(qwa_->paintDevice());
we get the default pen:
The default pen is a solid black brush with 0 width, square cap style
(Qt::Square
Abdelrazak Younes wrote:
> Hello,
>
> One more brick to the wall: 16/17 seconds for UserGuide now.
>
> Abdel.
>
Your recent two patches are very interesting.
Are they already in your branch? (Wanna see the
speedup by myself. :) )
Peter
1 - 100 of 106 matches
Mail list logo
